Overview
Understand the protocol landscape around ACP, UCP, MCP, A2A, AP2, AG-UI, A2UI, Schema.org, and Google structured data.
- MCP support is read-only over approved Commerce Graph data.
- ACP and AP2 are readiness-oriented; payment execution is outside Akii.
- UCP, A2A, AG-UI, and A2UI support depends on configured public outputs and graph completeness.
How to read protocol support
Akii uses support labels carefully. Supported means implemented in the product. Partial means a profile, output, or operation exists but does not represent full protocol certification. Readiness means Akii checks and prepares required data. Export means Akii emits structured payloads without claiming native platform execution.
Protocol logos and sources
Protocol pages use protocol/source-specific icons from the official source domains and link to the primary documentation used for public claims.
Protocol support overview
| Protocol | Purpose | Akii support | Status | Docs |
|---|---|---|---|---|
| OpenAI Agentic Commerce Protocol | Reduces ambiguity between an AI answer and the client checkout or approved action path. | Akii prepares client data for ACP-style flows and payment-handoff readiness. | readiness | /docs/protocols/acp |
| Universal Commerce Protocol | Gives clients and platforms a structured way to expose commerce capabilities instead of relying on scraped pages. | Akii prepares UCP-style client profiles and readiness evidence. | partial | /docs/protocols/ucp |
| Model Context Protocol | Lets AI clients query approved client data through a stable tool contract instead of scraping arbitrary pages. | Akii exposes approved Commerce Graph data through read-only MCP-compatible tools. | supported | /docs/protocols/mcp |
| Agent2Agent Protocol | Allows another system to understand what a client-facing agent can read or hand off safely. | Akii exposes A2A-style discovery and safe client read/handoff capabilities. | partial | /docs/protocols/a2a |
| Agent Payments Protocol | Clarifies how intent, authorization, payment credentials, and seller accountability should be handled when agents are involved. | Akii prepares client-side payment-handoff readiness for AP2-style flows. | readiness | /docs/protocols/ap2 |
| AG-UI | Gives UI surfaces a predictable way to render agent output and state updates. | Akii can export structured Agent UI payloads for approved commerce actions. | export | /docs/protocols/ag-ui-a2ui |
| A2UI | Lets agents describe useful UI cards and forms while keeping renderer control with the client application. | Akii can emit declarative A2UI-style commerce payloads for approved data. | export | /docs/protocols/ag-ui-a2ui |
| Schema.org and Google structured data | Helps crawlers and search systems parse business, product, offer, and organization information from rendered web pages. | Akii can publish JSON-LD-style structured outputs from approved client data. | supported | /docs/schemas |