CAIN-42 MCPGateAGENTIC AI 75 · #47
Universal commerce protocol
Google launched a standard spanning shopping discovery, purchase and post-purchase support.
Last reviewed 2026-11-11
Agentic AI 75 / #47
2026 status: Standards launch · Category: Commerce
The 2026 development
Google launched a standard spanning shopping discovery, purchase and post-purchase support.
The governance gap
A protocol that spans discovery to post-purchase also spans several authorities: browsing, payment, returns and data use. One session identity must not silently become all four.
Where CAIN-42 fits: Moat 2 — Security-Context Continuity
Core question: Does authority survive every boundary? Identity, scope and delegation are carried across tools, agents, memories and systems.
Scope each phase of the transaction separately and carry the purchase mandate only into the phases that need it. Discovery gets read scope; payment gets a bounded mandate; post-purchase gets order scope.
How the wiring works
- Issue phase-specific scopes rather than one session-wide grant.
- Carry the payment mandate only into checkout.
- Enforce merchant, amount and velocity limits at payment.
- Record the handoff between phases.
What is real today
PROPOSED A design mapping only. No dedicated implementation exists yet; do not buy this as a finished control.
No universal-commerce protocol implementation exists here. The mandate guard is real and useful for the payment phase only.
| Component in this repository | What the module says it is |
|---|---|
cain/commerce/mandate_guard.py | Agent Payment Mandate Guard. |
cain/runtime/transactions.py | CAIN Sovereign — Machine-to-Machine Transaction Governance (Prompt 7, Phase 18). |
cain/interop/commerce.py | Evolution 17 — verifiable agent-to-agent commerce: cryptographically governed |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Run the live payment-mandate demo
/api/v1/payment-mandate-guard/presets - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Commerce Protocol Authority Review |
|---|---|
| Buyer | Commerce platforms and standards bodies |
| Price (proposal) | Advisory from $10,000 |
| Bundle | Commerce & Payments — Delegated spending with a ceiling and a receipt. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
Fintech, commerce platforms, marketplaces, treasury teams is the bundle buyer. The entry offer for this bundle is Payment-mandate review; browser-agent checkout review; the range is $2,500–$7,500 per review; integration from $10,000. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-047 — Commerce Protocol Authority Review DESIGN
A design-partner statement of work and architecture: authority boundaries, evidence points, and a build plan. No control is delivered and no integration is claimed.
Kind: Assessment · Price (proposal): Advisory from $10,000 · Lead time: 15 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.