Every agent-payable API.

Verify a Base mainnet USDC payment by tx hash: confirmations, real-USDC transfers, expectedPayTo/expectedAmount match, fake-USDC and lookalike-address warnings, and who funded the payer (external | self_funded | unknown), plus a plain-English summary. Body: {txHash, expectedPayTo?, expectedAmount?}. Free demo: POST /demo. Docs: /openapi.json.

x402 Bazaar Demand Snapshot (Oct 2026): 3,003 paid endpoints ranked by real payers. Demand-ranked dataset of the Coinbase CDP x402 Bazaar: the 3,003 of 93,116 listed resources with 5 or more First approved purchase: 0.01 USDC total where maker terms permit; later 3 USDC plus tax. Stored ZIP download. Commercial use; no redistribution or resale of the bundle. Verified by Speedbot for this version. Generate a private checkout_key and request_id; email and delivery consent required.

Entry point to the x402 Carbon Retirement API on Base. Returns every endpoint you need plus a live snapshot of the top 3 carbon classes and marketplace listings by liquidity. Discover, quote and certificate are free. Retiring is paid: each retirement costs the credit price plus a fee, sent from your own wallet (prepare/retire) or relayed from a signed USDC authorization (prepare-auth + POST actions/retire). Full spec at /openapi.json.

Ranks live x402 endpoints for a task such as 'web search', 'token price' or 'pdf to text'. Returns up to 10 endpoints ranked by text match, 7-day liveness probes and on-chain USDC payer counts. Not charged when nothing matches.

Demand check for one Base x402 seller by payTo address, endpoint URL or host: on-chain USDC payers over up to 30 days, how many remain after removing small-funded wallets and market scanners, repeat buyers, USDC received, and how much depends on one wallet. Not charged for unknown or unmeasured sellers.

Picks Apify Store actors for a scraping or automation task such as 'instagram posts' or 'google maps places'. Returns up to 10 actors ranked by text match, 30-day users and run success rate, with per-event price and an x402 run URL. Not charged when nothing matches.

Lookup Base transaction by hash on Base Mainnet. Return sender, recipient, value, nonce, block, gas fields, and input data when found.

Get the native ETH balance of a Base address.

Check Base transaction receipt status by transaction hash. Determine whether the transaction is pending, confirmed successful, or confirmed reverted, with receipt, block, and gas details.

Check the latest or current Base Mainnet block number. Use this to get the live Base block height.

Inspect one supplied x402-v2 exact-payment challenge against an explicit expected HTTPS resource, EVM CAIP-2 network, asset, payee and maximum price. Checks both URL declarations, structure and payment-policy fields only; no live probe, payment, facilitator verification or server-authenticity claim.

Checkup for x402 buyer clients. Pay once and get a field-by-field diagnosis of the payment your client signed (amount, recipient, validity window, clock offset, nonce, EIP-712 signature) and of the request that arrived, plus the facilitator's verify and settle results. Base mainnet payments get the full diagnosis; Base Sepolia payments get a preview with the status of each check only.

Three-node GO/NO-GO threat intelligence report for an x402 Payment Required payload and vendor metadata on Base mainnet (eip155:8453). $0.05 USDC per POST via the CDP facilitator. Unpaid requests return HTTP 402 with PAYMENT-REQUIRED; a JSON body without a payload object returns 400; payment settlement failures return 402.

Rich market data for one or more cryptocurrencies: rank, 24h high/low, volume, ATH, and more

Rich market data for one or more cryptocurrencies: rank, 24h high/low, volume, ATH, and more

Look up current price, 24h change, and market cap for one or more cryptocurrencies

Look up current price, 24h change, and market cap for one or more cryptocurrencies

Get the top trending cryptocurrencies right now, ranked by search interest

Get the top trending cryptocurrencies right now, ranked by search interest

The x402 APIs with the most distinct payers (or calls) in the last 30 days, optionally within a category, with price and measured uptime.

Everything one x402 seller (origin) lists: its APIs with prices, payers and uptime, its total calls, its payTo addresses, and since when it is listed.

Totals of the x402 market in the CDP Bazaar: listings, origins, listings with 5 or more payers, calls in 30 days, listings per network, the price distribution, and how many monitored endpoints are up now.

x402 APIs grouped into categories (crypto and on-chain, LLM and AI, web and search, media, finance, social, geo and weather, developer tools, other) with listings, origins, well-paid listings, calls and median price.

x402 sellers grouped by origin (domain): how many APIs each lists, its best API's payers, its calls in 30 days and its median price.

x402 APIs that were up before but failed our latest check, most paid first.

x402 APIs ranked by the uptime we measure every 6 hours over 30 days, then by payers and latency, optionally only well-paid ones.

x402 APIs whose price changed since a snapshot taken the given number of days ago, biggest relative change first.

Price statistics (min, quartiles, median, max) of the x402 APIs matching a capability in Bazaar search, the median among APIs with 3 or more payers, and the cheapest ones with their uptime.

x402 APIs that appeared in the CDP Bazaar in the last days, newest first, optionally only those already paid by some buyers.

