AkiiAkii
  • Platform
    Commerce GraphKeep offers, rules, hours, and sources in one trusted place.Agent GatewayGive AI and partner systems a clean, approved way to read each client.Action RegistryMap each offer to the right booking, quote, call, WhatsApp, or checkout path.Answer QACatch wrong facts and broken customer paths before they cost demand.Protocol CompatibilityPrepare client data for ACP, UCP, MCP, A2A, AP2, and agent UI flows.ACP ReadinessCheck seller details, prices, rules, offers, and next steps.
  • Resources
    Solutions overviewStart with common agency client needs, then open the main platform pages.DocsRead practical guides for Commerce Graph, Agent Gateway, and readiness.BlogPlain notes on AI commerce, business data, and daily work.FAQShort answers for buyers, teams, agencies, and partners.ResearchNotes on agent commerce, action paths, checks, and sources.
  • Company
    AboutLearn what Akii is building and where the company fits.ContactReach Akii for sales, support, partnership, or account questions.
  • Pricing
LoginContactSign up
AkiiAkii

Platform

Commerce GraphKeep offers, rules, hours, and sources in one trusted place.Agent GatewayGive AI and partner systems a clean, approved way to read each client.Action RegistryMap each offer to the right booking, quote, call, WhatsApp, or checkout path.Answer QACatch wrong facts and broken customer paths before they cost demand.Protocol CompatibilityPrepare client data for ACP, UCP, MCP, A2A, AP2, and agent UI flows.ACP ReadinessCheck seller details, prices, rules, offers, and next steps.

Resources

Solutions overviewStart with common agency client needs, then open the main platform pages.DocsRead practical guides for Commerce Graph, Agent Gateway, and readiness.BlogPlain notes on AI commerce, business data, and daily work.FAQShort answers for buyers, teams, agencies, and partners.ResearchNotes on agent commerce, action paths, checks, and sources.

Company

AboutLearn what Akii is building and where the company fits.ContactReach Akii for sales, support, partnership, or account questions.
Sign up
PricingContact
Login
Home/Docs/AI commerce protocols/Protocol comparison
Protocol Compatibility

Updated 2026-07-07

Protocol comparison

Use this page to evaluate which Akii output maps to which protocol-style need.

OpenAI Agentic Commerce Protocol iconOpenAI Agentic Commerce ProtocolUniversal Commerce Protocol iconUniversal Commerce ProtocolModel Context Protocol iconModel Context ProtocolAgent2Agent Protocol iconAgent2Agent ProtocolAgent Payments Protocol iconAgent Payments ProtocolAG-UI iconAG-UIA2UI iconA2UISchema.org and Google structured data iconSchema.org and Google structured data

Start Here

  • Akii Documentation
  • Getting started with Akii
  • What is Akii?
  • Core concepts
  • Glossary

Core Platform

  • Commerce Graph
  • Agent Gateway
  • Action Registry
  • Protocol Compatibility
  • Answer QA
  • Monitoring
  • Fix Queue
  • Sources

Protocol Compatibility

  • AI commerce protocols
  • Agentic Commerce Protocol readiness
  • Universal Commerce Protocol readiness
  • Model Context Protocol support
  • Agent2Agent support
  • Agent Payments Protocol readiness
  • Agent UI payloads
  • Protocol comparison
  • Safe protocol claims and certifications

Publishing and Partner Access

  • Publishing overview
  • Access boundaries
  • Commerce Graph publishing
  • Approved data publishing
  • Read-only AI access
  • Agent discovery profile
  • UCP-style client profile
  • Exports
  • Availability and access messages
  • Traffic limits
  • Versioning

Implementation Guides

  • Create your first Commerce Graph
  • Publish your Agent Gateway
  • Map customer action paths
  • Run Answer QA
  • Configure protocol compatibility
  • Set up MCP access
  • Create an A2A Agent Card
  • Prepare for ACP-style flows
  • Prepare for UCP-style flows
  • Monitor drift
  • Manage fixes

Agencies and Partners

  • Agency guide
  • Client onboarding for agencies
  • Manage multiple client brands
  • Client reports
  • Fix Queue workflows for agencies
  • Reselling and packaging Akii
  • Partner guide
  • Batch client onboarding
  • Protocol exports
  • Partner readiness reports

Use Cases

  • Use cases
  • Ecommerce and complex catalogs
  • Service businesses
  • Local businesses
  • B2B companies
  • Hospitality
  • Wellness and clinics
  • Venues and events
  • Tours and experiences
  • Marketplaces
  • Multi-location brands

Security and Compliance

  • Security overview
  • Data handling
  • Public vs private data
  • MCP security
  • Payment boundaries
  • Roles and access
  • Audit logs
  • Certification and platform-claim rules

Reference

  • Reference
  • Entities
  • Commerce Graph schema
  • Action types
  • Protocol statuses
  • Issues
  • Readiness statuses
  • Plan limits
  • FAQ
  • Changelog
  • Schemas

Overview

Compare protocols by purpose, client data required, Akii support type, output/export, safety limitations, and official source.

  • Readiness is not certification.
  • Payment execution is not supported by Akii.
  • Protocol pages link to official sources.
  • Akii separates profile output, read-only tool access, readiness checks, action handoffs, and UI payload exports.

Comparison rules

The table distinguishes purpose, data required, Akii support type, current support status, output/export, safety limitations, and official source.

How to read support status

Supported means Akii has implemented the related product or output surface. Readiness means Akii checks whether client data and handoff paths are prepared for a protocol-style flow. Export means Akii can produce scoped output where configured. Planned and watchlist entries must not be sold as live support.

