Seller identity fields
Track seller identity, offer terms, accepted handoff types, deposit requirements, and policy summaries.
Agent commerce readiness
Prepare client facts for AI commerce handoffs.
ACP Readiness checks whether seller identity, offers, policies, prices, deposits, availability, and handoff paths are clear enough for ACP-style flows while checkout stays in client-owned systems.
6
Readiness areas
Seller, offer, price, policy, action, source evidence
Approved
Customer handoff
Data preparation and routing only
Needs review
Review state
Missing fields and warnings are tracked before export
Seller identity
Price and deposit clarity
Client-owned checkout
Platform layer
What this part of Akii actually does
Each part has one job: make client facts, buyer paths, or checks clear enough for AI and people to use.
Readiness checklist
Flag missing fields before partners or agents depend on an approved Commerce Graph.
Client-owned checkout
Akii prepares the verified data and approved handoff path. The final booking, deposit, or checkout stays with the client or approved provider.
Exportable review
Share readiness gaps with agencies, clients, and partners before commercial action paths are exposed.
Workflow
Check the handoff without claiming more than that
Start with the client facts as they are. Turn them into approved data, clear customer paths, checks, and fixes.
1
Readiness inventoryRead graph and actions
Review seller, offer, policy, price, deposit, and handoff fields from the approved graph and Action Registry.
2
Missing-fields tableFind missing fields
Flag unavailable terms, unclear deposits, missing cancellation policy, unsupported handoffs, and source gaps.
3
Boundary reviewSeparate claims from scope
Mark what Akii can represent as data and what must remain with the client, partner, or payment provider.
4
Readiness exportExport partner view
Share readiness status, warnings, and required fixes without making payment-processing claims.
How it works
Readiness checks
The inputs and outputs stay visible, so the agency, client, and AI systems can use the same approved facts.
| Area | Input | Output |
|---|---|---|
| Seller identity | Legal or trading name, location, contact, service region | Client identity status |
| Offer terms | Price, duration, eligibility, inclusions, exclusions, package constraints | Offer readiness status |
| Policy clarity | Deposit, cancellation, refund, arrival, group size, booking terms | Warnings and missing fields |
| Handoff boundary | Booking provider, form, phone, WhatsApp, payment link, partner route | Approved handoff status without processing claims |
Use cases
Where it is used
Partner readiness review
Partners can see whether a client has the fields needed before listing, export, or handoff.
Client cleanup
Operators get a practical list of missing policies, prices, deposits, sources, and action details.
Claim control
The system keeps Akii outputs focused on verified data and approved handoffs instead of claiming to replace client-owned systems.
Straight answers
The practical questions agencies and partners ask before they put Akii to work for a client.
Does ACP Readiness mean the client can accept agent payments through Akii?
No. It means the required data, policy, and handoff fields are prepared and reviewed. Checkout and booking completion stay with the client or approved provider.
Can readiness be exported?
Yes. Readiness reports can be shared with agencies, clients, partners, and operators with warnings and missing fields.
What happens when a field is missing?
It is flagged for review and can become a fix task before the graph, endpoint, or partner output is trusted.
Start with one client whose facts need work.
Structure what the business sells, publish approved outputs, and test whether AI can find the right facts and customer path.