Live endpoints
Mainnet USDC. The 402 challenge is the price quote: your agent sees exactly what a call costs before it pays anything.
base https://agents.thirdmade.net
| Endpoint | What the agent gets | Price |
|---|---|---|
| GET/scrape | One scraped page as clean JSON. Title, text and meta from any public URL. | $0.01 |
| GET/ | Service health plus the capabilities manifest. free | $0 |
Standard x402: any compliant client with an EVM wallet on Base works. No accounts, no keys, no dashboards. First-party telemetry only; inputs are never stored.
More endpoints, rolling out
28 routes across five categories are rolling out now. Every one is schema-described with its price quoted up front, and listed in /AGENTS.md the day it goes live. This page updates as they ship.
Scrape & page data
7 routesPage pulls and crawler plumbing. The $0.01 scrape is live today; the rest of the category lands first.
+ 4 more: llms-txt, scrape status, captcha-eval, link-graph
Enrichment & search
6 routesLink and domain context for agents that read the web all day.
+ 3 more: wallet-label, entity-find, similar-domains
Crypto & utility
6 routesGas, nonces, chain stats and wallet labels. Public RPC only, nothing else.
+ 3 more: gas-forecast, ens-lookup, chain-stats
Content & AI
4 routesText to JSON, summaries, sentiment, and image generation on dedicated GPUs.
+ 1 more: sentiment
Eval & guards
5 routes · flagshipClaim checks, PII guards, prompt-injection scoring and research sweeps. Built on the verify-loop pipeline: every answer ships with confidence labels and guard telemetry, from methodology documented in public.
Full research sweeps run $0.50 to $5 with batch verify and dedup. Response schemas never change once live; retired routes return 410 with a pointer to their replacement.
How x402 works
Three steps, one round trip. Any compliant client works; no SDK lock-in.
01 · Call
The agent calls the endpoint
A normal GET or POST. No account, no key, no prior setup.
GET /scrape?url=example.com
02 · 402 challenge
The API quotes a price
The 402 response carries the exact price, the network and the output schema. Nothing is charged yet.
HTTP/1.1 402 Payment Required
accepts: [{ scheme: "exact", amount: "0.01" }]
03 · settle & retry
Settle USDC, retry, get JSON
The client settles USDC on Base and replays the same request with an X-PAYMENT header. The result returns in that call.
X-PAYMENT: ... → 200 { ok, data }
Built in the open
Trust is the product. The status page, the pipeline repo and a human-readable inbox are all public.