New: the Scrapier MCP server. Every scraper in Claude Code with one command. See how →
Features

Everything you need to scrape the web at scale

Blocking, browser rendering, proxies and parsing run on our side. You send one request with one key and get typed JSON back: 199 endpoints across 35 platforms, over REST or as MCP tools.

Last updated

199endpoints
35platforms
0credits for a failed call
1API key for all of them
Quick answerScrapier turns 199 endpoints across 35 platforms into typed JSON calls. Each endpoint has a published schema, runs over REST or as an MCP tool, and costs a fixed credit price per successful call. Failed calls cost nothing.
Summary

Feature summary

Every feature serves one job: a platform's public data as typed JSON, from code or an agent, at a known price.

FeatureWhat you getWhere it's documented
Endpoint catalogueOne endpoint per platform and data type, 199 in all/scrapers/
Typed JSONThe same field names on every callEach endpoint's schema in the docs
MCP serverEvery endpoint as an agent toolMCP server
OpenAPI specA machine-readable API definitionGET /openapi.json
Free discovery calls/me, /endpoints and /openapi.json cost 0 creditsDiscovery endpoints
Cursor paginationnext_cursor passed back as cursor until it is nullPagination
Per-call billingFixed credits per endpoint; failed calls free/pricing/
Back-pressure signals429 or 503 with Retry-AfterRate limits
Catalogue

Endpoint catalogue

Each endpoint is one GET call with named inputs, such as /instagram-profile/?usernames=natgeo. No selectors, no URLs to build, no HTML. Browse all scrapers.

TikTok 29 Instagram 20 Facebook 19 YouTube 17 Google 12 Reddit 9 Amazon 8 LinkedIn 8 X 6 Threads 6 Etsy 6 Airbnb 5 All 35 platforms
Output

Typed JSON output

The same field names on every call. Code and agents read followersCount, score or price directly, because the schema is published before the call runs.

Output formats

JSON over REST and MCP, in one envelope: {"success": true, "data": {…}}. To turn a single page into text or Markdown, use the free web tools.

Sample response
// GET /instagram-profile/?usernames=mrbeast
{ "success": true,
  "data": { "profile": {
    "username": "mrbeast",
    "fullName": "MrBeast",
    "followersCount": 456000000,
    "postsCount": 350,
    "verified": true,
    "scraped_at": "2026-03-09T15:19:49Z"
  }, "next_cursor": null } }
MCP server

How do agents use Scrapier?

Every endpoint ships as an MCP tool with a typed schema and a plain-English description, so the agent chooses the right scraper itself. One remote server at mcp.scrapier.io/mcp works with Claude Code, Cursor, Windsurf, Codex, VS Code and other MCP clients.

  1. 01

    Add the server

    One command in Claude Code, Cursor or Windsurf.

    claude mcp add --transport http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"
  2. 02

    Ask in plain English

    Describe the data you need.

    "Get the last 20 posts from @natgeo."
  3. 03

    Get typed JSON

    The agent calls the right tool. Billed per successful call, at the same price as REST.

    instagram_user_posts(username="natgeo", limit=20)
response.json
// instagram_user_posts(username="natgeo", limit=20)
{
  "username": "natgeo",
  "count": 20,
  "posts": [
    { "id": "C9xQ2…", "likes": 412880, "comments": 2194 },
    { "id": "C9vL8…", "likes": 298113, "comments": 1607 }
  ]
}
Developers

Developer tooling

Everything below is in the docs, with copyable snippets.

Authentication

Send your key in the X-API-Key header on every request. Keys never go in URLs.

Discovery without a key

GET /endpoints lists every endpoint with its inputs and cost_credit. Free.

Pagination

Pass data.next_cursor back unchanged as cursor until it is null.

Errors and retries

402 with a balance means out of credits. 429 or 503: wait Retry-After seconds. Retry 5xx with backoff, free; set timeouts of 210 s or more.

OpenAPI and Postman

Import /openapi.json into Postman, Insomnia, Bruno or a code generator.

No-code integrations

An n8n community node, plus Zapier and Make through their HTTP and webhook modules.

Infrastructure

Blocking, rendering and proxies

Scrapier runs browser rendering, proxy rotation and retry logic for each endpoint. You never configure a proxy or a headless browser: you receive JSON, or an error you are not billed for.

Billing

Billing model

A fixed credit price per endpoint, per successful call, listed before you call it. Failed calls are free, an empty result page still costs, and MCP and REST cost the same. See pricing.

What we run

What does Scrapier handle for you?

Six layers you would otherwise build and maintain yourself.

Stealth

  • Anti-bot measures and CAPTCHAs handled per endpoint
  • Fingerprinting, proxy rotation and retries tuned by us, not you
  • A call that still fails is not billed

JavaScript rendering

  • Headless browsers run on our side where a platform needs them
  • Single-page apps, infinite scroll and lazy loading handled inside the endpoint
  • The next page arrives as a cursor, not a scroll script

Structured output

  • Clean, typed JSON with a published schema
  • No selectors to write and nothing to parse
  • Ready for AI, RAG, databases and analytics

Scalability

  • Synchronous calls: one request returns a full page of results
  • Up to 3 parallel requests per key; more on Enterprise
  • Zero infrastructure to manage or maintain

Discovery and pagination

  • The full catalogue, with every input, from one free call
  • The same cursor rule on every paginated endpoint
  • An OpenAPI spec for Postman or a code generator

Geo targeting

  • Country, location and language inputs on the endpoints that support them
  • For example countryCode on Google Search and country_code on TikTok trending videos
  • Target specific countries for localized data
Build vs buy

Scrapier vs building it yourself

LayerScrapierDIY scraper
Anti-bot and CAPTCHAsHandled per endpointConstant maintenance
ProxiesIncluded in the credit priceSeparate vendor and bill
ParsingTyped JSON per endpointSelectors that break on redesigns
Agent accessMCP server, one tool per endpoint, 199 in allWrite your own tool wrappers
BillingPer successful call; failed calls freeServers, proxies and engineering time
Limits

Feature limits

What Scrapier does not do, so you can rule it in or out quickly.

  • Catalogue platforms only; for a one-off page, use the free web tools
  • No interactive browser sessions (click, type, log in)
  • Public data only
  • Up to 3 parallel requests per key on self-serve plans
  • No custom JavaScript execution
FAQ

Frequently asked questions

What does Scrapier do?

Scrapier turns 199 endpoints across 35 platforms into typed JSON calls. Each has a published schema, runs over REST or MCP, and costs a fixed credit price per successful call. Failed calls cost nothing.

Does Scrapier work with Claude, Cursor and other MCP clients?

Yes. Every endpoint is an MCP tool on one remote server, priced the same as REST.

What format does Scrapier return?

Typed JSON with a published schema per endpoint, wrapped in a success and data envelope.

Do I need proxies or a headless browser?

No. Scrapier runs them per endpoint and bills only successful calls.

Can Scrapier scrape any website?

No. It covers its catalogue of 35 platforms. The free web tools convert single pages to text, Markdown or JSON.

Get started

Skip the scraping infrastructure.

One key, 199 endpoints, typed JSON back.