Who Is Paying for the X API Now? One Vendor Finally Answered on Its Pricing Page
- X moved to pay-per-usage credits for new developers in February 2026, which changed the cost base for every scheduler that supports it.
- There were only three obvious responses available: raise prices, move X to a higher tier, or quietly drop X support.
- Zernio takes a fourth: it states on its pricing page that X API usage is passed through at exact rates with zero markup.
- For you, the practical question is whether your X cost is variable and visible or bundled and invisible, and which one suits your posting volume.
In February 2026, X closed its free developer tier to new applicants and moved to pay-per-usage credits. We wrote about what that meant for individuals in X API free tier limits in 2026.
The more interesting question has been open ever since. Every scheduling tool that supports X sits on that API. The cost base changed underneath all of them simultaneously. Where did it go?
We have checked pricing pages every week since. Almost nobody says. This month one vendor does.
The three obvious moves, and the one nobody had taken
When an input cost rises for every supplier at once, the responses are predictable:
- Raise prices across the board. Visible, unpopular, and invites churn to whoever has not moved yet.
- Move X into a higher tier. Quiet, effective, and shows up as a feature-matrix change rather than a price change. Hardest for a customer to spot.
- Drop X support. Cleanest, and only viable if X is not why people bought you.
Zernio pricing page, checked first-hand on 14 September 2026, contains a fourth option written in plain language: X/Twitter API passed through at X exact rates, zero markup.
That is pass-through metering. Your X usage is billed at cost, separately from the account fee, and the vendor takes no margin on it.
Why this is better and worse than a bundled price
| Pass-through | Bundled into the plan | |
|---|---|---|
| If you rarely post to X | Cheaper. You pay near nothing | You subsidise heavy X users |
| If X is your main channel | More expensive and variable | Cheaper. You are the one being subsidised |
| Predictability | Poor. The bill moves with usage | Good. One number |
| Transparency | High. You can see the platform cost | Low. You cannot tell what X costs you |
| Risk if X raises rates again | Lands on you immediately | Lands on the vendor, then on you at renewal |
Neither is obviously right. But there is an asymmetry worth naming: with pass-through you find out about a platform price rise the month it happens, and with bundling you find out at renewal, after it has been absorbed and re-marked. Information arriving late is still information you paid for.
A bundled price is a bet the vendor makes on your behalf without telling you the odds. Pass-through hands you the ticket and the odds together.
What to check on your own tool this week
Whatever you use, these four checks take ten minutes and are worth doing before your next renewal.
- Is X still on your tier? Open the current feature matrix, not your memory of it. Option two above is the most common move and the least announced.
- Is there a separate X add-on? Metricool, for instance, lists X analytics as an add-on on Starter and includes complete X analytics only from Advanced. That is a real example of the platform cost surfacing as a tier boundary.
- Has the posting allowance for X specifically changed? Some tools now cap X separately from other networks.
- What happens if you exceed? Blocked, throttled, or billed. All three exist in this category and the difference matters.
The broader pattern this belongs to
This is one instance of something that keeps recurring: platform-side costs and limits get translated into vendor packaging, and the translation is where the information is lost.
Blotato started printing up to 900 TikTok posts a month on its entry plan this month — a platform-derived ceiling rendered as a plan line. Metricool splits X analytics across tiers. Postiz self-hosted documentation warns that getting your social apps approved takes a long time, which is the platform credential cost surfacing as a self-hosting caveat.
Each of those is a vendor being unusually transparent about something that is normally invisible. Worth rewarding with attention, because the default in this category is silence, and silence always favours whoever has more information.
The only way to opt out of the translation entirely is not to sit on the platform API — publishing from your own logged-in browser sessions instead, which is the architecture we use at NoobClaw. It removes API cost pass-through and client audit status from the picture, and adds a requirement that your own machine is running. As always, a different constraint rather than no constraint.
Related: Zernio vs Post Bridge for the full Zernio pricing structure, and the cheapest scheduler per account for how platform costs distort per-unit comparisons.
What a silent cost change looks like from the customer side
Worth spelling out, because most people never notice one happening and then cannot explain why their tool feels worse.
The signature is not a price rise. It is a sequence of small edits, each individually reasonable:
- A platform quietly moves from the base tier feature list to the tier above.
- A feature that used to be included becomes an add-on with its own line item.
- An allowance that was described as unlimited acquires a fair-use footnote.
- A platform disappears from the integration list entirely, with no announcement, usually between redesigns.
None of those is a price change, so none of them triggers the email you would get if your monthly fee went up. The bill is identical and the product is smaller. That is why comparing your current feature matrix against your memory of it is a genuinely useful annual habit.
The most expensive changes in this category arrive as edits, not as invoices.
There is a screenshot habit worth adopting if you run anything at scale: the day you subscribe, save the pricing page and the feature matrix as a PDF. It takes thirty seconds and it is the only way to have an argument about what you were sold. We have had to reconstruct vendor changes from archive snapshots more than once, and half the time the snapshot does not exist for the week that mattered.
This is also why we now re-scrape any competitor number on the day we publish it rather than trusting a record from a month ago. Within five days one vendor produced an entirely different pricing structure — different currency, different tier names, different quotas — with no announcement anywhere. A price older than a week is a hypothesis.
FAQ
Does this mean X posting is now expensive for everyone?
Not necessarily — it means the cost is no longer zero for new developer applications, and it has to appear somewhere in the chain. Whether that reaches you as a higher plan price, a tier restriction or a usage line depends entirely on your vendor packaging choice.
Can I still get free X API access?
Existing arrangements and new applications are not the same situation, and the terms have changed more than once. Check the current developer documentation rather than an article, including this one, because this is exactly the kind of fact that goes stale quietly.
Should I switch tools over this?
Only if X is a large share of your posting and your current tool has quietly moved it up a tier. Otherwise the difference is a few dollars, and switching costs you an afternoon of reconnecting accounts.