The Agentic Commerce Stack — Ahnaf Prio, Best Buy
Agentic checkout spans product feeds, tool discovery, checkout state, and delegated payment authority. Builders need protocol-specific adapters and evals because ACP and UCP have not converged.
The talk maps agentic commerce across MCP tool access, product feeds, checkout APIs, and payment authorization. **ACP and UCP** use different schemas, while current ChatGPT and Gemini integrations expect merchants to submit feeds rather than expose catalog search.
Treat commerce as a stateful protocol integration, not a browser automation task. Test behavior, schema compliance, latency, and leakage, and model checkout states such as **not ready, ready for payment, and completed** explicitly.
The talk maps agentic commerce across MCP tool access, product feeds, checkout APIs, and payment authorization. **ACP and UCP** use different schemas, while current ChatGPT and Gemini integrations expect merchants to submit feeds rather than expose catalog search. Treat commerce as a stateful protocol integration, not a browser automation task. Test behavior, schema compliance, latency, and leakage, and model checkout states such as **not ready, ready for payment, and completed** explicitly. The ecosystem is unsettled: **AP2**, identity standards, multi-agent delegation, and ACP/UCP convergence are still forming. Current payment paths also retain human or processor control rather than offering broadly autonomous payment.
This turns agentic commerce into a protocol and state-machine problem spanning discovery, schemas, checkout, authorization, and evaluation. It narrows near-term autonomy: merchant feeds and explicit checkout states matter more than browser control, payments still retain human or processor authority, and incompatible or unfinished standards make adapters, leakage tests, and workload-specific validation necessary rather than assuming one interoperable stack.