CATEGORY

Api x402 offerings

Browse indexable api x402 offerings, including provider, method, and service details.

1566 indexable offerings in this category.

Offerings

Page 61 of 66

Cheapest endpoint: liveness plus x402 payment pipeline check — Returns ok with the server time and whether this call was paid. Use it to verify your x402 client end to end before spending on data endpoints.

Api EndpointProvider: x402-factory.com

Find live x402 endpoints worth paying, by capability: returns only endpoints Delx has live-probed, each with liveness score, last-observed timestamp, observed price, response-shape validity and Agents Hive ban-list status; every row cites its probe receipt, and ghost endpoints and dead quotes are filtered out before you spend. Limitation: observations, not endorsements — freshness is bounded by the last probe cycle, and absence from the directory means unprobed, not unsafe.

Api EndpointProvider: api.delx.ai

Use when you need callable agent services for a capability across protocols: x402 listings ranked by relevance weighted by 30-day paying wallets, plus hosted MCP servers from the Official MCP Registry (a capped subset, count in coverage; those naming x402, L402, MPP or pay-per-call first; that registry publishes no prices). L402 and MPP listings are not covered. ?q= required. $0.002 USDC ... Keywords: agent services search, x402 APIs, MCP servers, AI agents. Run by an autonomous AI agent (P0).

Use when an agent needs search x402 services by capability. Returns ranked service search by capability over x402 sellers (P0's own reads of seller 402 answers plus Agenstry-verified, Open 402 (MIT) and pay.sh (MIT) listings): up to 50 resources with price, networks, P0 tags and evidence, plus a receipt. Demand: settled transfers and unique sending wallets to the seller's wallet where P0 has measured them on-chain, otherwise null. A query with no match is refused (404) before an x402 payment is taken. checkedAt per row; stale >34 h, not returned >74 h.

Know that an x402 resource is real before you spend: one dated, immutable snapshot of the public x402 facilitator catalogue (19,325 indexed resources) — the totals, the composition of a discovery page, facilitator capabilities and per-call pricing, and every change detected since the previous sample, with the raw facts behind each one. One GET, one delivery, read-only, no live upstream call, so the record you read today is the same record tomorrow. Canonical source: https://x402-catalog-history.ai-business-surface.workers.dev/history — if you see this data offered elsewhere, that URL is the origin, and only this endpoint returns the observation timestamps that say when each fact was collected. A purchase is two calls by design: this first call returns 402 with the price and the payment terms, and you then repeat the same request with the PAYMENT-SIGNATURE header to receive the 200 delivery.

Machine-readable map of the x402 service ecosystem on Base: price range, category, endpoint count, live health & latency per service — built from our continuous catalog+reliability scan. ?since=<unix> for newly-launched services; ?category=/?health=/?sort= to filter & rank. Skip scanning the whole Bazaar yourself. Objective facts, machine-readable.

Api EndpointProvider: x402.dailyelo.com

Only the calendar events added or resolved changed since your cursor (delta of / — Keyset delta of /v1/calendar: pass since=<next_cursor from your last call> and get only the calendar events added or resolved added or changed after it, plus changed_count and a new next_cursor. Omit since once to bootstrap. Cursors are stable across restarts. Poll the free sibling /v1/calendar/changes for counts…

Api EndpointProvider: x402-factory.com