X API Goes Pay-Per-Use: What Indie Hackers Should Build Now

X officially launched pay-per-use pricing for the X API on February 6, 2026 (X developer changelog). No monthly subscription: you buy credits in the Developer Console at console.x.com, and they're deducted as you make requests. Pay-per-use accounts are capped at 3 million post reads per billing cycle; above that, X points you to Enterprise.

The shift was telegraphed. X announced a closed pilot on October 20, 2025, and TechCrunch reported that selected developers received a $500 voucher to build with it. At the February launch, X said Basic and Pro remained available to existing subscribers, who could opt in to pay-per-use. As of October 10, 2026, the docs.x.com pricing page lists only pay-per-use credits and Enterprise.

The prices have already moved once. Effective April 20, 2026, X raised post creation from $0.010 to $0.015, set posts containing a URL at $0.20 each (summoned replies stay at $0.010), cut reads of your own data to $0.001, and removed follows, likes and quote posts from all self-serve tiers (X developer changelog, April 16, 2026).

X gives new pay-per-use accounts up to $70 in free X API credits, and no voucher code is needed: a one-time $20 when the account saves its first eligible credit or debit card, plus a one-time match of the first successful auto-recharge, capped at $50 (X developer docs, rolling out since October 2, 2026). Both are applied automatically and appear in the Developer Console within about a minute.

The fine print matters. The free X API credits expire 3 months after they are granted, they are spent before your purchased credits, and each incentive can be earned once per account and once per physical card. Prepaid cards do not qualify, and accounts that already had a card on file or a previous payment do not get the $20.

Two older offers explain the "X API voucher" searches: the $500 voucher TechCrunch reported for selected pilot users in October 2025, and the one-time $10 voucher X gave recently active Legacy Free tier users at the February 6, 2026 launch. X's docs describe no recurring monthly free credit allowance and no free tier on the current pricing page.

This pricing model isn't universally cheaper. It's a bet on attracting a large volume of small developers while extracting more from heavy users. Here's where the math lands:

For the past two years, X's API pricing was a wall. The $200/month minimum meant that any project built on X data needed to generate revenue from day one just to cover API costs. Side projects died. Bots went offline. Beloved third-party apps like Tweetbot and Twitterrific shut down permanently.

Pay-per-use changes the math entirely. You can now validate an idea on X data for $5–$50/month. Build an MVP, test it with real users, and only scale your API spending when your product actually generates revenue. That's the kind of economics that lets indie hackers experiment.

X itself described pay-per-use as "built for indie builders, startups, and hobbyists" (X developer changelog, February 6, 2026). Whether they follow through on developer relations remains to be seen, but the pricing finally makes it possible to build without committing $2,400/year upfront.

The pay-per-use model creates a specific sweet spot: tools that need moderate read access (under 50,000 requests/month) and deliver enough value to charge $29–$99/month. Here are five ideas that fit, with API costs recalculated at X's October 2026 rates.

Here's the business model shift most people are missing. Pay-per-use pricing doesn't just make it cheaper for developers to build on X—it creates a new product category: BYOK (Bring Your Own Key) tools sold as one-time purchases.

Think about it. Existing X tools like Typefully, Hypefury, and Tweet Hunter charge $29–$49/month because they're absorbing the API costs on your behalf. Those costs were fixed at $200/month minimum, so the SaaS model was the only way to make the math work. But now that X charges per request, a developer can ship a self-hosted or desktop app where the user plugs in their own X API key—and charge a one-time fee instead.

The user pays X directly for their usage (which might be $5–$30/month depending on volume), and pays the tool creator once. No recurring fees. No middleman markup on API costs. The tool creator has zero marginal cost per user and keeps 100% of the sale.

The April 2026 pricing update made BYOK even stronger. X's "Owned Reads" rate charges $0.001 per resource when an app reads the data of the same user who owns that developer app—their own posts, mentions, bookmarks, followers and lists (docs.x.com). In a BYOK tool the user is the app owner, so pulling 5,000 of their own posts costs $5 instead of $25.

Before you go all-in building on X's API, the elephant in the room: trust. X killed free API access overnight in 2023. They doubled Basic pricing from $100 to $200. Third-party apps that had served millions of users for over a decade were wiped out with weeks of notice.

Pay-per-use has not ended the repricing. Ten weeks after launch, X announced on April 16, 2026 that from April 20 posts with a URL would cost $0.20 instead of $0.01, and that follows, likes and quote posts would leave self-serve entirely (X developer changelog). Any product whose margins depend on a single X API line item should assume that line item can move.

Developers who got burned once are right to be cautious. The question isn't "Is this pricing good?" but "Will it stay stable?" Building a business on a platform that has changed its API terms this aggressively is a calculated risk.

X's move to pay-per-use is part of a broader trend. API pricing across the industry is shifting from fixed tiers to usage-based models—OpenAI, Twilio, and Stripe all price this way. For developers, it means lower barriers to entry but higher costs at scale.

The xAI integration is the most interesting signal. By connecting API spending to AI credits, X is positioning itself not just as a social platform with an API, but as a combined social + AI development platform. If that integration deepens—imagine Grok models trained on real-time X data available to API developers—the opportunity gets significantly bigger.