x402 + prepaid credits · USDC, gas sponsored

Web data API — no account, pay per call

11 APIs on 11 domains — Twitter/X, YouTube, Reddit, Google and more — 111 endpoints in total. No account, no OAuth, no subscription. Pay per call in USDC from $0.002, or top up once and spend one balance across all of them.

pay from any of:BasePolygonArbitrumMonadSolana
the x402 flow
# no account, no OAuth — just call it
$ curl 'twitter.fetcher.sh/api/search?query=x402'
← 402 Payment Required · $0.005 in USDC
      pay on Base, Polygon, Arbitrum, Monad or Solana

$ curl -H "X-Payment: <signed>" 'twitter.fetcher.sh/api/search?query=x402'
← 200 OK · settled on-chain

catalog

11 APIs, 111 endpoints

Each one is its own domain with its own docs, and they all draw on one balance. One MCP server at mcp.fetcher.sh. $0.002 – $0.005 per call in USDC on Base, Polygon, Arbitrum, Monad or Solana.

quick start

Three ways in

Same endpoints, same prices — pick how you want to pay and copy the snippet.

For agents with a wallet — no account at all

Call any endpoint. You get a 402 with machine-readable payment requirements, sign it, and retry. Pay in USDC on whichever chain you already hold — gas is sponsored, so no native token is needed.

accepts:BasePolygonArbitrumMonadSolana
curl — see the payment challenge
# call without payment to inspect the 402 challenge
curl -i 'https://twitter.fetcher.sh/api/search?query=x402'
# HTTP/1.1 402 Payment Required
# payment-required: <base64 payment requirements>

try it

One call, live, right here

Run a real request against a real endpoint. Without a key it opens the payment page for a browser wallet; with one it spends your credits.

Twitter search — $0.005

opens the payment page in a new tab · $0.005 per call

pay from any of:BasePolygonArbitrumMonadSolana

Already have a key?

One balance covers every service. Check what is left on yours:

No key yet? Top up — the first one mints it, shown once, minimum $1. Agents can do the same themselves via /skill.md.

mcp

Add it to Claude or Cursor

A remote MCP server on its own host — nothing to install. Browsing the catalog is free; your agent pays only when it fetches.

The catalog MCP server lives at mcp.fetcher.sh. Paste that origin into Claude Desktop, Cursor, or any MCP client — browsing the catalog is free; your agent pays only when it fetches.

mcp config
{
  "mcpServers": {
    "fetcher": { "url": "https://mcp.fetcher.sh" }
  }
}

Full setup, tools, and credits header · /skill.md

pricing

Start for $0.002 — not a monthly plan

Everyone else sells plans, seats, and minimums before you see a single byte. Here the entry price is one call. The live table is /prices.

price per call

$0.002 – $0.005

And that is the entire commitment. No plan, no seats, no monthly minimum — pay per call, and credits never expire. Exact per-endpoint prices are on /prices.

Official platform APIsmonthly plan + seats
Hosted scraper APIsmonthly plan + minimums
fetcher.shone call
← the whole commitment.

Bars illustrate what you sign up for before the first byte — subscriptions and minimums elsewhere, a single call here.

questions

FAQ

Do I need an official developer account?
No. fetcher.sh is not the official Twitter, YouTube, or Google API. You do not register an app, complete OAuth, or wait for platform review. Call a URL; data comes back as JSON.
Is there a monthly minimum or subscription?
No. There is no monthly plan, no seat fee, and no minimum volume. Pay per call from $0.002. Credits never expire. A $1 credit top-up is only if you want a prepaid API key instead of paying each call.
Can I pay for a single request?
Yes. Call any endpoint with no credential and pay that one request in USDC via x402. No account, no invoice, no leftover plan.
Do I need an account?
No. For pay-per-call you only need a wallet holding USDC on Base, Polygon, Arbitrum, Monad or Solana — the signed payment is the authentication. Prepaying credits gets you a bby_live_ API key, which is the only credential fetcher.sh ever issues.
How does x402 payment work?
Call any endpoint without payment and the server replies 402 with a machine-readable payment-required header listing one option per network (Base, Polygon, Arbitrum, Monad or Solana). Your client signs a USDC transfer authorization on whichever chain it holds and retries with an X-Payment header; fetcher.sh verifies and settles it through an x402 facilitator. Gas is sponsored, so the wallet needs no native token. Libraries like @x402/fetch automate the whole loop.
Why use credits instead of paying per call?
Throughput. A per-call payment adds an on-chain verify-and-settle round trip to every request; with credits there is one settlement per top-up and each call is a single atomic balance debit. Same endpoints, same prices — just faster, which matters when an agent fires hundreds of requests.
How do I get — and rotate — my API key?
Easiest: the /topup page — connect a wallet, pay (minimum $1), and your API key is generated and shown exactly once. Via API it is the same thing: POST /api/credits/topup?amount=5. Refills keep the key; add &rotate=1 (or tick rotate on the page) for a fresh key — the old one stops working immediately. Lost keys cannot be recovered (only a SHA-256 hash is stored) — rotate instead.
What happens when my balance runs out?
The call returns 402 with message topup_required, your balance, the endpoint price, and a top-up URL. Recharge at /topup (any wallet can recharge any key) or via the API, then retry.
What if a request fails?
Validation problems return a descriptive 400; upstream failures are forwarded in the same envelope. Settlement happens before delivery, so failed calls are not refunded — the trade-off is identical in both payment modes, and at the default price a lost call costs a millionth of a dollar.
Are there rate limits?
No. Per-call pricing is the backpressure — your balance (or wallet) naturally caps throughput.
Do you have an MCP server?
Yes — a remote server at mcp.fetcher.sh is catalog discovery (search, describe, fetch). Each service also has a specialized server at [service].fetcher.sh/mcp with one named tool per endpoint. Free tools do not charge; paid tools accept x402 or a Bearer credits key.
Is fetcher.sh built for AI agents?
Yes. Machine-readable 402 challenges, a stable { status, message, data } envelope, agent setup instructions at /skill.md, and an LLM-oriented summary at /llms.txt. Point your agent at the skill and it handles the rest.