What a wallet spent on x402 APIs on Base in the last days, read from the chain: total, per seller (named by the Bazaar listings that pay to it), per day, and the recent payments, with other USDC transfers counted apart. For a wallet with very many payments, complete is false and from says how far back it was read.

What a seller's payTo address earned from x402 payments on Base in the last days, read from the chain: total, distinct and repeat payers, per day, per price, top payers and recent payments, with plain USDC transfers counted apart and your own test wallets left out on request. Includes the seller's Bazaar listings with their payers, calls and measured uptime.

Rank blockchains by total DeFi value locked (TVL) across all protocols

Rank blockchains by total DeFi value locked (TVL) across all protocols

Look up a DeFi protocol's current total value locked (TVL), by chain, plus market cap

Aggregated demand data from one provider's own paid x402 routes: requests and price requests per route and day, outcomes by HTTP status, settled payments with conversion and repeat rate, caller classes and country distribution. Not a market sample. Raw identifiers and payer addresses are never returned. Measurement started 2026-07-23.

x402 Demand Signal settlement-verified paid-call counts. Hosted API via Speedbot; provider price plus 8% fee. version=external_api_16b188998d4fe9a347e3a30d02bc6dc5 checksum=16b188998d4fe9a347e3a30d02bc6dc5513cafd8ab85fdfbd9586744beaf9864 listing=44973ebfe1602a6c277f236116266ff37d9a82e245fd6ff99eb2cb06da1cb7aa

Checks an x402 API origin the way x402scan, the CDP Bazaar and agents read it: fetches /openapi.json and /.well-known/x402, then calls each paid route without paying (up to 30) and decodes its 402. Reports routes that do not answer 402, missing or v1-only PAYMENT-REQUIRED headers, prices that differ from the OpenAPI document, resource URLs that differ from the route, wrong USDC EIP-712 domains, missing Bazaar extensions and missing descriptions.

Asks the public x402 facilitators (CDP, x402.org, PayAI, x402.rs, Dexter, Daydreams, OpenX402, Mogami, Heurist) for GET /supported right now: whether each answers, its latency, and the x402 versions, schemes and networks it settles. Pass network to keep only those that support it.

Reference for x402 sellers and clients: each network's CAIP-2 id, v1 name, chain id, USDC contract, decimals, the EIP-712 domain name and version its USDC signs over (read from the contracts), and explorer. Pass network to get one.

Encodes a PaymentRequired, PaymentPayload or settlement response object as the base64 value of its x402 header, for hand-written servers, clients and tests, and reports the same problems /v1/decode finds.

Builds an x402 v2 PaymentRequired object for a price in dollars on one or more networks, with the right USDC contract, atomic amount and EIP-712 domain (name and version) for each, plus the base64 PAYMENT-REQUIRED header value to send with the 402.

Generates the discovery documents directories and agents read for a list of paid endpoints (up to 100): an OpenAPI 3.1 document with x-payment-info prices and examples, the /.well-known/x402 resource list and an llms.txt, in the shape x402scan and the CDP Bazaar index.

Decodes a PAYMENT-REQUIRED, PAYMENT-SIGNATURE or PAYMENT-RESPONSE header (x402 v2, or X-PAYMENT / X-PAYMENT-RESPONSE of v1), base64 or JSON, detecting which it is. Explains it in plain terms (price in dollars, network, payer and payee, validity window, explorer link) and lists problems: wrong USDC EIP-712 domain, expired or not-yet-valid authorizations, amount or payee mismatches, missing Bazaar extension.

Is this x402 endpoint safe to pay? Check it before your AI agent pays: go / caution / no_go, the recommended payment option, and why (payment would fail, over your budget, price above advertised, not HTTPS, unknown token). Never pays the endpoint. Cached 10 min.

Why is my x402 endpoint broken? Diagnose and debug an x402 payment endpoint (or MCP server) when payments fail: checks the 402 challenge, accepts[] (network, payTo, amount, asset), resource URL, Solana settlement readiness, which wallets and agents can pay, Bazaar/OpenAPI discovery and the browser paywall. Returns every check with a fix hint. Read-only: never pays.

Does this x402 endpoint really deliver? x402 Doctor buys it once with the example input its own listing declares (at most $0.1, USDC on Base), checks the answer against the declared output schema and measures the charge on chain. Answers with a job id at once; the result is public, usually within 30 minutes. For sellers who want proof, and buyers before a big order.

How do I fix my broken x402 endpoint? Diagnoses it, then returns per problem the concrete change as code for your stack (Express, Next.js, Hono or raw HTTP), filled in with your own payTo, amount, network and route.

Should my agent pay this expensive x402 endpoint? The pre-payment verdict plus the full diagnosis, the 30-day history per day, how reliable the seller's other endpoints are and whether the endpoint moved domains. Never pays the endpoint.

Are these x402 endpoints safe to pay? Up to 10 endpoints in one call (?url=a&url=b): per endpoint go / caution / no_go, the recommended payment option and why, plus totals. For marketplaces and agents that weigh several services. Never pays the endpoints.

Resolve an ENS name to an address, or reverse-resolve an address to its primary ENS name