X restructured its developer API pricing in 2026, replacing its older flat-fee tiers with a pay-per-use model — and that shift directly affects every third-party tool, including Twitter viewers, that reads public posts on your behalf. Understanding these changes explains why some viewer tools have become less reliable or feature-limited this year.
Key Takeaways
- X’s only self-serve API option now is pay-per-use: no flat monthly fee, charged per call instead.
- Posts containing a URL cost roughly 13 times more to read via API than plain-text posts.
- The older $200/month Basic and $5,000/month Pro tiers were phased out through mid-to-late 2026.
- Follow, like, and quote-post actions were removed from all self-serve tiers entirely.
- Higher API costs are a major reason some third-party Twitter tools have shut down, scaled back, or started showing more errors in 2026.
What Changed, In Plain Terms
Historically, developers paid a flat monthly fee for a bucket of API access. As of the April 2026 rate card, X moved its self-serve options to pure pay-per-use pricing: roughly $0.001 per read of your own posts, $0.005 per read of someone else’s public post, and a much higher $0.20 per post if that post contains a URL. The old $200/month Basic tier and $5,000/month Pro tier were deprecated during 2026, automatically migrating existing users to the new pay-per-use structure. Enterprise access, for accounts needing more than 3 million post reads a month, now starts around $42,000/month with custom terms.
Pricing at a Glance
| Tier | Cost | 2026 Status |
|---|---|---|
| Pay-per-use | ~$0.001–$0.20 per read, depending on content type | Only self-serve option now |
| Legacy Basic | Was $200/month | Deprecated; migrated to pay-per-use after June 2026 |
| Legacy Pro | Was $5,000/month | Deprecated August 2026; migrated after September 2026 |
| Enterprise | $42,000+/month, custom | Required above 3M reads/month |
Why This Matters for Viewer Tools Like Sotwe
A Twitter viewer’s whole job is reading public posts and re-displaying them. When the cost of every single read goes up — and the cost of reading a post that contains a link jumps roughly 13x — the economics of running a free tool get harder. This is part of why the third-party viewer landscape has been shifting throughout 2026: some tools have added delays or usage limits, some have shut down (the scheduling tool Hypefury cited the URL-read markup specifically as a factor in exiting X integrations), and others have had to change how frequently they refresh data to control costs.
What This Means If a Viewer Tool Is Acting Up
If a Twitter viewer feels slower than it used to, shows occasional errors, or has trimmed a feature, API cost pressure is a genuinely common explanation in 2026 — not necessarily a sign the tool is broken or unsafe. Keeping a second viewer bookmarked as a backup is a reasonable habit given how frequently the underlying API terms have shifted this year.
Frequently Asked Questions
Why did X change its API pricing in 2026?
X moved toward a usage-based model to better monetize high-volume API consumers, replacing flat monthly tiers with per-call pricing that scales with actual usage.
How much does it cost to read a tweet via the API now?
Roughly $0.001 to read your own post, about $0.005 for a third-party public post, and up to $0.20 for a post containing a URL — reflecting the steep markup X added for link-containing content.
Does this affect me if I just use a Twitter viewer like Sotwe?
Indirectly, yes. Higher API costs affect how viewer tools operate behind the scenes, which can show up as occasional slowdowns or feature limits, even though you aren’t paying anything directly.
Are the old flat-fee API tiers still available?
No. The Basic ($200/month) and Pro ($5,000/month) tiers were phased out during 2026 and existing subscribers were migrated to the pay-per-use model.
Why do link-containing posts cost more to read via the API?
X introduced a specific markup — roughly 13 times the base rate — for posts that contain a URL, as part of its 2026 rate card changes.