Where partners should start

Partners should begin with the protocol page for the surface they care about, then review the related publishing page and safety boundary. A partner evaluating commerce profiles should start with UCP. A tool integration should start with MCP. A protocol-readiness review should start with ACP, AP2, or the comparison table.

Claims boundary

Do not describe Akii readiness as third-party certification. Do not say Akii is formally partnered with a protocol owner unless the docs state that explicitly. Do not imply Akii processes payments, stores card data, stores payment tokens, or completes bookings. The comparison exists to make those boundaries visible before a page, report, or partner export is used.

Protocol matrix

ProtocolPurposeClient data requiredAkii support typeCurrent statusOutput/exportSafety limitationsOfficial source
OpenAI Agentic Commerce ProtocolReduces ambiguity between an AI answer and the client checkout or approved action path.Seller identity clarity; Products, services, offers, prices, availability, and policies; Checkout, deposit, booking, or provider handoff targets; Refund, cancellation, fulfillment, and customer-support rulesAkii prepares client data for ACP-style flows and payment-handoff readiness.readiness/docs/protocols/acpPayment processing; Shared Payment Token storage; Certification or formal ACP compliance claimhttps://developers.openai.com/commerce/guides/get-started
Universal Commerce ProtocolGives clients and platforms a structured way to expose commerce capabilities instead of relying on scraped pages.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 A2AAkii prepares UCP-style client profiles and readiness evidence.partial/docs/protocols/ucpGoogle UCP certification; Native checkout execution; Payment-handler operationhttps://ucp.dev/
Model Context ProtocolLets AI clients query approved client data through a stable tool contract instead of scraping arbitrary pages.Tool names and schemas; Structured tool responses; Approved client, offer, location, policy, source, and action dataAkii exposes approved Commerce Graph data through read-only MCP-compatible tools.supported/docs/protocols/mcpTransactional MCP tools; Unapproved private graph data exposure; Arbitrary tool executionhttps://modelcontextprotocol.io/specification/2025-11-25
Agent2Agent ProtocolAllows another system to understand what a client-facing agent can read or hand off safely.Agent Card metadata; Capabilities and supported operations; Public output URL and safety limits; Structured client and action-path payloadsAkii exposes A2A-style discovery and safe client read/handoff capabilities.partial/docs/protocols/a2aAutonomous transaction execution; Unauthorized booking or lead submission; Official certification claimhttps://a2a-protocol.org/latest/
Agent Payments ProtocolClarifies how intent, authorization, payment credentials, and seller accountability should be handled when agents are involved.Seller identity; Checkout and payment-handoff readiness; Refund, cancellation, deposit, fulfillment, and support policies; Evidence that payment execution is handled by an approved providerAkii prepares client-side payment-handoff readiness for AP2-style flows.readiness/docs/protocols/ap2Payment mandate issuance; Payment token handling; Card data storage; Payment executionhttps://ap2-protocol.org/
AG-UIGives UI surfaces a predictable way to render agent output and state updates.Structured offer, service, package, and action payloads; Safe UI state and handoff targets; Declarative payloads that avoid arbitrary code executionAkii can export structured Agent UI payloads for approved commerce actions.export/docs/protocols/ag-ui-a2uiArbitrary runtime UI code generation; Guaranteed renderer compatibility across every AG-UI clienthttps://docs.ag-ui.com/introduction
A2UILets agents describe useful UI cards and forms while keeping renderer control with the client application.Declarative card and form payloads; Commerce entity fields; Approved handoff and action target metadataAkii can emit declarative A2UI-style commerce payloads for approved data.export/docs/protocols/ag-ui-a2uiA formal A2UI certification claim; Client-side renderer shipping as part of public docshttps://a2ui.org/introduction/what-is-a2ui/
Schema.org and Google structured dataHelps crawlers and search systems parse business, product, offer, and organization information from rendered web pages.Organization, LocalBusiness, Product, Offer, Service, Store, and policy fields; JSON-LD output that matches visible page content; Accurate pricing, availability, review, return, and seller information where usedAkii can publish JSON-LD-style structured outputs from approved client data.supported/docs/schemasGuaranteed rich result eligibility; Manual-action immunity; Search ranking guaranteeshttps://schema.org/

Official sources

OpenAI Agentic Commerce ProtocolUniversal Commerce ProtocolModel Context ProtocolAgent2Agent ProtocolAgent Payments ProtocolAG-UIA2UISchema.org and Google structured data

Related docs

AI commerce protocols

Understand the protocol landscape around ACP, UCP, MCP, A2A, AP2, AG-UI, A2UI, Schema.org, and Google structured data.

Safe protocol claims and certifications

Understand readiness versus certification, support versus partnership, export versus integration, and safe public language.

Previous
Agent UI payloads
Next
Safe protocol claims and certifications

On this page

  • Overview
  • Comparison rules
  • How to read support status
  • Where partners should start
  • Claims boundary
  • Protocol matrix
Akii

Akii helps agencies turn scattered service-business client details into data AI chatbots can read. ChatGPT, Gemini, Claude, and Perplexity can compare the client clearly and guide customers to the right next step.

Platform

  • Commerce Graph
  • Agent Gateway
  • Action Registry
  • Protocol Compatibility
  • ACP Readiness
  • Answer QA

Solutions

  • Solutions overview

Resources

  • Docs
  • Blog
  • FAQ
  • Research

Company

  • About
  • Contact
  • Privacy
  • Terms

Account

  • Sign up
  • Login
  • Pricing

© 2026 Akii Technologies, Ltd. All rights reserved.

CookiesPreferences