x402 / CDP / Bazaar discovery diagnostics

When x402 settles on-chain but Bazaar still can’t find you.

A fixed-scope readback packet for merchants and SDK teams debugging routes that return valid 402 challenges, settle through a facilitator, but never appear in CDP/Bazaar discovery.

1. 402 challenge readback

Decode the live PAYMENT-REQUIRED body and table resource URL, method, body type, amount, asset, network, payTo and Bazaar extension fields.

2. Discovery index check

Search discovery resources for hostname, route URL, payTo and declared metadata; record the exact miss pattern and pagination scope.

3. Escalation appendix

Produce a GitHub/support-ready appendix separating merchant config, facilitator behavior, indexer symptoms and retroactive-indexing questions.

Useful for cases like Coinbase CDP SDK #690

On 2026-05-21 I ran a no-payment public readback against the issue #690 route: POST https://api.syndicatelinks.co/affiliate/links returned HTTP 402 with a Payment-Required header declaring Base USDC, amount 10000, payTo 0x070417a378121FE31EA33199e7313C8D50AD844E, method POST, and Bazaar metadata. The CDP discovery first-page readback returned 500 resources and did not contain syndicatelinks, the route, or that payTo address.

No wallet signing, paid call, settlement, crypto transfer or facilitator mutation was performed. This packet is designed to stay useful before anyone spends money.

Deliverables

Proof base