Overview
Map customer actions such as buy, book, inquire, request quote, call, WhatsApp, deposit, submit form, and checkout to approved paths.
- Action paths can represent buy, book, inquire, quote, call, WhatsApp, deposit, form, checkout, or fallback paths.
- Each path can carry provider, device, market, language, authentication, safe-test, approval, priority, and test status.
- Akii validates handoff paths; it does not silently complete transactions.
What Action Registry means in Akii
Action Registry 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
Operators connect offers, packages, services, and buyer intents to the right destination. Answer QA can then test whether the path still works and whether public claims point to the same next step.
- 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.
- Payment and booking completion stay with approved providers.
- Fallback actions should be explicit, not guessed by an AI answer.
- Broken or untested action paths should be treated as issues before publication.