Trust & data practices

Agent payments move money and generate data. Here is exactly how both are handled — in the architecture, not just in policy.

No custody on direct implementations

On a direct implementation, settlements move wallet-to-wallet: an agent's USDC goes directly to the API owner's wallet (the payTo address) via the facilitator — there is no step in that flow where Quinn's Conveyance holds, pools, or can move a client's funds. The Agent Gateway works differently, by design: agent payments settle to the gateway wallet first, and each supplier's 80% share is paid out to them in batches — with a per-call ledger the supplier can audit. We say which flow applies, on the page where it applies.

Customer data is never sold

The settlement ledger records what operating the service requires: transaction hash, payer wallet, endpoint called, amount, timing, and verification status. It is used to run the service, produce the client's own reports, and improve reliability — and for nothing else. Client data is never sold or shared with third parties. Export or deletion on request, any time.

Every settlement is verified

Each payment is independently checked after settlement — signature recovery, nonce consumption, transfer-log match, validity window — and the result is stored as a verify_status on the record. Verification is fail-open but loud: a check that cannot run is marked unverified, never silently passed, and a delayed re-check corrects the false failures that chain-propagation lag causes. The live statuses are public on the Insights dashboard.

Open by default

The demo is public, its settlement data is public, the SDK is open source (quinns-x402 on npm, source on GitHub), and our measurement methodology is published — How We'll Measure the Agent Economy. Claims you can check beat claims you have to trust.

The rails

Base mainnet, native USDC, EIP-3009 transfer authorizations — the payer signs and never pays gas. Settlement runs through two independent facilitators (Coinbase CDP and PayAI) with automatic failover, so no single provider's outage stops a client's revenue.

Questions

Security or data questions about a deployment: john@quinnsconveyance.com. If you are evaluating Quinn's Conveyance for your API, ask for the pilot agreement — the no-custody and data terms on this page are contractual there, not just descriptive.