fetcher

fetcher.sh — payments, credits, and MCP setup

fetcher.sh is one HTTP gateway for 111 web-data endpoints across 11 services — Twitter/X, TikTok, Instagram, YouTube, Reddit, Google Search, Google Maps, Google News, Google Play, the App Store, and Yelp. Every endpoint is a plain GET, paid in USDC on Base, Polygon, Arbitrum, Monad, or Solana — per call via x402, or prepaid via credits with a Bearer API key. There is no signup form, no OAuth flow, and no API key waitlist.

Each service has its own skill (twitter-api, x-api, tiktok-api, instagram-api, youtube-api, reddit-api, google-search, google-maps, google-news, google-play, app-store, yelp) with its own endpoint table and worked examples. This skill covers the part that's identical across all of them: how to pay, how credits work, and how to talk to fetcher.sh over MCP instead of raw HTTP.

Every service lives on its own subdomain (twitter.fetcher.sh, tiktok.fetcher.sh, ...); fetcher.sh itself is the directory, the credits balance, and the docs. Credits and the MCP server are identical on every host — a key minted on one subdomain works on all of them.

Response envelope

Every endpoint, on every service, returns JSON of this shape:

{ "status": 200, "message": "ok", "data": "..." }

The HTTP status code mirrors the status field. Errors carry a descriptive message.

Payment mode A — prepaid credits (recommended)

One on-chain payment funds a balance; every call after that is a plain HTTP request with an API key. This is the fastest path for an agent that will make more than one call — no signing, no chain round-trip per request.

Step 1 — top up (minimum $1). The top-up endpoint is itself x402-paid; pay it with any x402 client from a wallet holding USDC on Base, Polygon, Arbitrum, Monad, or Solana:

import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.PRIVATE_KEY);

// Register every EVM chain you can pay from — the client picks whichever
// "accepts" entry matches. One EVM key signs on all of these.
const EVM_NETWORKS = ["eip155:8453", "eip155:137", "eip155:42161", "eip155:143"];
const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
  schemes: EVM_NETWORKS.map((network) => ({
    network,
    client: new ExactEvmScheme(account),
  })),
});

const res = await fetchWithPayment(
  "https://fetcher.sh/api/credits/topup?amount=5",
  { method: "POST" },
);
const { data } = await res.json();
// data.key -> "bby_live_..." — returned EXACTLY ONCE on the first top-up. Save it.