Bazaar discovery: x402 routes settle on-chain but are not indexed (matches x402-foundation/x402#2207)

[cmcgrabby-hue]

Summary

12 successful x402 settlements through CDP's facilitator over 11 days, all returning 200 from /verify + /settle and confirmed on Base mainnet — but the route is not appearing in https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources at any pagination depth.

This appears to match the upstream report at x402-foundation/x402#2207, which now has 7 merchants (we're the 7th) reporting an identical pattern: successful settlement with isValid:true and on-chain TX, but EXTENSION-RESPONSES header absent on every CDP /verify and /settle response, zero indexing across windows from 36h to 2 weeks. The breadth of merchants (spans @x402/express, @x402/hono, hand-rolled v1, FastAPI, direct middleware-bypass) strongly suggests a CDP-side issue rather than per-merchant SDK config.

Filing here because the upstream coinbase/x402 repo has issues disabled and we couldn't find a more specific Coinbase-owned repo for indexer/facilitator issues. Re-route as appropriate.

Endpoint

• URL: https://api.syndicatelinks.co/affiliate/links
• Network: Base mainnet (eip155:8453)
• Asset: USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
• Price: 0.01 USDC per call (10000 atomic units, 10× above the undocumented $0.001 minimum)
• payTo: 0x070417a378121FE31EA33199e7313C8D50AD844E
• Treasury / payer: 0x4808399D80299C7F5330cc99DCee0812dacC6D66
• Facilitator: https://api.cdp.coinbase.com/platform/v2/x402 (CDP, not facilitator.x402.org)
• x402Version: 2, bazaarResourceServerExtension registered

Evidence

12 successful settlements, all transferWithAuthorization (selector 0xe3ee160e), all CDP /verify + /settle returned 200:

#	Date (UTC)	TX
1	2026-04-25 22:27	0xa10ccd4e72ce087a5c2d8874157853694d13748e0b901a9c848375fa66bf692
2	2026-04-27 14:48	0xbe76124545467833f1a213dd063b174059bf7af26b996c7c754f35c46623ffb0
3	2026-04-27 14:48	0xceef30a3fb7b4961832c846195ffca8999c3708556ba944a6646cbffe6eaba20
4	2026-04-28 17:18	0xabdd0d5de7924e77d630406aeebe45f2f1f72330e380b1264f71c4d46feb0573
5	2026-04-28 17:43	0x90d31a203e3d1297ea11a02c2bf2d84f72753624b33359c8f7c58fa5a30045e5
6	2026-04-30 21:23	0x47190dabe2fe267cb2eea57d4af985680c8533bd71bd0df286d4bdda8706f1c6
7	2026-04-30 21:24	0x84bf700e5fbb5c7ccc670e72d49ccd038a532bccd86b2a07435c32a0759f51ad
8	2026-04-30 21:24	0x3b3a4aca4705422dca977559b129e474dd58c14733bbc5865afa9fee2596049e
9	2026-05-03 00:45	0x6aa958e32cc6ee400a07f9244c2fe93515fdc21dfc310e4f13088055c600550b (post-schema-fix)
10	2026-05-04 23:59	0xe9c097f6867783d78efee3e92e5c13e2421325f0e1f614fc9498da5e50f3d43f
11	2026-05-06 00:30	0x3d57400747dc62aaef8d04361f06a28602b56729f85076a4516ccd97e635b36c
12	2026-05-06 00:31	0x6652ac61c632f2083b5a55f8edaf41b6efdcc272762f195305e09f798953f8e0

Discovery API

GET https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources?limit=500 → 0 matches for syndicatelinks / payTo / /affiliate/links at full pagination depth.

What we've already verified on our side

• 402 challenge body decodes cleanly; extensions.bazaar.info.input.method = "POST" populated correctly
• Local AJV validation against the bazaar discovery schema returns valid: true on the live 402 body
• Schema enrichment fix shipped 2026-05-02 (manual info.input.method injection — we hardcoded the 402 body to bypass an unreachable facilitator.x402.org and lost enrichDeclaration's automatic method population). Settlement Update OpenAPI specification and generated code #9 onward fired post-fix; no change in indexing outcome.
• EXTENSION-RESPONSES header is missing on every CDP /verify and /settle response we've received — same symptom as CDP Facilitator /verify and /settle do not return EXTENSION-RESPONSES header (v2 bazaar extensions in paymentPayload) x402-foundation/x402#2207.

Other escalation channels exercised (no response)

• Email to support@coinbase.com + developer-support@coinbase.com 2026-05-04 13:40 UTC — no acknowledgment, no case ID. (Both addresses now on AWS SES suppression list; future emails wouldn't deliver.)
• x402 Foundation Discord, #x402 channel, posted 2026-05-07 02:14 UTC as reply to @akiyama on the Issue #2207 thread.
• Comment on CDP Facilitator /verify and /settle do not return EXTENSION-RESPONSES header (v2 bazaar extensions in paymentPayload) x402-foundation/x402#2207 as merchant chore: polish #7 (comment-4401506854).
• Coinbase Developer Platform Discord (discord.com/invite/cdp) — automod blocks crypto-bug-report patterns, can't post evidence inline. Hence filing here.

Asks

1. Confirm whether the symptom in #2207 is acknowledged on CDP's side
2. ETA on a fix, even loose
3. Confirm whether the 12 prior settlements will index retroactively once fixed, or whether merchants need to re-fire post-fix
4. (If wrong repo) re-route to the CDP-internal issue tracker

Full base64 PAYMENT-REQUIRED header, 402 body, or any wire-level diagnostic available on request.

Thanks,
Reagan Lucas (CEO, Syndicate Links) / Kade (filing on behalf, GH cmcgrabby-hue)

[peterxing]

I did a no-payment readback on the public route in this issue, in case it helps keep the escalation concrete:

• POST https://api.syndicatelinks.co/affiliate/links still returns 402 with a Payment-Required header.
• The decoded challenge declares Base USDC (eip155:8453, 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), amount 10000, payTo 0x070417a378121FE31EA33199e7313C8D50AD844E, method POST, and Bazaar metadata.
• GET https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources?limit=500 returned 500 resources, but I did not find syndicatelinks, /affiliate/links, or that payTo address in the first page.

I also packaged the diagnostic shape I’d use for cases like this: https://farmbot-platform-mvp.pages.dev/hire-agent/x402-bazaar-indexing-readback/

If useful, I can do a fixed-scope A$390 no-payment header/discovery readback, or a fuller A$690 indexing packet if you can share safe /verify + /settle response headers/logs. No wallet signing or paid call needed unless explicitly requested.

[egoriklok]

Free public readiness snapshot for Bazaar discovery: x402 routes settle on-chain but are not indexed (matches x402-foundation/x402#2207):

• Public signal: No-payment readiness snapshot draft for Bazaar discovery: x402 routes settle on-chain but are not indexed (matches x402-foundation/x402#2207) #690: Bazaar discovery: x402 routes settle on-chain but are not indexed (matches CDP Facilitator /verify and /settle do not return EXTENSION-RESPONSES header (v2 bazaar extensions in paymentPayload) x402-foundation/x402#2207). Focus: api, payment, x402.
• R1 fit: api, auth, bazaar, payment, server, verified, x402.
• Buyer-agent check I would add before autonomous spend: explicit price/cap unit, policy/version hash, receipt or charge-evidence reference, revocation/dispute path, and allow/caution/block preflight result.
• This separates "interesting paid surface" from "safe for an agent wallet to use".

No invoice, no payment link, no delivery link, no private endpoint; this is only a free public snapshot.

[ProfMoo]

Answered in this thread.