X is moving legacy Basic API plans to pay-per-use as the migration starts trending on X

news

X says its legacy Basic API plans are being deprecated and migrated automatically to the newer pay-per-use model, a pricing change now getting clear traction across X and the X developer community.

Official X Developers image from the pay-per-use migration announcement page

What happened

X has announced that its legacy Basic API plans, both monthly and annual, are being deprecated and automatically moved to the company’s newer Pay-Per-Use (PPU) model. The shift is not just a pricing-page cleanup. It changes how existing self-serve developers are billed, how remaining annual value is handled, and what default spending settings kick in after migration.

The timing matters because this is landing after X already spent the past several months pushing its developer business toward credit-based usage. The company formally launched X API pay-per-use earlier this year, but this new update goes further by moving legacy Basic subscribers over automatically instead of leaving the old plans in place indefinitely.

What the official source confirms

The official announcement on X Developers Community says legacy Basic plans are being deprecated and that all Basic subscribers will be automatically migrated to the flagship pay-per-use plan. According to X, this automatic migration begins after June 1, 2026, with each account moving over at the end of its current billing cycle.

X also spells out the migration mechanics in detail. For Basic monthly subscribers, the current subscription ends at cutover and the account moves to PPU with no required action. For Basic annual subscribers, X says the remaining prorated value of the annual fee will be converted into PPU credits, and those credits will expire after the equivalent number of prorated months.

The company also confirms the default post-migration settings: auto-recharge enabled at $200 when the balance drops below $10, plus a default monthly spend limit of $5,000. Developers can change those settings later in the Developer Portal. If they do not want to move to PPU, X says they must opt out before June 1, 2026, but doing so means losing API access after the cutover date.

That update lines up with X’s broader official pricing documentation, which now frames the X API around pay-per-usage with no subscriptions, upfront credit purchases, per-endpoint pricing, real-time tracking, and optional auto-recharge. X’s official changelog also shows that pay-per-use was already launched as the main strategic pricing direction for the platform earlier this year.

Why the story is trending on X

This is getting traction on X because it affects a very specific and very real group: developers already paying for legacy Basic access. The official @XDevelopers post about the migration is circulating on X with a blunt message that monthly and annual Basic plans are being deprecated and moved to PPU after June 1.

That kind of announcement spreads fast because it is not abstract platform strategy. It directly changes billing behavior, spending controls, and API continuity for existing customers. Even developers who already expected X to favor usage-based pricing are paying attention because automatic migration, prorated annual credits, and opt-out consequences are all practical details that can affect budgets and production access.

What this means for developers, builders, and product teams

For indie developers and small teams, this is a cleaner model in one sense: costs can now scale with actual API use instead of sitting behind a fixed Basic subscription. That is attractive for seasonal products, experiments, and lightweight internal tools that do not need steady monthly volume.

But the flip side is cost variability. Teams that were used to the predictability of a flat plan now need to think more carefully about request volume, auto-recharge behavior, deduplication windows, and spend limits. The migration also makes monitoring more important, especially for apps that read a large number of posts or users and could burn credits faster than expected.

Strategically, the bigger signal is that X seems done treating legacy self-serve subscriptions as a long-term parallel path. The platform is consolidating around credit-based billing, tighter usage controls, and a more explicit monetization model for developer access.

What remains unclear

What is still unclear is how smooth this transition will be in practice for developers with older project setups, edge-case billing histories, or existing operational assumptions built around the Basic plan. X explains the financial rules, but not every migration-side implementation detail.

It is also not yet clear how many developers will see lower costs under PPU versus simply more billing complexity. That answer will depend heavily on workload shape, not just raw request count. For some teams this could be more flexible. For others, it may just make the economics harder to forecast.

Sources