OpenAI ACP readiness
Readiness, validation, and ACP-style merchant data export only.
Akii does not process payments, handle Shared Payment Tokens, or claim ACP certification.
Akii checks each client's data and action paths for ACP-style, UCP-style, MCP, A2A, AP2, and agent UI flows. It does not claim certification. It does not replace client-owned checkout systems.
Akii does not claim certification unless we state it. It does not claim partnership unless we state it. It prepares client data, access, actions, and readiness for those standards.
Readiness, validation, and ACP-style merchant data export only.
Akii does not process payments, handle Shared Payment Tokens, or claim ACP certification.
UCP-style merchant profile, capability export, and readiness validation.
Akii does not claim UCP certification or a formal Google partnership.
Read-only MCP-compatible tools over approved Commerce Graph data.
MCP tools are read-only by default and do not complete transactions.
A2A-style Agent Card discovery and safe merchant capability exposure.
Akii exposes discovery and handoff capabilities, not autonomous execution.
Payment-policy and handoff readiness reporting without payment execution.
Akii does not issue mandates, sign payment credentials, store tokens, or execute payments.
Structured offer/action payloads for agent-user interface renderers.
Akii exports safe JSON payloads only; no arbitrary code execution.
Declarative offer/action UI payloads for agent-driven interfaces.
Akii exports declarative JSON only and labels partial mappings honestly.
Protocol Compatibility uses approved client data and action paths. It checks AI-readable access, reports, fixes, and safe evidence.
These are tracked for strategic awareness, but Akii does not present them as active product support until the implementation and use case are real.
Watchlist only; route practical support through A2A compatibility.
Watchlist only for future decentralized agent discovery.