Best Twitter/X Scraper APIs in 2026
Honest comparison of the best Twitter/X scraping APIs in 2026. FetchLayer, ScrapeCreators, Apify, ScraperAPI, and Tweepy compared side by side.
Short answer: for reading public tweets, replies, profiles and follower lists without an X developer account, FetchLayer’s Twitter/X API has 11 endpoints at $1.99 per 1,000 requests (30 free to start) and works as an MCP server at https://mcp.fetchlayer.dev. TwitterAPI.io and SocialData are the cheapest per-tweet specialists, ScrapeCreators and Apify are the main multi-platform alternatives, and X’s own API now charges $0.005 per post read. The full comparison is below.
The Twitter/X data market changed in 2026. X dropped its Basic and Pro subscriptions for new developers and moved to pay-per-use, which made the official API usable for small jobs and expensive for large ones. Meanwhile, specialist APIs undercut it per tweet, and most of them now support AI agents over MCP.
We compared seven options on price, endpoints, follower-graph access and AI-agent support. Every price below comes from each provider’s own pricing page or docs, checked on 4 November 2026.
Disclosure: this is written by the team behind FetchLayer, one of the tools compared. We’ve tried to be accurate about what each option does and doesn’t do, but we’re not neutral. If you spot something out of date, tell us and we’ll fix it.
Quick comparison
| Tool | Type | Twitter/X endpoints | Price | Unit billed | Followers / following | Free to try | MCP server |
|---|---|---|---|---|---|---|---|
| FetchLayer | Twitter/X API | 11 | $1.99 per 1,000 requests | Request (a page of results, 25 by default) | Yes, plus verified followers | 30 requests | Yes |
| X API (official) | Official API | Full | $0.005 per post, $0.010 per user | Resource read | $0.010 per account | $20 credit after first purchase | Not checked |
| TwitterAPI.io | Twitter/X API | Not checked | $0.15 per 1,000 tweets | Tweet returned | Not checked | Up to $1 | Not checked |
| SocialData | Twitter/X API | Not checked | $0.20 per 1,000 results | Result | Not checked | Not stated | Not checked |
| ScrapeCreators | Multi-platform API | 7 | $47 for 25,000 credits | Credit | No | 100 credits | Yes |
| Apify (Store actors) | Scraping platform | Varies by actor | ~$0.15–$0.40 per 1,000 tweets | Result | Actor-dependent | $5 monthly usage | Yes (platform-wide) |
| ScraperAPI | General scraping API | None (raw HTML) | $49/mo for 100,000 credits | Credit | No | 5,000 credits, 7 days | Yes (page fetch only) |
Reading the units: per-tweet services charge for every tweet returned. A FetchLayer request returns a page of results (25 tweets by default), so 1,000 tweets are 40 requests, about $0.08 at pay-as-you-go rates. X’s own API charges per post read: 1,000 posts cost $5.
1. FetchLayer
FetchLayer’s Twitter/X API is a dedicated X data API with 11 endpoints: search (Top, Latest, People, Media and Lists), tweet detail, replies, user profiles and “about” details, user tweets and replies, followers, following, verified followers, and video transcripts.
What stands out:
- Follower graph at the same price. Followers, following and verified followers cost the same as any other request. On X’s API every follower entry is a $0.010 read.
- Pages, not items. One request returns a page of tweets or accounts (25 by default), which makes large pulls cheap.
- Three ways in. REST from any language, a typed npm package (
@fetchlayer/twitter, source on GitHub), and an MCP server for Claude, ChatGPT, Cursor and other agents. - No X account, tokens or cookies on your side.
Pricing: 30 free requests, no card. Then $1.99 per 1,000 requests pay-as-you-go, or monthly plans from $25 (15,000 requests) to $500 (1,000,000 requests, $0.50 per 1,000). Failed requests are never billed, and there’s no requests-per-minute cap (pricing).
Best for: developers who need search, timelines and follower graphs from code or an AI agent, at volume.
Limitations: read-only. It can’t post, like or send DMs; for those you need X’s own API. Video transcripts exist only where X has captions, which in our measurements was 17.5% of videos.
2. X API (official) and Tweepy
X’s own API, which Tweepy wraps for Python, moved to pay-per-use in February 2026. New developers can’t buy the old Basic or Pro subscriptions any more. You buy credits, and each resource read is billed:
- Posts: $0.005 per post read
- Users: $0.010 per user read
- Followers / following: $0.010 per account returned
- Your own data (“owned reads”): $0.001 per resource
- Writes: $0.015 per post created ($0.20 with a link)
Pay-per-use is capped at 3 million post reads a month; beyond that, X sells Enterprise contracts. The same resource read twice in one UTC day is billed once. New accounts get $20 of credit after their first purchase.
What stands out:
- The only official route, and the only one that can post, like, reply and DM
- No subscription or minimum
- Tweepy is a mature Python library for it
Best for: write actions, apps acting on behalf of their users, and small read volumes.
Limitations: reads get expensive fast. A pull of 100,000 tweets costs $500, and a 50,000-follower list costs $500. You also need an X developer account and OAuth setup.
3. TwitterAPI.io
TwitterAPI.io is a specialist X data API priced per item returned.
What stands out:
- $0.15 per 1,000 tweets, among the lowest per-tweet prices we found
- Up to $1 of free credit to test (expires after 31 days)
Pricing: per item returned, with a minimum charge of $0.00015 per call. Profile lookups are priced separately, and batch lookups are cheaper per profile.
Best for: tweet-heavy pipelines that want simple per-tweet billing.
Limitations: per-item billing scales linearly with what you pull. Compare it with page-based pricing on your actual page sizes.
4. SocialData
SocialData is another X-focused API, at $0.20 per 1,000 results, with a balance that doesn’t expire.
Best for: teams that want a simple prepaid balance for tweet and user lookups.
Limitations: per-result billing, like TwitterAPI.io. We couldn’t confirm the free allowance on its site.
5. ScrapeCreators
ScrapeCreators covers X alongside TikTok, Instagram, YouTube and Reddit. Its X section has seven endpoints: search, profile, user tweets, tweet, transcript, community and community tweets.
What stands out:
- One vendor for many social platforms
- Credits never expire; most requests cost 1 credit
- An official MCP server, CLI and Claude Code skill
Pricing: 100 free credits. Freelance is $47 for 25,000 credits ($1.88 per 1,000); Business is $497 for 500,000 ($0.99 per 1,000).
Limitations: no followers or following endpoints. Its docs say user tweets returns up to 100 popular tweets rather than the latest, and search runs over Google-indexed results.
6. Apify (tweet scraper actors)
Apify is a scraping platform with a marketplace of “actors”. Its most-used tweet scrapers charge per result: about $0.40 per 1,000 tweets for the most popular one, and $0.15–$0.25 for several others.
What stands out:
- Scheduling, storage, webhooks and integrations built in
- An official MCP server (mcp.apify.com) that can find and run actors
- Many actors to choose from
Pricing: platform plans from free ($5 of monthly usage) to Starter at $19, Scale at $199 and Business at $999 a month, plus each actor’s per-result price.
Limitations: quality, output format and maintenance vary by actor author, and actors break when X changes.
7. ScraperAPI
ScraperAPI is a general-purpose scraping API: you send any URL and get the page back.
Pricing: from $49 a month for 100,000 credits; a 7-day trial includes 5,000 credits.
Limitations: no structured X endpoints. You get HTML and parse it yourself, and keep that parser working as X changes its pages. Its MCP server fetches pages; it doesn’t return tweets as data.
Feature comparison
| Feature | FetchLayer | X API | TwitterAPI.io | ScrapeCreators | Apify actors | ScraperAPI |
|---|---|---|---|---|---|---|
| Keyword search | ✓ (Top, Latest, People, Media, Lists) | ✓ | Not checked | ✓ (Google-indexed) | Actor-dependent | ✗ |
| Tweet detail and replies | ✓ | ✓ | Not checked | Tweet only | Actor-dependent | ✗ |
| User profile | ✓ | ✓ | Not checked | ✓ | Actor-dependent | ✗ |
| Latest user tweets | ✓ | ✓ | Not checked | Popular only | Actor-dependent | ✗ |
| Followers / following | ✓ | $0.010 each | Not checked | ✗ | Actor-dependent | ✗ |
| Verified followers | ✓ | Not checked | Not checked | ✗ | Actor-dependent | ✗ |
| Video transcripts | ✓ (where captioned) | Not checked | Not checked | ✓ | Actor-dependent | ✗ |
| Post, like, DM | ✗ | ✓ | Not checked | ✗ | ✗ | ✗ |
| MCP server | ✓ | Not checked | Not checked | ✓ | ✓ | ✓ (page fetch) |
| No X account needed | ✓ | ✗ | ✓ | ✓ | ✓ | ✓ |
What 100,000 tweets cost
| Option | Cost for 100,000 tweets |
|---|---|
| X API pay-per-use | $500 |
| Apify actors | ~$15–$40 |
| SocialData | $20 |
| TwitterAPI.io | $15 |
| FetchLayer, 25 per request (4,000 requests) | ~$8 at pay-as-you-go rates |
Prices are list prices as of 4 November 2026; monthly plans lower FetchLayer’s rate further.
Which should you pick?
You need to post, reply or act on behalf of users → X’s official API. Nothing else can.
You need tweets, timelines and follower graphs at volume → a dedicated read API. FetchLayer bills per page, so large pulls and follower lists stay cheap.
You want simple per-tweet billing for modest volumes → TwitterAPI.io or SocialData.
You need many social platforms from one vendor → ScrapeCreators, accepting that its X coverage has no follower data. If the goal is brand or keyword tracking across X, Reddit and TikTok, a social listening API that covers all three on one key is the shorter path.
You already run jobs on Apify → a tweet scraper actor (check its maintenance record).
You use Claude, ChatGPT or Cursor → pick an option with an MCP server that returns tweets as data: FetchLayer, ScrapeCreators or Apify.
For the hands-on version, see How to Scrape Twitter/X in 2026, and for the official API’s pricing in depth, Twitter API Alternatives in 2026.
Frequently asked questions
What’s the best Twitter scraper API in 2026?
For read-only data at volume (search, timelines, replies, followers), a dedicated API: FetchLayer bills $1.99 per 1,000 requests, each returning a page of tweets, and works over MCP. For per-tweet billing, TwitterAPI.io ($0.15 per 1,000 tweets). For posting or acting for users, X’s own API.
How much does the X API cost now?
Pay-per-use since February 2026: $0.005 per post read, $0.010 per user or follower read, $0.015 per post created, capped at 3 million post reads a month. There are no subscription tiers for new developers.
Is there a free Twitter API?
Not from X: you buy credits, and new accounts get $20 after their first purchase. Third-party APIs offer small trials: FetchLayer gives 30 requests, ScrapeCreators 100 credits, and TwitterAPI.io up to $1.
Can I get someone’s followers without the X API?
Yes. FetchLayer’s followers, following and verified-followers endpoints return any public account’s lists, a page of accounts per request. See how to export Twitter followers to CSV.
Is it legal to scrape Twitter/X?
Accessing publicly visible data is generally lawful in the US (hiQ Labs v. LinkedIn), but X’s terms restrict automated access, so review your use case and how you store personal data. This isn’t legal advice.
Can I switch between tools easily?
The REST APIs all take HTTP requests and return JSON, so switching means changing the endpoint and mapping the response fields. If you rely on follower graphs or write actions, check that the new provider supports them first.
Last checked: 4 November 2026. Prices and features change, so check each provider’s site before you buy.