x402-listing-doctor
Why is my x402 service not listed — or listed but never paid? Send your endpoint URL; we fetch your 402 envelope, run the exact SDK validation the CDP facilitator runs, check catalog presence, and return per-check pass/fail with concrete fix hints. Includes two undocumented traps we verified against the live facilitator: a buyer must echo your bazaar extension into the settle payload, and a description over 500 characters makes the facilitator reject every payment. Deterministic, no LLM.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.25 USDC on Base to 0xD617…441eE. The signed payment is good for 5 minutes.
- Paid to
- 0xD617…441eE
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 250000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xD617a7145ca56E3ed58d639F9DEC6999B22441eE",
"amount": "250000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"method": "POST",
"resource_url": "https://your-shop.example.com/v1/your-endpoint"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"url": "https://your-shop.example.com/v1/your-endpoint",
"checks": [
{
"id": "returns_402",
"status": "pass",
"message": "402 Payment Required"
},
{
"id": "bazaar_extension_present",
"status": "pass",
"message": "extensions.bazaar present"
},
{
"id": "facilitator_extraction",
"status": "pass",
"message": "extractDiscoveryInfo OK (same function CDP runs)"
},
{
"id": "listed_in_catalog",
"status": "warn",
"message": "not in catalog snapshot 20260612 (25403 items)"
}
],
"overall": "listable_pending_settle",
"how_to_get_listed": [
"1. ...",
"2. KEY: buyer must echo the bazaar extension into the settle payload ...",
"3. ..."
]
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"resource_url"
],
"properties": {
"method": {
"enum": [
"POST",
"GET",
"PUT",
"PATCH"
],
"type": "string",
"description": "HTTP method of your endpoint (default POST)"
},
"resource_url": {
"type": "string",
"description": "public https URL of your x402-gated endpoint"
}
},
"description": "Diagnose why an x402 resource is (not) listed in the CDP Bazaar. Fetches your 402 envelope, runs the same SDK validation/extraction CDP runs, checks catalog presence, and returns per-check fix hints including the undocumented buyer-side settle requirement."
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-08-01 21:04Z
- Last indexed by Roundhouse
- 2026-08-31 20:50Z
- Last enriched (probe, favicon, geo)
- 2026-09-11 06:45Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 404
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 8 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service x402-listing-doctor and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=x402-listing-doctor' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://x402.dailyelo.com/v1/listing-doctor, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.