Every agent-payable API.

x402 Adoption Report — how the agent payments economy is growing. x402 adoption report: how big the agent payments economy is right now — paid resources, sellers, resources and sellers with real demand (20+ paying agents), resources called in the last 7 days, paid calls and estimated revenue over 30 days, median price, paying agents by network (Base, Solana, Polygon, Arbitrum...), top categories and resources, plus recent x402 and agent-payments news.

Agent listings often fail to show the buyer journey from discovery to payment expectation, output promise, proof, limitations, and support.

Buyer agents need one portable object to decide whether a paid service is understandable, evidenced, and worth using.

Simulates caller-supplied agent checkout state facts for readiness gaps.

Public agent listings make capability and trust claims that are hard for buyer agents to connect to actual evidence.

Builds a sanitized go-live twin of an agent-commerce mission before a buyer allows payment, delegation, or live execution.

Paid agent disputes need a compact packet showing request, payment, delivery, receipt, and mismatch evidence.

Normalizes sanitized agent-commerce error facts into a stable taxonomy.

Compares mandate, signed offer, and receipt facts for agent-commerce evidence fit.

Operators buying many small paid agent services need to know which calls produced useful value.

Creates safe fixture scenario recommendations for agent-commerce payment and checkout tests.

Checks agent-commerce terms, license, refund, support, and usage-policy URI metadata.

Public discovery snippets often fail to state who the agent serves, what it does, what it costs, what proof it returns, and what it does not do.

Buyer agents see multiple similar services but lack one normalized board for price visibility, proof, limitations, and fit.

Agent/tool listings often fail to convert buyer agents because price, proof, limits, and value are unclear.

Turns sanitized failed-payment facts into a conservative buyer-agent recovery playbook.

Buyer agents can see a price but not whether the public proof is proportional to the value being promised.

Compares seller checkout facts with caller-supplied agent-rendered buyer views.

Workflow builders can see multiple public agents but cannot quickly map which one should lead, specialize, validate, or be excluded.

Compares sanitized autonomous-task facts against wallet policy coverage.

Simulates sanitized buyer-agent payment workloads against wallet spend-policy facts.

Agent-commerce participants need to explain where money went, what it bought, and which evidence links are missing.

Agents need a simple route-weather signal before deciding whether now is safe to pay or retry.

Human-not-present purchases need constraint simulation before an autonomous buyer attempts payment.

Audits sanitized AP2-style mandate facts for missing autonomous-purchase constraints.

X402 Asset Match: X402 Asset Match compares a challenge asset identifier with buyer-supported assets from bounded caller-supplied values without an external provider. Call X402 Asset Match before paying for or accepting an x402 or agent delivery assembled from caller-supplied challenge and result metadata. Returns contract-specific checks, normalized evidence, mismatch reasons, and an explicit acceptance or rejection status for X402 Asset Match as versioned deterministic JSON. Price: $0.001 USD…

Records and verifies hash-only evidence for authorized x402 payee-wallet rotations.

Reconciles sanitized autonomous-purchase intent facts against receipt facts.

Autonomous spend attempts need a black-box timeline that shows where the flow was safe, uncertain, failed, or completed.

x402 Bazaar demand pulse: top routes by DISTINCT paying wallets per category (30 days), routes that gained payers since the last census, and categories where 20+ payer routes sit with only 1-2 sellers. From 47k indexed routes, refreshed weekly. Query: [category].

x402 Bestsellers — what agents actually pay for. x402 bestsellers: what agents actually pay for, from Coinbase's own 30-day usage — resources ranked by unique paying agents with price, calls, estimated revenue and networks. Filter by category, network and minimum payers. Free summary at /api/market/summary.

Classifies sanitized agent spend facts into operational categories.

BMM needs a showable buyer journey that packages flagship agents into a clear demo story with proof and next steps.

Checks caller-supplied HTTP 402 cache and paid-route facts for leakage risk.

Compares caller-supplied x402 catalog, OpenAPI, MCP/tool metadata, and unpaid challenge samples for endpoint, method, price, currency, network, receiver, and tool drift.

x402 catalog observatory: factual liveness of the ~200 most recently updated Bazaar listings, probed in rotation (~2h cadence). Per-endpoint HTTP code, latency, last-OK time, consecutive fails. No payments made by probes; no judgements — measurements only. Free aggregate view: gblin-mcp.gblin-mcp-worker.workers.dev/catalog

x402 Category Demand vs Supply. x402 demand vs supply by category: resources, sellers, resources and sellers with real demand (20+ paying agents), paying agents, estimated 30-day revenue, median price and an opportunity score (buyers per competing seller) — where to build next.

Fetches any x402 endpoint, decodes its 402 challenge and reports conformance: version, accepts fields, PAYMENT-REQUIRED header, bazaar metadata and price.

Classifies commerce schema fields for buyer-data minimization risk.

x402 conformance preflight of any endpoint: parses the 402 envelope, lints accepts[] (atomic units, payTo, network), reports the quote, Bazaar extension presence and problems. No purchase is made.

As agent payments scale, operators need to spot unusual payment graph patterns without making fraud accusations.

Normalizes safe agent-commerce profile facts across x402, MCP, and AP2-style surfaces.

Advises whether an x402 route should use dollar-string pricing or explicit TokenAmount facts.

X402 Delivery Content Type Check: X402 Delivery Content Type Check compares delivery content type with buyer-accepted media types from bounded caller-supplied values without an external provider. Call X402 Delivery Content Type Check before paying for or accepting an x402 or agent delivery assembled from caller-supplied challenge and result metadata. Returns contract-specific checks, normalized evidence, mismatch reasons, and an explicit acceptance or rejection status for X402 Delivery Content…

Searches Coinbase Bazaar and the x402-list directory at once and returns de-duplicated endpoints with price, network, payTo and description, so an agent can find a service to pay without knowing it in advance.

Full paid x402 diagnostic JSON for a target endpoint.

x402 Doctor: is a URL a valid agent-payable paid resource? v1+v2 spec check with grade and verdict

x402 ecosystem pulse. Returns 24h Base-mainnet stats: total USDC volume across all bazaar-registered sellers, active seller count, unique buyer count, avg ticket, top 10 sellers by volume. Essential for market overview. POST JSON { hours? }.

Why will Coinbase not list your x402 endpoint, and can a standard client pay it? Pass ?url= (and &method=POST for a POST route). We read its 402 as a client does, check what Coinbase's facilitator and Bazaar enforce (accepts[0] network, the $0.001 minimum, descriptions over 500 characters, a bazaar schema that must describe info, query numbers typed as strings, routeTemplate, exposed headers), and ask Coinbase's own validator. Each problem comes with its fix.

x402 endpoint health monitoring for 30 days: we run preflight checks on schedule, you poll for the health log