Overview
OpenAI Agentic Commerce Protocol documentation for Akii support boundaries, setup, approved outputs, readiness, safety limitations, and related docs.
- Reduces ambiguity between an AI answer and the client checkout or approved action path.
- Akii support today: ACP-style readiness checks over Commerce Graph fields; Seller, offer, policy, price, deposit, and action-path completeness; Evidence-backed readiness report and recommended fixes.
- Akii does not do: Payment processing; Shared Payment Token storage; Certification or formal ACP compliance claim.
This page is marked Readiness. Treat the content as an implementation boundary, not a certification, production support guarantee, or platform partnership claim.
What OpenAI Agentic Commerce Protocol does
Supports agentic commerce flows where products, offers, seller identity, policies, and payment handoff details can be evaluated by agentic surfaces.
- Seller identity clarity
- Products, services, offers, prices, availability, and policies
- Checkout, deposit, booking, or provider handoff targets
- Refund, cancellation, fulfillment, and customer-support rules
What Akii supports today
Akii documents support by implementation status: supported, partial, readiness, export, planned, watchlist, or requires verification.
- ACP-style readiness checks over Commerce Graph fields
- Seller, offer, policy, price, deposit, and action-path completeness
- Evidence-backed readiness report and recommended fixes
Setup instructions
Start from an approved Commerce Graph, resolve missing client identity, offer, policy, source, publishing, and action-path fields, then enable only the public output or export surfaces that are implemented for the client brand.
- Confirm the client brand has approved identity, website, locations, offers, policies, and action paths.
- Run the relevant Protocol Compatibility check and resolve missing required fields before publishing.
- Enable public data publishing, MCP-compatible access, Agent Card output, UCP profile output, AP2 readiness output, Agent UI payloads, or JSON-LD only when the agency or client owner has approved that public surface.
- Run Answer QA after enabling the output and record any issues in Fix Queue.
What Akii does not do
These boundaries are part of the public claim. Do not collapse readiness into certification or a data export into a live platform partnership.
- Payment processing
- Shared Payment Token storage
- Certification or formal ACP compliance claim
Safety note
Akii does not claim certification or formal partnership with protocol maintainers unless explicitly stated. Akii prepares, validates, and exposes the client-side data and action layer those systems increasingly require.
- Do not describe readiness as external certification.
- Do not imply payment-token storage or live payment execution.
- Do not present Akii as the client checkout or payment-execution system.