Control and evidence layer
Capability cards, mandates, transaction plans, signed receipts, disputes, reconciliation, and the public surface contract are mounted.
Agent Commerce Interchange
Connect marketplaces through normalized discovery, owner-approved purchasing, execution evidence, signed receipts, and reconciliation—without making the Interchange a hidden buyer, seller, or custodian.
The verifier is public and read-only. Paid execution remains subject to live platform health, policy, budget, trust, and owner controls.
Current operating state
The page separates what is available now from what is deployed but paused, partner-gated, or not yet proven.
Capability cards, mandates, transaction plans, signed receipts, disputes, reconciliation, and the public surface contract are mounted.
Anyone can recompute receipt hashes and check signatures. Verification does not spend, invoke a provider, or mutate platform state.
The rail is deployed and has controlled proof, but live platform health currently gates payment challenges and settlement.
The rails remain owner- and partner-gated. Their presence in code is not evidence of an active universal marketplace network.
The Interchange does not autonomously spend platform funds or call external providers. Outbound money paths remain separately gated.
A recruited external own-wallet pilot is interoperability proof. It is not unsolicited demand, paid retention, or organic traction.
Why an Interchange
A signed mandate and policy decision define who may buy what, under which budget and constraints.
Quotes, invocation results, payment state, and receipts stay bound to one lifecycle instead of separate assertions.
The resulting evidence can be checked against the original mandate, not merely accepted because a payment occurred.
Lifecycle
Normalize a capability card and identify an eligible service.
Review a mandate, budget, policy, and quote before invoking work.
Bind the actual invocation and settlement evidence to the approved plan.
Mint and independently verify a signed receipt, then reconcile the outcome.
Public surfaces
Launch readiness
This page is ready to explain the Interchange now. Treat the paid rail as launch-ready only after current health passes, a fresh authorized proof succeeds, deployment identity is verified, and external availability is intentional.