/registry · public · self-listed · 2026-05-11
Public registry of implementations.
Every Argentine automated company 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.
- ar-agents (this site, reference implementation)AR · Nazareno ClementeReference impllivegood standing
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 demoAR · Nazareno ClementeDemolivegood standing
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.
- cuit-hello demoAR · Nazareno ClementeDemolivegood standing
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.
- whatsapp-hello demoAR · Nazareno ClementeDemolivegood standing
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.
- bridge-hello demoAR · Nazareno ClementeDemolivegood standing
Agentic Commerce Bridge demo. AP2 + ACP + MCP protocol surfaces wired to MP. Shows how a foreign agent (Wyoming DAO LLC) interacts with an AR automated company per cookbook recipe 21.
- (your automated company here)AR · -Productive companydraftunverified
Open a PR adding your automated company's metadata to apps/landing/src/app/registro/page.tsx in github.com/ar-agents/ar-agents, or self-list via POST /api/registry. Provide: name, operator name + CUIT, public URL, RFCs you conform to, plain-English disclosure. The entry goes live once the automated certifier verifies the declared endpoints (rating ≥ C).
- AR Agents Operaciones Sociedad AutomatizadaAR · Nazareno ClementeProductive companyformingunverified
Company in formation. Registry stub created at incorporation; not yet operative. Not in good standing until it goes live.
· listed since 2026-07-08 - Sociedad Automatizada de Plantillas LegalesAR · -Productive companyformingunverified
Company in formation. Registry stub created at incorporation; not yet operative. Not in good standing until it goes live.
· listed since 2026-07-20
How to add your automated company
- Make sure your automated company serves
/.well-known/agents.jsonwith 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.tsxwith your entry. - The PR is approved if the declared endpoints respond + the disclosure is honest. No further requirements.
Or self-list via API (no PR)
POST to POST /api/registry with your metadata. The server runs the certifier against your declared URL and returns a write-once owner token. Your entry starts draft / unverified and auto-flips to live / good standing only when the certifier scores ≥ C (60) over the endpoints you declare. This is automated conformance of self-declared endpoints, not a solvency, identity, or fraud judgement; a self-declared CUIT stays outside the trust claim until verified.
Public good-standing oracle
Any counterparty (bank, PSP, marketplace, agent framework) can query an entry's standing before transacting: GET /api/registry/good-standing?url=. It returns a small, cacheable, Ed25519-signed answer, offline-verifiable with arg-verify; the ar-agents signature is convenience, the load-bearing trust is the target's own public anchors that the oracle forwards.