Overview
Learn how Agent Gateway publishes approved Commerce Graph data through structured data, read-only AI access, feeds, and partner exports.
- Approved public output exposes approved public data only.
- Client-domain publishing depends on configured domains and output health.
- Partner exports are distinct from public output and can require configured access.
What Agent Gateway means in Akii
Agent Gateway 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
Agent Gateway publishes the outputs allowed by the client graph and its settings. These can include JSON, JSON-LD, summaries, protocol status, UCP-style profiles, A2A Agent Cards, MCP-compatible access, AP2 readiness, and Agent UI payloads.
- 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.
- Does not expose private fields through approved public output.
- Does not guarantee third-party platform ingestion.
- Does not turn a handoff into payment or booking completion.