Canonical public endpoints
Expose the approved client profile, locations, offers, actions, policies, sources, and MCP-compatible access from one trusted version.
Agent Gateway publishes approved client data through endpoints, feeds, JSON-LD, read-only MCP access, and partner exports. No scavenger hunt across scattered pages.
Each part has one job: make client facts, buyer paths, or checks clear enough for AI and people to use.
Expose the approved client profile, locations, offers, actions, policies, sources, and MCP-compatible access from one trusted version.
Agent tools retrieve approved client facts, action paths, policies, source URLs, and booking options without mutating systems.
Export graph slices and readiness reports to partners, agencies, platforms, and internal teams by client and version.
Track whether AI-readable access is available, current, and returning the approved business facts.
Start with the client facts as they are. Turn them into approved data, clear customer paths, checks, and fixes.
Choose the approved Commerce Graph version that should power public and partner outputs.
Enable Akii-hosted JSON, client-domain publishing, partner feeds, and read-only MCP as needed.
Check schema, availability, freshness, and field visibility before AI systems or partners depend on it.
Review endpoint and MCP activity with timestamps, response status, client, and tool context.
The inputs and outputs stay visible, so the agency, client, and AI systems can use the same approved facts.
| Area | Input | Output |
|---|---|---|
| JSON endpoints | Approved graph version and public field set | Stable machine-readable URLs |
| MCP tools | Tool definitions for client profile, offers, actions, policies, and sources | Read-only agent tool surface |
| Partner feeds | Partner assignment, export scope, graph version, field visibility | Partner-ready slices and readiness reports |
| Monitoring | Response status, schema checks, latency, stale-version signals | Access and freshness timeline |
Give AI systems a predictable endpoint family that represents the approved client profile.
Expose approved business facts through a read-only tool catalog that can be inspected and logged.
Share the right client graph slice with agencies, platforms, and commerce partners without manual exports.
The practical questions agencies and partners ask before they put Akii to work for a client.
Yes. Akii supports Akii-hosted endpoints and client-domain publishing where DNS and verification are configured.
Yes. Partner outputs can be scoped by client, graph version, field visibility, and readiness state.
No. The v2 MCP surface is read-only and built for retrieval, inspection, and evidence-backed answers.
Structure what the business sells, publish approved outputs, and test whether AI can find the right facts and customer path.