OpenAI / Stripe Agentic Commerce Protocol
OpenAI / Stripe ACP readiness
Readiness, validation, and ACP-style merchant data export only.
Akii does not process payments, handle Shared Payment Tokens, or claim ACP certification.
Protocol Compatibility
Prepare your business for the standards AI platforms are adopting.
Akii checks whether your business has the structured data, policies, actions, and access points needed for ACP-style, UCP-style, MCP, A2A, AP2, and agent UI flows without making certification claims or replacing merchant-owned checkout systems.
Compatibility, not false certification
Akii does not claim certification or formal partnership with these platforms unless explicitly stated. Akii prepares and validates the business-side data, access, action, and readiness layer those standards increasingly require.
Checkout stays with business-owned systems
Customer actions route to approved handoff paths
Read-only MCP by default
Public endpoints expose approved graph data only
Unsupported protocols stay watchlist-only
Google Universal Commerce Protocol
Google UCP profile readiness
UCP-style merchant profile, capability export, and readiness validation.
Akii does not claim UCP certification or a formal Google partnership.
Model Context Protocol
Read-only MCP tools
Read-only MCP-compatible tools over approved Commerce Graph data.
MCP tools are read-only by default and do not complete transactions.
Agent2Agent Protocol
A2A Agent Card readiness
A2A-style Agent Card discovery and safe merchant capability exposure.
Akii exposes discovery and handoff capabilities, not autonomous execution.
Agent Payments Protocol
AP2 payment-readiness report
Payment-policy and handoff readiness reporting without payment execution.
Akii does not issue mandates, sign payment credentials, store tokens, or execute payments.
AG-UI
AG-UI payload exports
Structured offer/action payloads for agent-user interface renderers.
Akii exports safe JSON payloads only; no arbitrary code execution.
A2UI
A2UI payload exports
Declarative offer/action UI payloads for agent-driven interfaces.
Akii exports declarative JSON only and labels partial mappings honestly.
What Akii checks before AI relies on it
Protocol Compatibility is backed by approved business data, customer action paths, AI-readable access, readiness reports, defects, fixes, and safe evidence.
Business identity, seller display name, domain, and support path
Offers, prices or price ranges, currencies, availability sources, and policies
Approved booking, quote, checkout, deposit, WhatsApp, call, and partner handoffs
Read-only MCP tools and protocol compatibility status
UCP-style profiles, A2A-style Agent Cards, and structured UI payload exports
AP2 checkout-handoff fields with merchant-owned completion
Watchlist protocols
These are tracked for strategic awareness, but Akii does not present them as active product support until the implementation and use case are real.
BeeAI ACP watchlist
Watchlist only; route practical support through A2A compatibility.
ANP watchlist
Watchlist only for future decentralized agent discovery.