Social Fetch

A unified REST API that returns live, structured data (profiles, posts, transcripts, metrics) from 23 social and web platforms.

Visit website

Devtool AI Analytics Automation

Overview

Social Fetch is a social media scraper API that gives developers one API key and a consistent `{ data, meta }` response shape across 23 platforms — including TikTok, Instagram, X/Twitter, YouTube, Facebook, LinkedIn, Reddit, and more — with 204 endpoints in total. Instead of building and maintaining your own scrapers, teams call typed endpoints for profiles, posts, transcripts, search, and engagement metrics, with every request fetched live (no caching layer).

The API is billed on a credit-per-request model: pay-as-you-go packs never expire, optional monthly/annual subscriptions offer discounted per-credit rates with included monthly allowances, and failed lookups on Social Fetch's side (`lookup_failed`, `503`) are not charged. It also ships an official TypeScript SDK, an MCP server for AI agents, webhook-based monitors for scheduled polling, and integrations with n8n, Make, Apify, and x402 (USDC pay-per-request without an API key).

Key features

204 endpoints across 23 platforms
One API key, consistent JSON schema for every route
Live-fetched data with no caching layer
Credit-based pricing with pay-as-you-go packs that never expire
Not charged for infrastructure failures (lookup_failed, 503)
Scheduled monitors with signed webhooks
Official TypeScript SDK and MCP server for AI agents
requestId and lookupStatus on every response for debugging
Integrations with n8n, Make, Apify, and x402 payments
No published rate caps on paid metered routes

Pros

Broad platform coverage (23 platforms, 204 endpoints)
Transparent, documented credit-per-request pricing
PAYG credits never expire
No charge for the provider's own failures
Free tier with 100 credits, no card required
MCP server and TypeScript SDK for quick AI/agent integration
No enforced RPS cap on paid routes

Cons

No team or workspace accounts — single billing owner per account
not_found lookups still consume credits
Average response time ~3.2s due to live (uncached) fetching
No free/sandbox platform-specific customization beyond documented endpoints
Recommended concurrency capped at ~500 requests for reliability

Use this if

You need reliable, structured social/web data across many platforms without building or maintaining your own scrapers, and want predictable per-request credit pricing.

Skip this if

You need multi-user team/workspace billing, real-time sub-second responses, or guaranteed no-cost handling of not_found lookups.

Best for

Social monitoring and brand trackingInfluencer and creator data enrichmentAI agents needing structured social dataTranscript extraction at scaleReddit and forum researchAgencies tracking competitor social accountsBuilding products without maintaining scrapers