# x402 Listing Doctor — x402-store.dgdb.workers.dev

> x402 Listing Doctor — x402-store.dgdb.workers.dev is a paid API for AI agents from x402-store.dgdb.workers.dev, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-14).

Validates an x402-gated endpoint against CDP facilitator requirements and returns per-check pass/fail results with fix hints for Bazaar listing eligibility.

## Facts

- Endpoint: POST https://x402-store.dgdb.workers.dev/v1/listing-doctor
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-listing-doctor-x402-store-dgdb-workers-dev-7b8faca6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gqxJyJeA66lHab9CJa1Vw

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-listing-doctor-x402-store-dgdb-workers-dev-7b8faca6 -d '<json body>'
```

Example prompt: My x402-gated API at https://api.myservice.com/v1/generate is not showing up in the Bazaar — can you run the listing-doctor check on it as a POST endpoint and tell me exactly what's failing and how to fix it?

## When to prefer this

Use this endpoint when an x402-gated API is not appearing in the Bazaar or CDP facilitator catalog and you need deterministic, LLM-free diagnosis of exactly which validation step is failing. Preferred over manual inspection because it runs the exact same SDK validation and extraction functions the facilitator uses, including undocumented requirements like the bazaar extension echo.

## Known failure modes

- Endpoint URL is not publicly reachable — returns error indicating fetch failure
- Endpoint does not return a 402 status — check reports missing payment required response
- Malformed x402 envelope — specific field failures listed with expected format
- Bazaar extension not present or not echoed in settle payload — flagged as undocumented requirement failure
- Endpoint already in catalog but misconfigured — partial pass with remaining fix hints

## How this service works

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.

## Output

A structured list of per-check pass/fail results covering 402 envelope validation, CDP SDK extraction compatibility, catalog presence, and the bazaar-extension echo requirement in settle payloads, each with a concrete actionable fix hint.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-listing-doctor-x402-store-dgdb-workers-dev-7b8faca6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-store.dgdb.workers.dev](https://www.zero.xyz/host/x402-store.dgdb.workers.dev/llms.txt)