Outdated or incorrect details?

Scraping & contentSocial media

SocialRouter

One API to extract data from any social network, with automatic provider failover.

Agents extract social and web data through a single REST endpoint, an official npm SDK, CLI, or MCP server. The provider catalogue and per-record pricing are queryable before a call, and credits are pay-per-record so an agent can compare providers and pin the cheapest or fastest.

Agent access evidence

CLI

native

Official `@socialrouter/cli` npm package runs extractions, browses providers, and checks the account from the terminal; configured via the SOCIALROUTER_API_KEY env var.

Evidence

API

native

REST API with `POST /v1/extract`, `POST /v1/search`, provider catalogue, balance, and usage endpoints; Bearer auth and normalized responses.

Evidence

MCP

native

Official `@socialrouter/mcp` server exposes extract, search, list_providers, get_provider, get_extraction, get_balance, and get_usage tools for Claude Desktop, Claude Code, Cursor, and other MCP clients.

Evidence

Browser

strong

Dashboard manages keys, credits, and usage; a browsable provider list at socialrouter.io/providers exposes copy-ready slugs.

Evidence

Account creation

strong

Self-serve signup, then create `sr_live_` API keys from the dashboard.

Evidence

Pricing clarity

strong

Pay-per-record pricing is documented and queryable per provider via `GET /v1/providers`; the published rate is the rate charged with no hidden multipliers.

Evidence

Docs quality

strong

Mintlify docs cover quickstart, authentication, concepts, an interactive API reference, and dedicated SDK, CLI, and MCP guides.

Evidence

Sandbox

unknown

No sandbox, test mode, or dry-run is documented. Every extract/search call runs against live providers and is billed against the account's real paid credit balance, so an agent cannot rehearse a call for free.

Readiness score

Usable

Usable: 69/100. Strongest in machine operability; weakest in agent safety.

Machine operability24/25

Agent safety6.4/25

Agent readability17.4/20

Auth and setup12/15

Production reliability9.2/15

Best for

Extracting normalized social media and Google Maps data across many providers without integrating each scraping actor separately.

Pricing

Pay-as-you-go credits denominated in USD, charged per record returned. No subscriptions or minimums. Per-record price varies by provider, platform, and extraction type; the live price on `GET /v1/providers` is the price paid.

Auth

Bearer API keys prefixed `sr_live_`, created in the dashboard and shown once. 60 requests/minute per key, with optional per-key credit limits. Listing providers is public; all other endpoints require auth.

Account creation

Self-serve signup at socialrouter.io; create API keys from the dashboard.

Browser support

Web dashboard handles signup, API key management, credit top-ups, and a browsable provider catalogue with copy-ready slugs.

CLI

@socialrouter/cli

API

https://api.socialrouter.io

MCP

npx -y @socialrouter/mcp

Limitations

Key limitations: Extractions are billed per record returned against whichever provider succeeds, so an agent should set a sensible `limit` and watch credit balance before large jobs. Scraping social platforms may be subject to each platform's terms and regional data rules; review compliance before delegating bulk extraction. The Vercel function timeout caps long-running extractions at 300s, and the in-memory rate limiter is advisory. Verify provider availability and pricing via `GET /v1/providers` before automating.