Unofficial Third-party API

10 endpoints live

Twitter/X data.
Without the scraping.

FetchLayer Twitter/X Scraper returns tweets, user profiles, follower graphs, and search results as structured JSON via REST API or MCP. No scraping infrastructure, no HTML parsing, no rate limit headaches.

Start building free See examples →

Free tier included · No credit card required

POST /api/twitter/search

200 OK · 1.2s

Request

$ curl -X POST fetchlayer.dev/api/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
  }]
}

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.

Tweet detail & replies

Fetch any tweet by ID with full engagement metrics, media, and language. Paginate through reply threads.

User profiles

Bio, follower/following counts, verification status, join date, location, website, and avatar for any public account.

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.

MCP for AI agents

Connect your AI IDE to X/Twitter data with one config block. Works with Cursor, Windsurf, Claude.

API reference

One base URL. Ten endpoints.

All public data. POST with JSON body, get JSON back. Auth via Bearer token.

Endpoint

What it returns

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.

mcp.json Model Context Protocol

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer sk-..."
      }
    }
  }
}

agent chat using fetchlayer

Find tweets from AI founders discussing their tech stack. Pull the top 10 with engagement metrics.

Using fetchlayer.twitter.search

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

Cursor

VS Code

Windsurf

Claude

Cline

OpenClaw

No wrapper code

All 10 endpoints exposed as tools

Official & maintained

Free to install

API examples

Request in, structured JSON out.

Pick an example, hit Run, and see the response. Every endpoint works the same way.

Examples

Request

POST /api/twitter/search

{
  "query": "GPT-5.6 launch",
  "product": "Latest",
  "count": 5
}

POST /api/twitter/tweet-detail

{
  "tweetId": "1942939879222220800"
}

POST /api/twitter/user-profile-details

{
  "handle": "openai"
}

POST /api/twitter/user-tweets

{
  "handle": "sama",
  "count": 3
}

Click Run to see the response

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.

brands sentiment research

AI agent context

Feed real user conversations straight into your LLM pipeline. Structured data, zero parsing scripts.

llm agents mcp

Brand monitoring

New posts, new mentions, new complaints. Sort by recency and run it on a schedule.

alerts monitoring cron

Product research

Pull customer pain points from niche communities. Real people, real frustrations, no surveys.

pain points validation niches

Content pipelines

Trending discussions become blog ideas, newsletters, social content. Automate your content sourcing.

content automation trending

Lead generation

Find people asking for solutions you sell. Identify intent signals in the right communities.

leads sales intent

FetchLayer Research Chat

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.

fetchlayer.dev/chat

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

Set up MCP

Via FetchLayer Research Chat

Instant

No 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

Open Research Chat

Uses the same credits as the API · No additional setup

Pricing

Start free. Pay for what you use, or lock in a flat rate.

Credits for flexible, no-commitment usage. Subscriptions for a fixed monthly rate with built-in savings. Subscriptions+ for teams that want volume pricing at scale.

Free plan

30 free requests

A small test drive to verify the API, inspect real responses, and decide whether you want to stay on credits or move to a subscription.

Try free

Pay as you go

$1.99 per 1,000 requests

$0.00199 per request

How credits are counted

One credit = one request. No matter how many results come back — replies, comments, search pages — you pay for the call, not the output size.

Your first successful payment unlocks unlimited API keys on the account, including pay-as-you-go credits.

No monthly commitment — buy only what you need
Credits never expire — they stay until you use them
Same API, same MCP access, same data quality
∞ req/min

Get API key

Credits never expire

Buy once, use whenever. There's no monthly reset, no pressure to hit a quota, no wasted credits at the end of a billing cycle.

No strings attached

No subscription to cancel, no seat minimums, no contract to negotiate. Start, pause, or scale whenever you want.

Full access from credit one

Every endpoint, MCP included, is available on credits. You're not on a limited tier — you get the 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 about Apify?

The same scraper runs as an actor on Apify at apify.com/neatrat/twitter-scraper. If you already live in Apify — schedules, datasets, webhooks — use it there. Same data, different delivery.

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.

Ready to pull X/Twitter data into your stack?

Free tier included. No credit card. Start hitting endpoints in two minutes.

Get started free View pricing →

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.

Twitter/X data. Without the scraping.