Is the Twitter API Free?
Short answer: No. The official X (Twitter) API has no free tier — it bills pay-per-usage at $0.005 per post read ($5 per 1,000), $0.010 per user read, and $0.015 per post created. X grants $20 in free credits when you save your first eligible card, about 4,000 post reads, and access requires an X developer account. Pay-per-usage tops out at 3 million post reads a month; beyond that, Enterprise pricing is not published.
Third-party providers offer a different model — TwitterAPI.io, Scrapfly, ScrapingBee, and ScraperAPI each grant free starter credits on signup with no card required (on TwitterAPI.io, up to $1 in free credits for new accounts that pass the bot check; expires after 31 days; see /pricing), then move to per-call pay-as-you-go pricing that starts in cents per thousand calls. There is no developer account to set up and no card to save before your first call.
All the options, side-by-side
| Option | Price | What you get | Access | Best for |
|---|---|---|---|---|
| X API — Starter credits | $20 free credits | ~4,000 post reads; first auto-recharge matched up to $50 | Developer account + saved card | Evaluation |
| X API — Pay-per-usage | $0.005/post read, $0.010/user read | Up to 3M post reads per month | Developer account + saved card | Prod workloads |
| X API — Enterprise | Not published | Above 3M post reads per month | Interest form | Enterprise scale |
| TwitterAPI.io — Free starter | $0 | Up to $1 in free credits for new accounts (bot check, expires after 31 days), no card | Google sign-in, 5 min | Evaluation |
| TwitterAPI.io — Pay-as-you-go | $0.15 per 1,000 tweets, $0.18 per 1,000 profiles | No monthly minimum | Top up balance anytime | Production at scale |
Official X API pricing as published by X Corp; verify at docs.x.com/x-api/getting-started/pricing before purchasing. TwitterAPI.io is not affiliated with X Corp.
What "free" actually means in practice
"Free tier" is a marketing term across this whole category. The substantive question is: what can I actually do on the free tier before I have to pay? Three things determine that.
- Volume ceiling. Official starter credits are $20, about 4,000 post reads at $0.005 each. Third-party free starters typically grant 1,000–5,000 credits or equivalent, which goes further per request because per-request costs are lower.
- Metering. The official API meters every resource separately — posts, users, follower lists and DM events each carry their own rate. Third-party tools usually expose the full surface on the free starter so you can evaluate end-to-end.
- Time to first call. The official API requires an X developer account and a saved payment card before the first call. Third-party tools are typically API-key-on-signup, five minutes from sign-up to first response.
When does the free tier stop being enough?
Three concrete signals it's time to leave the free tier:- You hit the monthly call ceiling more than once. On the official API, the $20 starter credit is about 4,000 post reads — if your single-script test exhausts it in an afternoon, your production workload will too.
- You need an endpoint the free tier doesn't expose. Real-time streaming, historical search, or write actions are the common ones. Don't wait for users to complain — switch when you know the feature is on your roadmap.
- You start hitting platform-side rate limits during normal operation. Free-tier rate limits are not the ceiling of the underlying platform; they're the ceiling of the marketing tier. Paid access raises them substantially.
Caveats worth knowing
Unit prices compound with volume
On the official API, 100,000 post reads cost $500 and 1 million cost $5,000, before any user or follower reads at $0.010 each — and past 3 million post reads a month you need an Enterprise agreement. Most third-party paid plans also meter per call. Always compute total cost on your actual expected volume, not just the headline unit price.
Free starter credits are for evaluation
Third-party free starter credits are intended to evaluate the API surface end-to-end, not to power a production workload indefinitely. The difference from the official API is that the post-evaluation paid path is priced in cents per thousand calls rather than $5 per 1,000 post reads — so the upgrade isn't a cliff.
FAQ
Is the Twitter API really free?+
No. The official X API no longer has a free tier: it bills pay-per-usage, with no subscription. X grants $20 in free credits when you save your first eligible card and matches your first auto-recharge up to $50. At $0.005 per post read, $20 covers about 4,000 post reads, so for anything beyond a hobby script the credits run out quickly. You also need an X developer account.
What does the official X API actually cost?+
It is pay-per-usage: $0.005 per post read ($5 per 1,000, so 100,000 posts cost $500 and 1 million cost $5,000), $0.010 per user read, follower/following read or DM event read, and $0.015 per post created ($0.200 if the post contains a URL). Pay-per-usage is capped at 3 million post reads per monthly billing cycle; above that you request Enterprise through an interest form, and X does not publish an Enterprise price. Access requires an X developer account and a saved payment card.
Are there genuinely free third-party Twitter APIs?+
Yes — several third-party providers offer free starter credits (no card) so you can evaluate the surface end-to-end. TwitterAPI.io grants up to $1 in free credits to new accounts that pass the bot check; the credit expires after 31 days (see /pricing). Scrapfly and ScrapingBee each grant 1,000 free credits on signup. ScraperAPI grants a 7-day trial with 5,000 credits. None of these require an X developer account or a saved card to start.
Is there a catch with the free third-party tiers?+
Free starter credits are intended for evaluation, not for indefinite production use. Once your workload is non-trivial you will move to a paid balance. The difference is the rate: third-party paid usage is priced in cents per thousand calls, while the official API charges $5 per 1,000 post reads.
What is the cheapest way to get real Twitter / X data?+
For most workloads the cheapest path is a third-party API at the per-call rate. TwitterAPI.io for example bills per credit at 100,000 credits = $1, with bulk tiered pricing on follower endpoints (down to about $0.0225 for 5,000 follower IDs). Match the endpoint to the data you actually need — pulling IDs only is 50% cheaper than pulling full profiles when all you need is the graph.
Skip the developer-account setup
Up to $1 in free credits for new accounts (bot check, expires after 31 days) on Google sign-in, no card, no developer account. Pay as you go after that.