Bazaar discovery API stuck at 9/83 resources after 96hrs · Issue #854 · coinbase/cdp-sdk · GitHub
Skip to content

Bazaar discovery API stuck at 9/83 resources after 96hrs #854

Open

Description

@6mickswagger9

Summary

Merchant 0xb5093b19A6cf2e5135B212074521d1734ADad959 shows only 9 of 83 resources in the discovery API after ~96 hours of continuous uptime. All 16 APIs have been confirmed Bazaar-settled via x402scan self-test (Oct 16, 16/16 settled).

Details

  • Merchant address: 0xb5093b19A6cf2e5135B212074521d1734ADad959
  • Resources indexed: 9 / 83
  • Time since first settlement: ~96 hours
  • Pattern: compute-api 7/14, gecko-toll 1/2, llm-toll 1/2, all others 0/N
  • Discovery endpoint: GET /platform/v2/x402/discovery/merchant?payTo=0xb509...d959

Reproduction

  1. Settle any x402 payment to the merchant above
  2. Wait 24–96 hours
  3. Query the discovery API — resource count does not increase beyond initial index

Related

Request

Can you trigger a re-index for this merchant, or confirm a fix timeline for the selective ingestion bug?

Workaround attempted

  • Confirmed all 16 APIs respond correctly to /.well-known/x402
  • Confirmed x402scan shows 19/19 servers live
  • Self-test settles 16/16 successfully
  • No action on my side resolves the indexer gap

Activity

  1. ethanoroshiba commented on Oct 23, 2026

    @ethanoroshiba
    Contributor

    Hi @6mickswagger9, it looks like the nine routes you listed have the correct Bazaar metadata, but many payments were missing the required paymentPayload.resource (see docs here).

    To get each endpoint discovered and keep it listed:

    • Include valid paymentPayload.resource and paymentPayload.extensions.bazaar on settlements to the CDP Facilitator.
    • Make a settlement corresponding to each resource you wish to be listed /.well-known/x402 is not part of the x402 spec and is not supported by the CDP Bazaar.
    • Keep every endpoint reachable and returning a valid 402 payment response to unpaid requests. /price and /chat were removed after liveness checks received 3 consecutive 500s in response, and both still return errors. /summarize also returns 500.

    Hope this helps, please see the docs link above for more troubleshooting steps and information regarding discovery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions