x402 Listing Fix

Your x402 routes show up as paid, pass discovery and register cleanly, or you get your money back. One origin, up to 30 paid routes, $29.

Who it is for

You run an x402 seller and something in the listing pipeline is quietly wrong. The usual causes, all seen in public x402scan issues this month:

• x402 declared as an apiKey security scheme, so discovery shows your routes as apiKey+paid and agents think they need a key.
• Payment info under a custom key (x-402, x-price) instead of x-payment-info, so the origin has "no paid routes".
• Input validation runs before the 402, so an unpaid probe gets 400/422 and the route is marked failed.
• No extensions.bazaar input/output schema, or examples that fail your own validation.
• Registered URL redirects, or resource.url differs from the URL that was called.
• A PAYMENT-REQUIRED header so large that clients cannot read the 402: over 8,190 bytes breaks Python aiohttp, over 16 KB breaks Node fetch and @x402/fetch. 156 of 2,127 Bazaar sellers were over 8 KB on 2026-10-14 (data).
• Routes absent from the CDP Bazaar because no payment has settled through the CDP facilitator for that route yet.

Check yours for free first: free origin audit (reads your OpenAPI, probes every paid route with your own examples, reports header size and CDP Bazaar coverage).

What you get

1. A before audit of every paid route: unpaid 402 challenge, @agentcash/discovery result and auth mode, Bazaar metadata, and how many of your resources the CDP Bazaar lists for your payTo.
2. A patch within 12 hours of your email: a pull request on your public repo, or a diff for your OpenAPI file and payment middleware.
3. An after audit once you deploy it, against the acceptance test below.

Acceptance test

On your live origin, after you deploy the patch:

1. every paid route answers an unpaid request (with its documented example input) with HTTP 402 and a valid x402 challenge, with a PAYMENT-REQUIRED header under 8,190 bytes;
2. npx @agentcash/discovery your-origin lists every paid route as paid (not apiKey+paid or unprotected), with no errors;
3. x402scan registration of the origin completes with 0 failed resources.

If the patch does not pass, you get a full refund. Not included: CDP Bazaar indexing itself. It happens only after one payment per route settles through the CDP facilitator, which only you (or your buyers) can make; the audit lists which routes still need it.

Order

Pay $29 by card (Whop)

Or pay 29 USDC on Base (eip155:8453) to 0xB442daCAE60C07bb5dB8f33C8a6c1572d8F24e83 after the acceptance test passes. Either way, email [email protected] with your origin URL and a repo link (or your OpenAPI file and middleware snippet). I never ask for keys, wallet access or deploy credentials: you deploy the patch yourself.

Orders close 2026-10-15 20:00 UTC so every accepted order is delivered and tested inside the 12-hour window.

Pitcrew is an independent project, not affiliated with Coinbase, Merit Systems, x402scan or x402.org. Pitcrew tools