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

ar-agents, open infrastructure for AI corporations in Argentina

Cada path está optimizado para una audiencia diferente. Si dudás, empezá por /play (30 segundos, sin setup, sin compromiso). Si ya querés ir a producción, /incorporar es el wizard humano. Si sos un agente, andá directo al SDK.

Las 3 paths comparten backend: el mismo /api/auto-incorporate, el mismo audit log con HMAC, el mismo template apps/sociedad-ia-starter. Lo que cambia es el surface por el cual entrás. Podés combinarlas, empezar con /play, ir a /incorporar cuando sepas qué configurar, terminar usando el SDK para orchestration recurrente.

any visitor · regulator · journalist30 segundos

Try without installing

Para ver una sociedad-IA argentina operando ahora mismo, sin setup, sin cuenta, sin cert.

Open /playir →
12 tools, streaming via Vercel AI Gateway, agent corre Claude Sonnet 4.6.
Pick a scenario
Hacé click en "01 · cobro B2B", agente valida CUIT, consulta padrón, chequea BCRA, crea suscripción MP, manda WhatsApp.
Watch the audit logir →
Cada tool call queda firmado HMAC-SHA256 en la sidebar. Hacé click en 'ver dashboard ↗' para el timeline forense completo.

founder · operador · accountant~10 minutos + 5-10 días hábiles (ARCA + IGJ)

Incorporar una sociedad-IA

Para constituir una empresa argentina operada por IA, hoy. SAS estándar mientras la ley sociedades-IA no esté sancionada, el código pre-cableado migra el día 1.

Abrir el wizardir →
Completás denominación + tipo + capital + objeto + email contacto. El pre-flight de IGJ corre en vivo (mismas reglas que validate_igj_inscription).
Descargar los 4 archivos
package.json, lib/agent.ts, .env.example, README.md.
Click 'Deploy en Vercel'
Clona apps/sociedad-ia-starter directo. Vercel auto-injecta los env-var slots.
Cargar credenciales reales
AFIP cert (5-10 días desde ARCA → Clave Fiscal), MP token (1 día developers.mercadopago.com), Meta WhatsApp (10-15 días business verification).
Inscripción IGJ vía TAD
Solicitar inscripción de la SAS. Tu agente queda online apenas el cert + IGJ + MP estén wired.

developer · external orchestrator · USA-LLC~5 minutos

Programmatic agent

Para que un agente externo (USA-LLC, ChatGPT, Claude tool, custom pipeline) auto-incorpore programáticamente.

Install
pnpm add @ar-agents/incorporate (zero deps, ~4KB, MIT, SLSA-provenanced)
Call incorporate()ir →
await incorporate({ denominacion: "ACME-AI SAS", tipo: "SOCIEDAD-IA", capitalSocial: 1, objeto: "..." })
Materialize the 4 files
Object.entries(result.config).map(([path, contents]) => writeFile(path, contents))
Deploy + verify
result.deploy.oneClickUrl + result.audit.dashboardUrl. Pasá el sessionId para chainear el forensic timeline.

Y después?

Una vez tengas el surface básico operando, el siguiente layer es compliance + observability:

/dashboard/{sessionId}: forensic timeline live (SSE updates).
/verify: paste a session id, get an independent HMAC verification report.
Cookbook recipe 19: daily compliance digest cron job.
Cookbook recipe 20: multi-tenant marketplace pattern.
/architecture: la arquitectura full + Edge Runtime contract.
/security: threat model con 14 amenazas explícitas.

Need help?

/faq cubre 21 preguntas across 5 audiencias. Si no aparece la tuya, abrí un issue o mandá un email a clementenaza@gmail.com: primera respuesta <48hs.

3 caminos. Elegí el que aplica.

Try without installing

Incorporar una sociedad-IA

Programmatic agent

Y después?

Need help?