Every agent-payable API.

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

Compares caller-supplied x402 facilitator cost facts for buyer-agent routing.

Scores caller-supplied x402 facilitator facts for production readiness.

Classifies sanitized x402 failure facts into safe diagnostic causes without replaying payments or storing raw logs.

Compares agent-commerce quote, checkout, final payment, and order totals for unexplained deltas.

x402 fleet health status API — live up/down check of core endpoints with timestamp, for AI agent monitoring dashboards. $0.001 USDC on Base per call.

x402 hello-world — $0.01 prove-the-rail settle. Returns signed Ed25519 receipt attestation + echo so your wallet stack has verifiable proof it can pay.

x402 Inspector scan (payment-challenge validation) — per call

Buyer agents can land on public docs but fail to find service purpose, examples, price, limitations, and support path.

Maps aggregate high-volume low-value machine-payment facts for treasury dust and reconciliation risk.

MCP/App SDK builders need to know whether tool schemas, action descriptions, privacy metadata, auth notes, and UI hints are ready for review.

Audits sanitized MCP elicitation prompts and consent facts for scope and record gaps.

Records and compares hash-only x402, OpenAPI, and MCP operation stability facts.

Maps paid MCP tool surfaces against x402 routes and possible unpaid aliases.

Audits sanitized MCP paid-tool permission scope declarations.

Checks MCP server release metadata for registry and paid-tool readiness.

MCP resource lists can mix public docs, schemas, logs, user data, and restricted-looking resources without clear buyer labels.

MCP servers can expose sampling behavior that is hard for buyers to understand before connecting or paying.

Grades paid MCP tool names, descriptions, schemas, and output labels for buyer-agent clarity.

Classifies one-shot MCP paid-tool metadata changes for buyer-agent compatibility risk.

Maps caller-supplied agent-commerce role facts into payment, fulfillment, support, and refund boundaries.

Builds an advisory failover ladder for caller-supplied x402 facilitator and network options.

Normalizes safe x402 challenge metadata from multiple provider formats.

Plans safer x402 network, token, amount-format, and transfer-method routing from caller facts.

Buyer agents often see a price and promise but no useful preview that proves what the paid result will contain.

Tracks hash-only completeness snapshots for paid-agent response contracts across releases.

Audits paid MCP/tool confirmation prompts for clear buyer spend consent.

Creates and verifies hash-only latency SLA evidence for paid agent tools.

Orders caller-supplied paid agent tools into a clear, trust-preserving upsell path.

Classifies timeout, cancellation, partial result, retry, and charge-policy facts for paid work boundaries.

x402 payability check: reachable + well-formed 402 + (Solana) destination-ATA existence

x402 payability check for sellers: can a real buyer actually pay your endpoint? Sends one payment signed by a fresh unfunded key through your server and facilitator. A payable endpoint fails only on balance; anything else (bad schema, long description, wrong EIP-712 domain, facilitator error) is reported with the exact reason. Base USDC, x402 v1 and v2.