Overview
Understand readiness versus certification across ACP, UCP, MCP, A2A, AP2, AG-UI, and A2UI.
- Readiness is not certification.
- Exports are not the same as live platform integration.
- Akii supports read-only MCP and several readiness/export surfaces, but does not process payments.
What Protocol Compatibility means in Akii
Protocol Compatibility is documented as part of Akii v2 only: Commerce Graph, Agent Gateway, Action Registry, Protocol Compatibility, Answer QA, monitoring, sources, fixes, and Partner Console operations. The page explains the operational role, not a generic marketing claim.
How it works
Akii validates the Commerce Graph against protocol-specific requirements, reports missing fields, prepares supported profile or readiness output, and records what remains platform- or partner-dependent.
- Start from approved client data instead of scraped fragments.
- Keep public and private data boundaries explicit.
- Attach evidence, owner, status, and version context where the product supports it.
- Retest after changes so issues and readiness gaps do not become stale.
Boundaries
Akii documents what is supported, partial, readiness-only, export-only, planned, or watchlist. Do not treat readiness as certification or exports as full partner integration.
- Akii does not claim formal OpenAI, Stripe, Google, UCP, ACP, A2A, AP2, AG-UI, or A2UI certification.
- Payment processing, token storage, and mandate issuance are outside Akii.
- Unsupported protocol watchlist items should not be sold as production support.