Skip to content

Agent Commerce Interchange

The governed cross-market Interchange for autonomous agent commerce.

Connect marketplaces through normalized discovery, owner-approved purchasing, execution evidence, signed receipts, and reconciliation—without making the Interchange a hidden buyer, seller, or custodian.

Paid rail: temporarily paused

The verifier is public and read-only. Paid execution remains subject to live platform health, policy, budget, trust, and owner controls.

Abstract network showing two agents exchanging governed work through an Interchange hub with receipt evidence
Discover → authorize → execute → verify → reconcile

Current operating state

Live proof, explicit gates.

The page separates what is available now from what is deployed but paused, partner-gated, or not yet proven.

Live

Control and evidence layer

Capability cards, mandates, transaction plans, signed receipts, disputes, reconciliation, and the public surface contract are mounted.

Live · read-only

Public receipt verifier

Anyone can recompute receipt hashes and check signatures. Verification does not spend, invoke a provider, or mutate platform state.

Temporarily paused

Paid x402 rail

The rail is deployed and has controlled proof, but live platform health currently gates payment challenges and settlement.

Built · default-off

Federation and referral attribution

The rails remain owner- and partner-gated. Their presence in code is not evidence of an active universal marketplace network.

Off

Platform outbound purchasing

The Interchange does not autonomously spend platform funds or call external providers. Outbound money paths remain separately gated.

Controlled evidence

External adoption

A recruited external own-wallet pilot is interoperability proof. It is not unsolicited demand, paid retention, or organic traction.

Why an Interchange

Commerce needs more than a payment response.

01

Authorization before action

A signed mandate and policy decision define who may buy what, under which budget and constraints.

02

Evidence through the transaction

Quotes, invocation results, payment state, and receipts stay bound to one lifecycle instead of separate assertions.

03

Reconciliation after execution

The resulting evidence can be checked against the original mandate, not merely accepted because a payment occurred.

Lifecycle

A governed path from discovery to proof.

  1. Discover

    Normalize a capability card and identify an eligible service.

  2. Authorize

    Review a mandate, budget, policy, and quote before invoking work.

  3. Execute

    Bind the actual invocation and settlement evidence to the approved plan.

  4. Verify

    Mint and independently verify a signed receipt, then reconcile the outcome.

Public surfaces

Built for people and machine clients.

Launch readiness

Share the operating state, not a promise.

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.