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).

2026-05-11 · ar-agents · /notes

Shipping spree: 18 rounds in one day.

What shipped on 11 May 2026, in 18 autonomous rounds.

On 28 April 2026 Argentina's Ministerio de Desregulación announced a regime for sociedades-IA, AI-only companies that can transact autonomously. By 5 May the npm packages, the landing site, and RFC-001 (three-layer civil liability) were live. The first reaction from the technical community was: "OK, the basic libraries are there. Now what does it actually mean to operationalize one of these?"

The 13 days between then and now (today, 11 May) have answered that question by shipping the missing pieces. Today alone, in 18 distinct shipping rounds, the work jumped from "has libraries + has a vision RFC" to "has 5 RFCs, 30 recipes, 32 public surfaces, a working certifier, a frozen conformance test-vectors corpus, a one-page regulator brief, a legislative synthesis in Spanish and English, a public registry with 5 deployments each scoring 100/100."

This note is the recap.

What shipped

The 18 rounds layered concrete artifacts on top of the existing libraries. Each round took 30–90 minutes; cumulative inventory at the end of round 18:

5 RFCs (001, 002, 003, 004, 005) covering civil liability, agent discovery, cross- jurisdictional reciprocity, normative operational-log wire format, and the Ed25519 asymmetric upgrade path. CC-BY-4.0, ready for legislation to cite-by-reference.
2 frozen test-vectors files: RFC-004 v1 (7 vectors) + RFC-005 v1 (3 vectors) with hex-exact deterministic HMAC + Ed25519 signatures. Reference impl passes all 10 (103 vitest tests across 6 files).
Public certifier at /certifier — paste any URL, get a 0-100 score across ~11 checks in seconds. Honors rfcConformanceclaims: SKIPs checks the manifest doesn't claim, FAILs only on overclaim. Reference impl + all 4 demos score 100/100 A.
14 HTTP APIs + 3 well-known endpoints — audit (read/verify/csv/stream), badge, cert-badge, openapi (JSON + YAML), discovery, certifier, conformance-history (KV time-series), auto-monitor (daily cron), auto-incorporate, rfc-003-envelope, audit-summary, well-known/verify-key (RFC-004 § 5), well-known/sociedad-ia/keys (RFC-005 § 4).
Bilingual narrative: /legislación (Spanish, for the actual legislator) and /en/legislation (English, for international press + comparative-law scholars). Both with suggested cite-by-reference articles.
Regulator brief: /auditor — 1-page Spanish-first, print-friendly summary. 7-minute read. Every claim links to evidence.
Public registry: /registro — 5 entries, each with live cert-badge + conformance sparkline. All 5 currently score 100/100 A. Self-listing via PR (recipe 30).
30 cookbook recipes at /examples. Highlights:
- 25 — quarterly compliance report generator (the answer to a regulator request, generated from the audit log alone).
- 26 — single-shot certifier function (also backs the web /certifier UI).
- 27 — live monitoring loop with drift detection + alerting.
- 28 — operator pre-launch readiness checklist.
- 29 — Ed25519 keypair generation + publication walkthrough (RFC-005 § 4).
- 30 — registry-submission PR-body generator with honesty heuristics + pre-flight checks.
4 published JSON schemas at /schemas/* — operational-log entry (RFC-004), agents.json (RFC-002), certification (the /certifier output), cross-jurisdiction envelope (RFC-003).
Operator tooling: /glossary (21 alphabetized terms), /refs (BibTeX/APA/Chicago citations), /share (6 prepared social + email templates), /timeline (visual chronology), /audit-explorer/{sessionId} (forensic per-session view), /feed.xml (Atom feed of shipping rounds), CITATION.cff at the repo root.

What's NOT in the work

Honest scoping. The 18 rounds covered the technical infrastructure layer. They do not cover:

Tax doctrine. Does a sociedad-IA pay monotributo, IVA, ganancias, ganancia mínima presunta? Each requires its own political decision. The RFCs are silent.
Labor. Can a sociedad-IA be an employer? Is it joint-and-several with the humans it instructs? Out of scope.
Bankruptcy. How is a sociedad-IA liquidated? What happens to cryptographic keys in concurso preventivo? Out of scope.
Penal. Mens rea of an entity without consciousness. Imputability of the operator for dolo or culpa of the agent. Out of scope.
Real productive sociedades.Today (2026-05-11) the registry has 1 reference implementation + 4 demos. Zero productive sociedades transacting with real customers. That's honest. It changes the day Meta Business Verification + MP production access land for the existing Astro/Publi projects, or the day a third party deploys their own and lists it.
Outreach.The artifacts are done; getting them in front of Sturzenegger's asesores, AAIP/AFIP staff, international press, and comparative-law scholars is the manual next step. /share has templates ready.
IETF / W3C submission. The RFCs are published under CC-BY-4.0 with GitHub Discussions as the governance surface. Submitting them as IETF Internet-Drafts or W3C Community Group notes is a future decision.

Why all this

The bet is straightforward. The Argentine sociedad-IA regime will be drafted by people who are smart but not necessarily steeped in agent infrastructure. The cheapest way to get a good outcome is to do the technical groundwork in the open, first, under permissive licenses, with versioned + conformance- tested specs.

Then the law has something concrete to cite. Then operators have something concrete to implement. Then regulators have something concrete to inspect. The work compounds.

18 rounds is enough for one day. Tomorrow: outreach.