X API Pay-Per-Use,
Actually Explained

On February 6, 2026, X made pay-per-use the default pricing model for its API and discontinued the free tier for new developer signups. If you create a developer account today, every request costs money from the first call. New signups received a small one-time credit voucher to test with, but it is not a free tier and it does not cover production usage.

The old subscription tiers went with it. Basic ($200/month) closed to new signups in February and X began auto-migrating remaining Basic subscribers to pay-per-use on June 1, 2026, converting the prorated remainder of annual fees into credits. Pro ($5,000/month) and Enterprise contracts still exist for high-volume and streaming use cases.

Pay-per-use is honest pricing, and for some workloads it is a genuine improvement: a hobby bot that posts a few plain tweets a day now costs single-digit dollars instead of $200. But the rates punish two things hard: posts that contain links, and anything that reads. The rest of this page shows exactly where the money goes.

There is no invoice-at-the-end-of-the-month model for regular developers. You prepay: buy credits in the X Developer Console, and every API request debits your balance at the rates above. When the balance hits zero, your calls fail.

You can set spending limits per billing cycle, which you should do on day one. A retry loop that keeps re-posting on failure, or an agent stuck reading a firehose of search results, will burn credits at machine speed. The limit is the only guardrail between a bug and your card.

X also runs a rebate: spend enough in a billing cycle and you get a percentage back, scaling from nothing below $200 up to 20% at $1,000 or more. The catch is the rebate is paid in xAI API credits (for Grok models), not X API credits. If you do not use xAI, the rebate is worth nothing to you.

One more thing that surprises people: XMCP, the official X MCP server, bills through the same system. Every tool call your agent makes through XMCP, reads and posts alike, debits your pay-per-use credits and requires your own developer account.

To be fair to X: for plain posting, it is not expensive anymore. $4.50 a month for a 10-tweets-a-day bot undercuts every scheduling tool on the market, including this one. If that is your whole workload, use pay-per-use and skip the middlemen.

The expense concentrates in three places. The link fee: any post containing a URL costs $0.20, a 13x multiplier introduced in April 2026 that turns every RSS bot, blog-promotion workflow, and product-launch thread into the priciest thing you run. Reads: $0.005 per post returned sounds tiny until your agent monitors mentions and searches for context, at which point reading becomes 75% of the bill (see the third scenario above). And volume: anything past 2 million post reads a month, or needing filtered streams and archive search, pushes you into Pro at $5,000/month.

There is also the cost that never shows on the invoice: the X developer account application, OAuth 2.0 with PKCE, refresh token rotation, and rate limit handling. That is engineering time you spend before the first tweet posts, and maintenance you carry forever. The X API rules for AI agents guide covers what else you sign up for when you automate directly against X.