ar-agents is a Mercado Pago Agent Toolkit for the Vercel AI SDK 6. It ships 89 typed tools that an LLM agent can call directly to drive Mercado Pago billing flows: subscriptions, payments, refunds, checkout pro, marketplace OAuth, cuotas (installments), QR in-store, 3DS challenge resolution, point-of-sale devices, webhooks. Sidecar packages cover AFIP/ARCA, WhatsApp Business Cloud, banking (CBU/CVU + BCRA), and shipping (Andreani/OCA/Correo Argentino).

How is this different from the official mercadopago SDK?

The official mercadopago SDK is a thin REST client. It does not ship Vercel AI SDK tool schemas, does not implement webhook HMAC verification with replay protection, does not run on Edge Runtime (Node-only), and does not gate irreversible operations. ar-agents adds all of that on top of the underlying API: 89 typed tools, deterministic idempotency keys derived from inputs, programmatic human-in-the-loop on refund/cancel/delete, npm provenance attestation, Vercel KV adapters via subpath, OpenTelemetry instrumentation. You can use both packages in the same project; ar-agents wraps the underlying API directly without depending on the official SDK.

Does ar-agents work on Edge Runtime?

Yes. The whole package is Web Crypto-based with no node:crypto dependency, so it runs on Vercel Edge Functions, Cloudflare Workers, Deno, and any other V8-isolate runtime. Webhook signature verification, HMAC, and idempotency-key generation all use the Web Crypto API.

What is HITL (human-in-the-loop) in ar-agents?

Eight tools mutate state irreversibly (refund_payment, cancel_subscription, delete_customer_card, etc.). The toolkit accepts a requireConfirmation callback that gates each invocation: the tool function literally will not execute until your callback returns true. This is a programmatic gate, not just an LLM instruction. You can show the user a UI and wait for their explicit approval before any irreversible operation runs.

How does idempotency work?

Every POST request gets an auto-generated idempotency key. For LLM-driven retries, four mutating tools (create_payment, create_subscription, create_payment_preference, refund_payment) use a deterministic key derived from a SHA-256 hash of the meaningful inputs (external_reference, amount, payment_method, etc.). Same inputs produce the same key, so retries return the existing resource instead of double-charging the customer.

Yes. MIT license. No paid tier, no telemetry phone-home, no usage caps. The package is published to npm under the @ar-agents scope with SLSA v1 provenance attestations.

What about AFIP, WhatsApp, banking, shipping?

Sidecar packages cover the rest of the Argentine business stack: @ar-agents/identity (CUIT/CUIL validation + AFIP/ARCA padron lookup with monotributo category and IVA condition), @ar-agents/facturacion (AFIP/ARCA factura electronica via WSFE), @ar-agents/whatsapp (WhatsApp Business Cloud API with HMAC webhook verify and AR phone normalizer), @ar-agents/banking (CBU/CVU validation + BCRA Central de Deudores), @ar-agents/shipping (Andreani, OCA, Correo Argentino), @ar-agents/identity-attest (HMAC-signed verification orchestrator). Each ships independently to npm.

Is there a Model Context Protocol (MCP) server?

Yes. @ar-agents/mcp bundles all 7 ar-agents packages into a single MCP server compatible with Claude Desktop, Cursor, Codeium, Continue, Cline, or any MCP host. Auto-detects which packages to enable from environment variables. Listed on Glama (glama.ai/mcp/servers/ar-agents/ar-agents) and the official MCP Registry (io.github.ar-agents/mcp).

/registry · public · self-listed · 2026-05-11

Public registry of implementations.

Every Argentine AI-corp or demo that implements RFC-001..004 can be listed here. Public metadata only: no customer counts, no revenue, no PII. Self-listing via PR at github.com/ar-agents/ar-agents.

Honest disclosure. Today the 5 listed entries are all operated by the same person (Naza). This is NOT a multi-operator ecosystem, it is a reference implementation + 4 demos by the project author. Zero (0) productive AI-corps (with real customers, real invoices, real collections): the AI-corp law has not yet been sanctioned and the regime does not legally exist. When a third party adopts the RFCs and operates under its own CUIT, their entry will be added via PR. In the meantime, what you see is a complete technical proposal validated end-to-end by a single person.

1

Reference impl

4

Demos live

0

Productive sociedades

5

Total live

ar-agents (this site, reference implementation)
AR · Naza
Reference impllive
Reference implementation of the spec. Hosts /play (interactive demo), /verify (HMAC verification), /api/play/audit/* (audit endpoints), /test-vectors (conformance vectors). Not a productive company, i.e. does not transact with real customers, does not emit invoices, does not collect. Source of truth for the spec.
https://ar-agents.ar· RFCs: rfc-001-v1, rfc-002-v1, rfc-003-draft, rfc-004-draft· listed since 2026-05-05
mp-hello demo
AR · Naza
Demolive
Mercado Pago Subscriptions integration demo. Wired to a real MP sandbox + production app 178743372667921. Shows the @ar-agents/mercadopago lib end-to-end. Not a productive company.
https://mp-hello.ar-agents.ar· RFCs: rfc-001-v1· listed since 2026-05-05
cuit-hello demo
AR · Naza
Demolive
AFIP/ARCA padron lookup + CUIT validation demo. Uses a real AFIP cert (homo for safety; prod cert available). Shows the @ar-agents/identity lib end-to-end. Not a productive company.
https://cuit-hello.ar-agents.ar· RFCs: rfc-001-v1· listed since 2026-05-05
whatsapp-hello demo
AR · Naza
Demolive
WhatsApp Business Cloud API demo combining identity + MP + WhatsApp libs. Webhook handler + chat UI. Limited by Meta verification 5-recipient dev cap until business verification passes.
https://whatsapp-hello.ar-agents.ar· RFCs: rfc-001-v1· listed since 2026-05-05
bridge-hello demo
AR · Naza
Demolive
Agentic Commerce Bridge demo. AP2 + ACP + MCP protocol surfaces wired to MP. Shows how a foreign agent (Wyoming DAO LLC) interacts with an AR AI-corp per cookbook recipe 21.
https://bridge-hello.ar-agents.ar· RFCs: rfc-001-v1· listed since 2026-05-05
(your sociedad-IA here)
AR · -
Productive sociedaddraft
Open a PR adding your AI-corp's metadata to apps/landing/src/app/registro/page.tsx in github.com/ar-agents/ar-agents. Provide: name, operator name + CUIT, public URL, RFCs you conform to, plain-English disclosure. The PR will be reviewed for honest claims (e.g. claimed RFC-001 conformance must include a /.well-known/agents.json that resolves).

How to add your AI-corp

Make sure your AI-corp serves /.well-known/agents.json with public metadata (RFC-002).
Make sure your audit endpoint returns signed entries that pass the RFC-004 conformance vectors (/test-vectors).
Open a PR at github.com/ar-agents/ar-agents modifying apps/landing/src/app/registro/page.tsx with your entry.
The PR is approved if the declared endpoints respond + the disclosure is honest. No further requirements.