x402-protocol-integration

Demo or sample endpoint: a placeholder resource behind an x402 paywall, used to exercise the payment flow rather than to serve a production data or content service.

Decode an x402 payment challenge before paying: give it the raw 402 body or payment-required header, as JSON or base64, and get back the version, resource, and every accepted payment normalised to scheme, network, asset, amount and payTo. Names what is wrong with named warnings — bad amount, unrecognised network, invalid payTo, unsupported scheme, missing input or output schema — and returns the declared Bazaar schemas. No network call, no payment sent.

Live liveness + quote check for any x402 endpoint: probes it unpaid (cached ≤5 min), returns status, latency, parsed price/network/payTo, schema completeness, on-chain payer activity (Base), quality score and risk flags. Call before paying an unfamiliar endpoint.

Same lookup as /lookup/{agentId} — this route exists to measure willingness-to-pay and x402 Bazaar discoverability, not because the result is different or better paid.

One unpaid-probe preflight report for an x402 endpoint.

Audit a whole set of captured 402 challenges in one call. Per challenge it reports whether a payment can be constructed, which blocking defects stand in the way, whether the resource is bound to the URL it came from, the cheapest accepted amount and the networks offered. A challenge supplied without its URL has its binding reported as unchecked rather than assumed sound. Nothing is paid.

Decide whether a captured 402 challenge can actually be paid. Separates defects that stop a payment being constructed from ones that merely make the call harder to get right, and checks the resource is bound to the endpoint that served it - a challenge naming a different resource would, if paid, satisfy a requirement for something else. Also names the price spread when several payments are accepted. Nothing is fetched and nothing is paid.

OpenAI-compatible chat completions over x402, answered by Claude Sonnet 4.6 — send a messages array…

Highest-demand x402 services tagged 'inference': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 125 providers and 382 paying wallets measured in this tag.

Highest-demand x402 services tagged 'gateway': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 72 providers and 289 paying wallets measured in this tag.

Highest-demand x402 services tagged 'llm': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 183 providers and 459 paying wallets measured in this tag.

Find out what an x402 endpoint will charge before you pay it. Probes the endpoint, reads the challenge from the header or the body, and returns the decoded price, network, asset and payTo plus the declared input and output schemas. Never sends a payment. Only reviewed origins are reachable, and a redirect is refused rather than followed.

Find out which x402 versions you are actually dealing with across a set of sellers. Reports challenges declaring a version you do not support, challenges declaring no version at all - where how to read the rest is a guess - and a set spanning more than one version, which means your client must implement each of them at once. Nothing is paid.

Free x402 resource (price 0): a compact preview of one public Airbnb room page as JSON: title, location, rating, review count, property type and photo count. Same parser as the paid /api/airbnb/listing endpoint, which returns the full record (description, host, amenities, rooms, coordinates, photos) for USD 0.02. Input: airbnb.com/rooms/<id> URL.

x402-paid endpoint: an unpaid request returns HTTP 402 with a PAYMENT-REQUIRED header (base64 JSON payment requirements). Pay with any x402 client and retry with the X-PAYMENT header. Response is delivered synchronously; you are never charg

x402 listing-quality snapshot from public discovery catalogs (CDP and/or PayAI). Scores unique-payer vs wash when quality fields exist. No invented market sizes. Cached 15 minutes.

Audit any public x402 endpoint: one unpaid probe → 402 validity, x402 version, decoded price/network/asset, payTo type (EOA vs contract), discovery-metadata hints, pass/warn/fail checks; SSRF-safe; never pays

Submit a design prompt. Requests without a paid L402 credential return HTTP 402 with Lightning payment details; replay the same request with an L402 Authorization header after payment.

读取 ypolymarket `panel-{timeframe}.jsonl` 末尾 lookback 行。 未付款时由 x402 ASGI 中间件返回标准 HTTP 402 + payment requirements； Agentic Wallet / CDP Facilitator 结算成功后本 handler 才会执行。

JINBots SAGA | 3 • 7 • 42 | Proof More |. https://jinsbot.thesaiyajin.io - POST CloseTheDoor Credits Pack (42 check-ins)

Ranked list of live x402 endpoints (top 50) filtered by keyword, network and max price, ordered by Settled quality score. Use it to find a working alternative to a dead or overpriced endpoint.

Robinhood prediction-market catalog (x402)

Self-test endpoint to trigger x402 listing using wSOL

x402Sample: x402 - x402Sample