State of x402: November 2026

Headline numbers

→ 0 more columns

The headline rate is 87.9 percent: 13177 delivered calls out of 14995 calls that reached a final outcome. Calls held as inconclusive (below) and calls still waiting for a re-read are left out. The totals include Tempo over MPP. The public state API publishes the rate as l1Rates.deliveredOfFinalOutcomePct and its denominator as l1Rates.denominators.finalOutcome.

By chain

→ 0 more columns

Chains with fewer than 100 settled calls are omitted from this table. Settled calls answered with a 4xx are held out of the last column.

Tempo is paid over MPP rather than x402, so its row sits in the public state API instead of this table. The totals above include it. All chains, including the small ones, are in the public state API.

Base carries most of the volume. The table is there so each chain team can read its own row.

Why calls did not complete

vet402 groups the calls that did not end as delivered into four reasons, as of 2026-11-09 (UTC). The first three are held out of seller scores.

Settled, then a 4xx answer (746): Payment went through and the seller answered with a 4xx. vet402 may have sent a request body or key the seller did not expect, so these are held out of seller scores.

4xx with no settlement receipt (4315): The paid request answered with a 4xx other than 402, and no settlement receipt came back. Often vet402 formed the request differently from what the seller expects. These are held out of seller scores too. Sellers can make their request shape easier to follow by describing it in the 402 response.

vet402 wallet empty (1032): From 2026-09-13 to 2026-09-15 (UTC), vet402's Base buying wallet was empty. Those runs are excluded from seller scores. They say nothing about sellers.

Settled, no usable content (504): Payment settled and the answer carried no usable content: a 5xx, a 202 Accepted, an empty 2xx body, or no status on record. A seller that answers every settled call with content closes this gap.

What sellers can do

• Return the paid content on every settled call. Use consistent success status codes and payloads so automated buyers can verify delivery.
• Keep 402 payment instructions aligned with what your server enforces. Mismatches show up as pre-payment rejections or post-payment errors.
• Watch your chain's settled and delivered counts in the public observatory data. When settled climbs faster than delivered, the handler is the place to look.

What agent builders can do

• Treat settlement and the HTTP response as one workflow. An agent should not mark a task done on chain confirmation alone.
• Check before you pay: read what vet402 received from a seller before an agent signs. How: https://vet402.com/x402/check-a-seller
• Pull the CSV export before you route an agent, and prefer endpoints with a delivered row. In this snapshot, 8199 endpoints delivered at least once and 8807 had at least one settled payment.

Method

vet402 buys from public x402 catalogs and the MPP directory with its own wallets, records what came back over HTTP, then re-reads the settlement on chain. Counts in this report match the public observatory API as of 2026-11-09 (UTC). Full state: https://vet402.com/api/v1/observatory/state. CSV export: https://vet402.com/api/v1/observatory/export.csv. Data under CC BY 4.0.

Paid x402 can work at scale when sellers deliver after every settlement. vet402 keeps measuring that gap in the open.