Overview
Agent2Agent Protocol documentation for Akii support boundaries, setup, approved outputs, readiness, safety limitations, and related docs.
- Allows another system to understand what a client-facing agent can read or hand off safely.
- Akii support today: A2A-style Agent Card output; Read-only client operations for profile, offers, policies, actions, and sources; Explicit unsupported transaction operations.
- Akii does not do: Autonomous transaction execution; Unauthorized booking or lead submission; Official certification claim.
This page is marked Partial. Treat the content as an implementation boundary, not a certification, production support guarantee, or platform partnership claim.
What Agent2Agent Protocol does
Defines discovery and interaction patterns for agents, including agent cards and supported capabilities.
- Agent Card metadata
- Capabilities and supported operations
- Public output URL and safety limits
- Structured client and action-path payloads
What Akii supports today
Akii documents support by implementation status: supported, partial, readiness, export, planned, watchlist, or requires verification.
- A2A-style Agent Card output
- Read-only client operations for profile, offers, policies, actions, and sources
- Explicit unsupported transaction operations
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.
- Autonomous transaction execution
- Unauthorized booking or lead submission
- Official certification 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 present A2A-style discovery as autonomous transaction execution.
- Do not describe A2A-style support as external certification.