Overview
How Akii describes client capabilities and safe handoffs for agent discovery where configured.
- Approved public output contains only reviewed Commerce Graph data.
- Partner exports require configured access where implemented.
- Read-only access stays separate from booking, payment, and data changes.
Access boundary
Akii separates approved public output, configured partner access, and private account work. Public docs describe the boundary without exposing private workspace routes.
What customers should know
Approved outputs can help AI tools and partners read client facts, offers, policies, reviews, and next steps. They should never include secrets, private notes, or unapproved work.
Approval and version safety
Akii separates unapproved work from approved and published output so public consumers do not read data that has not been reviewed.
Availability and limits
Publishing surfaces can be unavailable, disabled, or limited. Customers and partners should treat that as a signal to review setup, permissions, or readiness before relying on the output.
Publishing reference
| Surface | Access | Mode | Boundary |
|---|---|---|---|
| A2A-style Agent Card | Published only when enabled | Read-only publishing surface | No private notes, secrets, unapproved work, or account workspace data. |
| Read-only client operations | Published only when enabled | Read-only requests where enabled | No private notes, secrets, unapproved work, or account workspace data. |