AkiiAkii
  • Platform
    Commerce GraphKeep services, offers, rules, and sources in one approved place.Agent GatewayPublish the facts AI and partner systems are allowed to read.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 CompatibilityCheck readiness for ACP, UCP, MCP, A2A, AP2, and agent UI flows.ACP ReadinessCheck seller facts, prices, rules, offers, and next steps.
  • Resources
    Solutions overviewStart with the client problem, then see the Akii page built for it.DocsRead practical guides for Commerce Graph, Agent Gateway, and readiness.BlogPractical notes on client data, buyer paths, and AI. No prophecy required.FAQStraight answers for buyers, teams, agencies, and partners.ResearchNotes on agent commerce, action paths, checks, and sources.
  • Company
    AboutSee what Akii is building, why it exists, and who is behind it.ContactTell Akii what you are trying to fix.
  • Pricing
LoginContactSign up
AkiiAkii

Platform

Commerce GraphKeep services, offers, rules, and sources in one approved place.Agent GatewayPublish the facts AI and partner systems are allowed to read.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 CompatibilityCheck readiness for ACP, UCP, MCP, A2A, AP2, and agent UI flows.ACP ReadinessCheck seller facts, prices, rules, offers, and next steps.

Resources

Solutions overviewStart with the client problem, then see the Akii page built for it.DocsRead practical guides for Commerce Graph, Agent Gateway, and readiness.BlogPractical notes on client data, buyer paths, and AI. No prophecy required.FAQStraight answers for buyers, teams, agencies, and partners.ResearchNotes on agent commerce, action paths, checks, and sources.

Company

AboutSee what Akii is building, why it exists, and who is behind it.ContactTell Akii what you are trying to fix.
Sign up
PricingContact
Login
Home/Docs/Protocol Compatibility
Core Platform

Updated 2026-07-22

Prepare client data for AI commerce standards.

Protocol Compatibility checks whether client data, publishing settings, policies, and action paths are ready for protocol-style flows while keeping certification and payment boundaries clear.

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 iconA2UI

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
  • What another agent can see
  • 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

  • Run Akii across client accounts
  • Client onboarding for agencies
  • Manage multiple client brands
  • Client reports
  • Fix Queue workflows for agencies
  • Reselling and packaging Akii
  • Onboard clients and share approved outputs
  • Batch client onboarding
  • Protocol exports
  • Partner readiness reports

Use Cases

  • Find the clients Akii fits best
  • Ecommerce and complex catalogs
  • Service businesses with complex buyer paths
  • Local businesses
  • B2B quote and inquiry journeys
  • 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
  • Give each role only the access it needs
  • 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

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.

Related docs

AI commerce protocols

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

Protocol comparison

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

Safe protocol claims and certifications

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

Previous
Action Registry
Next
Answer QA

On this page

  • Overview
  • What Protocol Compatibility means in Akii
  • How it works
  • Boundaries
Akii

Akii turns scattered client details into one approved Commerce Graph. AI systems can read the facts, and Answer QA can catch what they get wrong. AI has enough to guess at already.

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