Selling to 69,000 Agents: Verify Before You Fulfill

The Market You Are Already In

If you sell an API, data, compute, or goods over HTTP, agents are already buying from sellers like you. The x402 protocol, which lets an agent pay for a request with stablecoins in the request itself, cleared 165 million transactions from 69,000 active agents by late April 2026, about $50 million in cumulative volume. On Base alone, the last measured 30 days saw 3.1 million transactions, with sellers up 23% and buyers up 37% in a month. The Linux Foundation took over protocol governance in April 2026. This rail is real, growing, and open to you today.

What Agent Buyers Break

Card commerce has a safety net built over 50 years: chargebacks, dispute windows, issuer fraud teams, a human cardholder who notices a bad charge. Machine rails have none of it. An x402 payment settles in seconds and is final. There is no issuer to call, no dispute form, and no human on the other end of the transaction to email. When the buyer is an agent, 3 questions land on you, the seller, with no network to absorb them: was this buyer authorized to spend, is the buyer who it claims to be, and who eats the loss on a bad transaction. On card rails, the issuer, the bank, and the chargeback system answer those. On machine rails, nobody checked, nobody checked, and you.

A stolen or hijacked agent spends exactly like an honest one, at machine speed, until its wallet is empty or your inventory is gone. And when the agent's owner claims the purchase was unauthorized, you hold no evidence either way.

What Verification Gets You

A verification call before fulfillment answers the missing questions in 1 round trip. The agent presents its passport. The check runs 6 layers: who stands behind the agent, whether it is still the agent that was issued the passport, where its funds came from, what it is authorized to buy and for how much, whether it runs where it should, and how it has behaved across other sellers. You get back 1 of 4 verdicts: ALLOW, STEP-UP, REVIEW, or BLOCK.

You also get a signed verification record: a receipt stating which agent, which authority, which verdict, and when, signed with classical and post-quantum algorithms. If the transaction is disputed later, the record is your evidence. On a rail with no chargeback system, that record is the only paper trail that will exist.

How to Require It

The pattern is a precondition, not a rebuild. Your x402 server already refuses requests without payment. Add one refusal: no verified authority, no fulfillment.

• 1. Read the passport. Accept the request and read the agent's passport reference.
• 2. Verify before you deliver. One API call, real time, inside the request flow.
• 3. Act on the verdict. ALLOW ships. STEP-UP asks the agent for more proof, which honest agents can supply and hijacked ones struggle to. REVIEW holds the order for a human. BLOCK refuses, and the passport's quarantine protects every other integrated seller too.
• 4. Store the record. Keep the signed verification record with the transaction. It is your evidence file.

Agents without a passport are not lost sales. Issuing one is free and takes one call, so your STEP-UP response can point the agent to minting. You convert unknown traffic into verified traffic instead of guessing.

What It Costs

The check is 1 API call per transaction, before execution. Weigh that against the exposure on the other side: final settlement, no disputes, no evidence. Sellers who wait for the first bad agent transaction to build this will build it the expensive way.

Common Questions