13 September 2026 · Social & Data APIs · 5 min read
I built the X (Twitter) API cost calculator last week and left it with a question I didn't answer at the time: is pay-per-use actually cheaper than the old Basic/Pro/Enterprise tiers, or does X just look cheaper because there's no sticker price to compare against? So I ran three real bot profiles through it — a hobby bot, a growth-hacking bot, and a lead-gen bot — against the legacy subscriptions they'd have needed before February 2026. Two of them came out well ahead. The third one walked straight into the September 21 Search pricing change and nearly tripled its own bill without adding a single extra API call.
Straight from X's pay-per-use pricing, per unit: post reads (search, timelines, lookups) $0.005, user/profile reads $0.010, owned-resource reads (your own posts, mentions, DMs) $0.001, plain post writes $0.015, and posts containing a link $0.20 — roughly 13x a plain write. Legacy subscriptions, still sold to grandfathered accounts but closed to new signups: Basic $200/mo, Pro $5,000/mo, Enterprise from about $42,000/mo on a custom contract.
A small bot posting daily updates and checking its own mentions: 10,000 post reads, 500 profile reads, 1,000 owned reads, 500 plain writes, 50 link posts a month.
| Line | Volume | Rate | Cost |
|---|---|---|---|
| Post reads | 10,000 | $0.005 | $50.00 |
| Profile reads | 500 | $0.010 | $5.00 |
| Owned reads | 1,000 | $0.001 | $1.00 |
| Plain writes | 500 | $0.015 | $7.50 |
| Link writes | 50 | $0.20 | $10.00 |
Total: $73.50/mo against a legacy Basic tier at $200/mo. That's the entire point of pay-per-use for small accounts — Basic made every hobby project round up to $200 whether it used 5% of the tier or 95%. This bot would've been overpaying by more than 2.7x under the old model.
A social-listening bot for a growing brand: 500,000 post reads, 50,000 profile reads, 20,000 owned reads, 5,000 plain writes, 500 link posts a month.
| Line | Volume | Rate | Cost |
|---|---|---|---|
| Post reads | 500,000 | $0.005 | $2,500.00 |
| Profile reads | 50,000 | $0.010 | $500.00 |
| Owned reads | 20,000 | $0.001 | $20.00 |
| Plain writes | 5,000 | $0.015 | $75.00 |
| Link writes | 500 | $0.20 | $100.00 |
Total: $3,195/mo against a legacy Pro tier at $5,000/mo — still $1,805/mo cheaper, but the margin is nowhere near the hobby bot's 2.7x. Post reads alone are 78% of this bill. That's the number to watch as this bot scales: it's a linear cost, not a flat one, so the savings versus Pro shrink every time read volume climbs, and at some point they flip.
This is the bot I built the calculator to think through in the first place. It searches X for mentions of target accounts and resolves the author's profile for every result — the standard shape of a social-listening or lead-gen tool. Say it pulls 200,000 posts a month and resolves a profile for all of them.
Before September 21, 2026, X Search billed at a flat $5 per 1,000 calls, and a lot of integrations treated "one search call" as one billable unit regardless of what it returned. Under that flat model, 200,000 search calls cost $1,000/mo. After September 21, Search split into the same resource-based rates as the rest of the API: $5/1,000 posts fetched and $10/1,000 profiles fetched, billed separately.
| Line | Volume | Rate | Cost |
|---|---|---|---|
| Post reads (search results) | 200,000 | $0.005 | $1,000.00 |
| Profile reads (author lookup) | 200,000 | $0.010 | $2,000.00 |
Total: $3,000/mo — exactly 3x the old flat-rate estimate, and every dollar of the increase comes from the profile-resolution half of the pipeline that used to ride along for free inside the flat per-call price. Nothing about this bot's actual usage changed. The bill did, because the thing it was already doing — look up an author for every result — now has its own line item at double the post-read rate.
If your integration only fetches posts and never resolves the author, the September 21 change doesn't touch you — re-run the numbers anyway to be sure, because "we probably don't do that" is exactly the assumption that got this bot's bill wrong. If you do resolve profiles, price it as two separate lines, not one. And watch the 3,000,000 post-read monthly ceiling on pay-per-use — cross it and X pushes you to a custom Enterprise contract, the same $42,000+/mo tier that made Basic and Pro look reasonable by comparison in the first place.
New to usage-based pricing? Start with the free API-cost guides.
Host your bot: DigitalOcean — $200 free credit ↗ · Hostinger VPS ↗
Rates verified against X's official pay-per-use pricing page, last checked 2026-09-12. Reference estimates — legacy subscription grandfathering, negotiated Enterprise contracts and any future rate changes vary; confirm current pricing at docs.x.com before budgeting.