Argentine Agentic Commerce 2027

Summary

By Q4 2027, between 13% and 20% of LATAM retail intent (Forrester / Flywheel projections) will route through agent intermediaries — ChatGPT Instant Checkout, Claude shopping flows, Gemini's product graph. The marketplaces that emit a controlled, opt-in agent feed and integrate with the Agentic Commerce Protocol (ACP) will retain the relationship; the ones that don't will be disintermediated as scrape targets.

This RFC proposes a concrete architecture for Argentine marketplaces — primarily Mercado Libre, secondarily Tiendanube + Falabella + Magalu — to participate in agentic commerce without ceding the marketplace-buyer relationship to third parties.

Why now

1. Buyer-side agent shipping is real, not hypothetical.

·OpenAI Instant Checkout shipped September 2025 with Etsy + Shopify on ACP 2026-04-17.

·Anthropic has shipped MCP-driven shopping demos through partner builds (June 2025).

·Google's Gemini is indexing product feeds against Schema.org/Product for buyer-intent queries.

2. Mercado Libre's CEO has publicly committed to agentic commerce.

"We are developing our own agentic experience inside MercadoLibre … agentic commerce could mean that retail will move even faster from offline to online."

— Ariel Szarfsztejn, CEO Mercado Libre, Q4 2025 earnings call (Feb 26 2026)

But MELI's public agent surface, as of May 2026, exposes only one MCP tool: search_documentation. The seller-side agent tools needed to compete with Tiendanube's Lumi and Mercado Pago's Claude Code marketplace are not shipped.

3. Tiendanube launched Lumi at InovA 2026.

Direct LATAM marketplace competitor with an AI assistant for sellers and a WhatsApp checkout (NuvemChat). Tiendanube reported R$65 billion in sales and is moving aggressively into the AI-friendly platform positioning.

The empty space between "MELI sellers asking ChatGPT to write their listings" and "MELI ratifying that workflow" is competitive territory Tiendanube is happy to occupy.

Architecture — three layers

Layer 1 — Discovery (the agent-side defense)

A controlled ACP feed at /.well-known/agentic-feed.json that advertises the marketplace's preference for routing buyers through native checkout, defaults to opt-in, and returns paginated FeedProduct entries with deep-links so even unaffiliated agents prefer routing through MELI.

Reference impl: @ar-agents/mercadolibre/feed. Live at bridge-hello.ar-agents.ar.

Layer 2 — Transaction (the routing-back surface)

An ACP facilitator at /api/acp/checkout_sessions that accepts buyer-agent checkout requests per ACP 2026-04-17, resolves the cart against the marketplace's actual inventory + price + shipping data, and runs the actual capture inside MELI's checkout, not via third-party Stripe.

This is the architectural difference between MELI participating in agentic commerce vs being scraped.

Reference impl: @ar-agents/agentic-commerce-bridge.

Layer 3 — Seller-side agent

An expanded MCP server / AI SDK toolkit covering the seller-relevant API surface — items, categories, questions, orders, claims, shipments, reputation, promotions, webhooks. With HITL gates on irreversible operations.

Reference impl: this package. 14 tools shipped, 142 tests, MIT-licensed, ready to extend MELI's existing mercadolibre/mercadolibre-mcp-server.

Open questions for the comment period

1. Marketplace-side authentication. Should there be a marketplace-issued buyer-agent token for higher-trust flows?
2. Argentine consumer law (24.240). Who is the legal buyer of record — the agent, the user, or the agent operator?
3. Mercado Pago integration. ACP 2026-04-17 assumes Stripe-style payment_intents. A LATAM-localized profile may be needed.
4. Sandbox infrastructure. None of the LATAM marketplaces today provide an agent-friendly sandbox. This architecture would benefit from a public sandbox mode.
5. Trademark + co-branding. What's the pattern when a community-built impl gets ratified? See Stripe's Community SDKs.

Comment + collaborate

·GitHub Discussions: ar-agents/ar-agents/discussions

·Direct: naza@helloastro.co subject [rfc-001]

·Strategic argument: POSITIONING.md

·Adoption paths: /integrate