Overview
Universal Commerce Protocol documentation for Akii support boundaries, setup, approved outputs, readiness, safety limitations, and related docs.
- Gives clients and platforms a structured way to expose commerce capabilities instead of relying on scraped pages.
- Akii support today: UCP-style client profile output for approved Commerce Graphs; UCP readiness validation; Client-domain profile discovery where configured.
- Akii does not do: Google UCP certification; Native checkout execution; Payment-handler operation.
This page is marked Partial. Treat the content as an implementation boundary, not a certification, production support guarantee, or platform partnership claim.
What Universal Commerce Protocol does
Defines commerce primitives for AI surfaces and commerce providers, including merchant-controlled transaction and capability flows.
- Client profile and capabilities
- Offer, catalog, checkout, fulfillment, policy, and post-purchase data where applicable
- Capability extensions and transport bindings such as REST, MCP, or A2A
What Akii supports today
Akii documents support by implementation status: supported, partial, readiness, export, planned, watchlist, or requires verification.
- UCP-style client profile output for approved Commerce Graphs
- UCP readiness validation
- Client-domain profile discovery where configured
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.
- Google UCP certification
- Native checkout execution
- Payment-handler operation
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 UCP-style profiles as external certification.
- Do not imply a formal Google platform partnership.
- Do not present Akii as the checkout executor.