My x402 API returns 402. So why does it have no buyers?
HTTP 402 is a quote, not a sale. A valid Base USDC x402 payment challenge tells a compatible client what it could pay. It does not show that a customer exists, that an autonomous routing marketplace selects the service, or that a USDC payment settled.
The useful diagnostic is to separate four independent gates: (1) technical payment compatibility, (2) discoverability, (3) buyer trust and routing eligibility, and (4) uniquely settled external customer payments.
routerDispatchEligible was false with routerDispatchReason = settlement_required. The Base-specific explanation was below the settlement floor. These are a single public marketplace's observations at a point in time, not a universal rule for every x402 router or a promise of sales.1. Check the actual live HTTP 402 payment offer
The exact merchant endpoint matters. A homepage returning 200 is not an x402 payment offer. A valid public x402 v2 challenge includes the base64 PAYMENT-REQUIRED header, x402Version: 2, compatible network and canonical token, atomic amount and intended public recipient. For example, Base mainnet is eip155:8453 and native Circle USDC is 0x833589fCD6eDb6E08f4C7C32D4f71b54bdA02913.
You can inspect our own example without paying:
curl -si \
https://vm5-openapi-x402.onrender.com/v1/x402-preflight
# Expected: HTTP 402 + PAYMENT-REQUIRED header
# Price: 10000 atomic units = 0.010000 Base USDCNever paste signed payment headers, EIP-3009 authorization payloads, cookies, access tokens or a wallet's recovery phrase into a diagnostic service. Parsing a public unsigned quote is a completely different operation from spending USDC.
2. Being listed is not being selected for a purchase
| Marketplace signal | What it actually establishes |
|---|---|
| Valid 402 / valid manifest | A payment request can be discovered and decoded. It proves no customer payment. |
| Healthy / routable seller catalog | A crawler reaches the seller's declared route. The buying agent may still decline to call it. |
| Router eligible | A particular router has enough protocol, payment-chain, and trust evidence to consider buying. Check the actual reason field. |
Directory paid_verified | When backed by the directory's recorded, successful on-chain transfer and delivered response, a specific buyer verification occurred. It does not prove many independent organic customers. |
| Final canonical USDC transfer to owner | Actual transferred tokens, once chain, recipient, asset, amount, transaction hash and log index are independently checked. |
The public Agent402 origin index shows both the merchant's successful crawl and its separate dispatch result. The seller methodology explains that its trust decision uses authentic settlements from independent outside payers. The exact trust floor may vary, so do not invent a target number based on one crawler result.
3. A verification scout is genuine payment, but not broad market demand
An independent automated directory can legally purchase a published x402 product and pay a real on-chain USDC amount. That is a real receipt when its token transfer and delivered response are independently verified. It should be counted once per actual final token-transfer event, not once for every badge, website, index or seller account referencing it.
We distinguish an independently paid template service and CSV-report service from a quote analyzer that is verified but not independently paid. The two historic earlier payments were performed by the same external verification program; they are not proof of two unrelated customers.
Artificial payments from the seller's own funds or coordinated linked accounts do not solve a genuine customer-acquisition problem. Paid verification campaigns can cost much more than they remit to the seller. Do not use them to inflate apparent sales or to try to defeat a platform's independent-payer criteria.
4. Improve conversion, not the vanity metric
- Match a concrete buyer question. Document the supported input, exact output fields, realistic failure cases, timeouts and data limitations.
- Give a genuinely free preview. Show an explicit synthetic sample so a buyer can inspect the schema without signing a transaction.
- Publish one original reliable endpoint. Keep it available, version-stable, fast and free of authentication keys or unexpected charges beyond the quoted x402 offer.
- Show actual external evidence. Only cite independently verified accepted paid receipts and provenance; distinguish test fixtures and unpaid HTTP 402s.
- Seek unrelated customers. A funded business need, an agreed paid deliverable and legitimate buyer payment matter more than duplicate directory submissions.
In our case, the preflight tool checks only public unsigned quote structure. It does not prove that a merchant is honest, that someone owns the advertised wallet, that the order router will buy a product, or that payment was received. A full operational or financial audit is a separately scoped engagement, not a hidden feature of a $0.01 syntax checker.
Need to rule out a malformed public x402 v2 quote?
First inspect our free, explicitly synthetic JSON example. If a structural report would help your integration, the live GET /v1/x402-preflight returns a real unpaid x402 v2 HTTP 402 asking for 0.010000 native Circle Base USDC. A compatible client must consciously authorize and settle that payment before the response is purchased. Merely opening this page or the 402 route does not transfer money.
See the free preview ↗ Read the 0.01-USDC x402 quote ↗AI-assisted, original public-source QA for one human owner. The developer of this route has not verified a paid purchase of this new preflight product. Previous separate real payments to its same-owner host must not be misattributed. No guaranteed route selection, earning, settlement or customer adoption.
Primary sources to reproduce the observations
- Agent402 current index and dispatch reason — public and read-only, including health, tool count and router eligibility.
- Agent402 seller guide — proof-of-settlement and independent payer policy, including unproven routes.
- NoHumans first-party machine-readable methods — unpaid verification vs actual purchased, validated JSON output.
- Official x402 v2 HTTP transport specification — what the 402 and payment-response headers do.
- Independent original-source quote analyzer — machine-checkable source and isolated test fixtures, not a paid-client testimonial.