| Resource | $ / 1,000 | Volume / month | Cost |
|---|
Why X API costs need a per-resource calculator now
For years, budgeting the X (formerly Twitter) API meant picking a subscription: Basic at $200/month, Pro at $5,000/month, or an Enterprise contract for real scale. That made costs predictable but forced everyone into rigid buckets — a hobby bot and a growth-stage growth-hacking tool both had to round up to whichever tier covered their peak month. In February 2026, X flipped the default to pay-per-use: load prepaid credits and pay per resource actually consumed. That's fairer at low volume, but it also means your bill now depends entirely on which resources you call, not a flat monthly number — a search-heavy sentiment tool and a posting bot can use the "same API" and land on wildly different bills.
The line items aren't priced anywhere close to evenly. Reading a post costs about half a cent; reading a user profile costs twice that; a plain post write costs three times the read rate; and a post that contains a link costs roughly 13× more than a plain write. Most of the sticker-shock stories from X API users in 2026 trace back to one of these multipliers being missed during planning — usually the link-post surcharge or the profile-read rate on a pipeline that resolves author details for every post it pulls.
The September 21, 2026 Search pricing change
X Search billing moved off its flat $5-per-1,000-calls rate to the same resource-based split as the rest of the API: $5 per 1,000 posts fetched and $10 per 1,000 user profiles fetched. If your integration searches for posts and stops there, nothing changes. If it also resolves the author's profile for every result — a common pattern for social-listening and lead-gen tools — that half of the query now costs double what post-fetching costs, and it wasn't broken out separately before. Re-run your Search volume through the Post reads and User/profile reads rows above rather than assuming the old flat rate still applies.
The legacy tiers still lurking
If your account predates 2026, you may still be grandfathered onto a legacy subscription: Basic (~$200/mo, roughly 10,000–15,000 post reads and 50,000 writes included, 7-day search only), Pro (~$5,000/mo, ~1,000,000 post reads, full-archive search, filtered/sampled streaming), or a custom Enterprise contract (legacy floor around $42,000/mo). None of these are open to new signups anymore — new developers go straight to pay-per-use. If you're on a legacy tier, compare your included allowance against what this calculator estimates for the same volume on pay-per-use before you let the subscription lapse; at low-to-moderate volume, pay-per-use is usually cheaper, but a Pro subscriber doing millions of reads a month can still come out ahead on the flat rate.
How to use it
1. Estimate monthly post reads — search results, timelines, mentions lookups, anything you fetch that isn't your own account's data.
2. Add user/profile reads separately whenever you resolve author or follower profile data — don't fold it into post reads.
3. Put reads of your own posts, mentions and DMs under owned-resource reads — they're an order of magnitude cheaper.
4. Split your post writes into plain posts and posts containing a link — the link surcharge is the single biggest per-unit rate on the API.
5. Leave the prepaid-credit field at 0 unless you're carrying a real unused balance; X's pay-per-use plan has no recurring free allowance.
Common mistakes
Treating the link-post rate as additive. The ~$0.20 rate is what a link-containing post costs in total, not a surcharge on top of the ~$0.015 write rate — enter link posts only in that row, not both. Lumping profile reads into post reads. They're priced 2× apart, so mixing them undercounts the bill for any pipeline that resolves author data. Assuming the old flat Search rate still applies. As of September 21, 2026 it's split by resource type — re-check integrations built against the earlier flat pricing. Ignoring the 3,000,000 post-read monthly ceiling. Pay-per-use plans can't scale past it; that volume requires an Enterprise agreement with custom pricing. Forgetting owned-resource reads are cheap. Polling your own mentions or DMs frequently is far less costly than polling public search — don't over-throttle it out of habit.
Once you know the X API line, fold it into your whole stack with the API stack cost calculator, and compare it against other search and data sources in the search API guides and data API guides.
Estimate only. X API pricing is reference figures and changes — verify at docs.x.com.