Twitter/X data.
60× cheaper than X's API.
Tweets, user profiles, follower graphs, and search results as structured JSON via REST or MCP. X bills per post read — we bill per request, and one request returns a full page. No scraping infrastructure, no rate limit headaches.
Trusted by developers shipping real products.
99,750 served today
Request
$ curl -X POST api.fetchlayer.dev/twitter/search \ -H "Authorization: Bearer ss-..." \ -d '{"query": "openai", "product": "Latest"}'
Response
{
"results": [{
"text": "Just tried the new GPT-5.6...",
"author": { "handle": "devuser" },
"likeCount": 142,
"retweetCount": 31
}]
} vs the official X API
Twitter/X data,
60× cheaper.
X bills per post read and has closed its cheap tiers to new developers. We bill per request — and one request returns a whole page. Here's the math, plus everything else you stop maintaining.
Same data, a fraction of the bill
X bills per post read. We bill per request — and one request returns a whole page of posts.
1,000 searches · 25 posts each (our default)
≈ 63× cheaper — and it widens with page size
X retired its free tier and closed Basic and Pro to new signups — pay-per-use or enterprise are the only remaining self-serve routes.
The part nobody budgets for
The scraper is a weekend. Keeping it alive is a headcount.
With FetchLayer Our entire pricing model, in three lines
No compute units, no per-result inflation, no monthly minimum. Three lines is the entire formula — extra pages included, so the bill never surprises you.
You only pay for data you actually get.
A timeout, a block upstream, a bug on our side — the reason doesn't matter. If a request doesn't come back with usable data, it isn't billed.
Live, not cached
Fetched the moment you ask. You're never handed a three-week-old dump that quietly went stale.
Nothing to maintain
Guest tokens, rotating GraphQL ids, cursors, and bans are our on-call rotation. Your code keeps calling one URL.
Support, any hour
Stuck on an endpoint or a strange payload? Message us and you get an answer — any hour, any day.
What you get
Every public Twitter/X endpoint, structured.
We access publicly available X/Twitter data and return it as clean, typed JSON. No authentication with X required on your end.
Search tweets
Full-text search across X/Twitter with Top, Latest, People, Media, and Lists product views. Paginated results.
POST /twitter/search 200 OK Tweet detail & replies
Fetch any tweet by ID with full engagement metrics, media, and language. Paginate through reply threads.
"This changes the whole pipeline…"
@devuser · 142 ♥ · 31 ⇄
"Does it handle cursors though?"
@sre_anna · 12 ♥
"Yep, cursor-based pagination…"
User profiles
Bio, follower/following counts, verification status, join date, location, website, and avatar for any public account.
48,201 followers
joined 2011
User timelines
Pull tweet and reply timelines for any public user. Full engagement data with cursor-based pagination.
Network graph
Followers, following, and verified followers for any account. Map audience graphs with profile metadata.
edges
Base: POST /api/twitter/<endpoint> · Bearer auth · Cursor-based pagination ·
Full API reference →
MCP & agents
Your AI already knows
how to use this.
One config block and every Twitter/X endpoint becomes a first-class tool inside your agent. No SDK, no wrapper code, no glue logic — just paste and go.
Pick your editor and we hand you the config with your key already in it — no JSON to hand-edit, no wrapper code.
Get your free API keyFree tier · no credit card · any MCP host
Find tweets from AI founders discussing their tech stack. Pull the top 10 with engagement metrics.
Found 10 tweets. Top result from @sama: "We think this is the most important capability for agents" with 4.2K likes...
Works with every MCP-compatible tool
Use cases
What developers build with X/Twitter data.
Same API, endless applications. Here's what teams ship with our endpoints.
Competitor intelligence
Search public forums for any brand or product. Get unfiltered opinions, complaints, and praise from real users.
AI agent context
Feed real user conversations straight into your LLM pipeline. Structured data, zero parsing scripts.
Brand monitoring
New posts, new mentions, new complaints. Sort by recency and run it on a schedule.
Product research
Pull customer pain points from niche communities. Real people, real frustrations, no surveys.
Content pipelines
Trending discussions become blog ideas, newsletters, social content. Automate your content sourcing.
Lead generation
Find people asking for solutions you sell. Identify intent signals in the right communities.
Instant research. Zero setup.
You can use FetchLayer with AI coding agents like OpenAI Codex, Claude Code, Cursor, or Windsurf via MCP. But if you just want results now — no IDE, no code, no terminal — open FetchLayer Research Chat and describe what you need.
Found 128 tweets from 84 accounts discussing AI tooling. Exporting now...
tweets-ai-tooling-2026-07.csv
128 rows · 8 columns · ready to download
Via AI Coding Agents
Connect via MCP and let your AI agent call FetchLayer tools inline. Fully customizable — build pipelines, chain tools, add your own logic. The most powerful option for devs who need total control over their workflow.
- Best for: custom pipelines & automated workflows
- Fully programmable — chain any tools together
- Setup: add MCP config to your AI IDE
- Output: inline in your editor/terminal
Via FetchLayer Research Chat
InstantNo IDE needed. Describe your research in plain English — "Find tweets from AI founders about pricing changes" — and get a downloadable CSV or JSON file with structured data in seconds.
- Best for: instant research & lead gen
- Setup: none — just type
- Output: downloadable CSV & JSON files
Uses the same credits as the API · No additional setup
Pricing
Start free. Scale when ready.
Pay per request with no commitment, or lock in a flat monthly rate with built-in savings.
Calculate your savings
vs the official X API
100,000
X API
$500.00
$0.005 / post read
SocialSignal
$7.96
4,000 requests · $1.99 / 1,000
You save $492.04/mo
63× cheaper
Free plan — 30 requests
Verify responses, inspect the API, no credit card required.
Pay as you go
$1.99
per 1,000 requests
$0.00199 per request · credits never expire
How credits work — no multipliers
One credit = one API call, on every endpoint and platform. No matter how many results come back, you pay for the call, not the output size. Most scraping APIs charge multipliers of 5x, 25x, even 75x per call depending on the target — here it's always 1.
- No multipliers — 1 request = 1 credit
- No monthly commitment
- Credits never expire
- Same API & MCP access as subscribers
- ∞ req/min, ∞ API keys
∞
Expiry
Credits stay until you use them. No monthly reset, no pressure to hit a quota.
0
Commitments
No subscription, no contract, no minimums. Start, pause, or scale whenever.
100%
Access
Every endpoint and MCP included. Not a limited tier — same data as any subscriber.
FAQ
Common questions.
What is FetchLayer Twitter Scraper?
FetchLayer Twitter Scraper is a REST API and MCP-compatible service for accessing publicly available X/Twitter data as structured JSON. It covers search, tweet details, replies, user profiles, follower/following graphs, and more — without requiring you to maintain scrapers, parse HTML, or manage proxy infrastructure.
Is this the official X/Twitter API?
No. FetchLayer is an independent, third-party service not affiliated with, endorsed by, or sponsored by X Corp. or Twitter, Inc. We access publicly available data and structure it for developer use, in compliance with applicable law.
Is this legal?
We access only publicly available information — the same data any browser can see without logging in. We do not bypass authentication, access private content, or violate any terms of service. If you have questions about your specific use case, consult your own legal counsel.
Can I use this with AI agents?
Yes. Call the API from your agent code, or use the MCP server so your AI IDE (Cursor, Windsurf, Claude Desktop) can search and analyze Twitter/X data directly.
What is the MCP server?
A Model Context Protocol server. You add it to your AI IDE config, and your AI can call Twitter/X search, profile lookup, and network graph tools inline. One-time setup.
Does MCP cost extra?
No. MCP uses the same API credits as direct API calls. Same plan, same bill.
What data comes back?
Tweet text, author info, engagement counts (likes, retweets, replies, views), timestamps, follower/following lists, user bios, verification status. Everything in consistent JSON.
Can I search for tweets by keyword?
Yes. Search across Top, Latest, People, Media, or Lists product views. Sort and paginate results. Build your own monitoring pipeline on a schedule.
Can I pull someone's followers or following list?
Yes. The network endpoints return followers, following, and verified followers for any public account — with profile metadata and pagination support.
Get X data without
breaking the bank.
Search tweets, pull profiles, map follower graphs — structured JSON on your first call, at a fraction of what the official API charges.
or read the docs first — no account needed
FetchLayer is an independent, third-party service. We are not affiliated with, endorsed by, or sponsored by X Corp. or Twitter, Inc. "X", "Twitter", and related marks are trademarks of X Corp. This service accesses only publicly available data — the same information visible to any unauthenticated browser. We do not access private content, bypass authentication, or store personal data beyond what is publicly displayed. Use of this API is subject to our Terms of Service and applicable law.
Used by developers at
Individual developers or teams — not official partnerships