# What the X API actually costs in 2026

> X publishes a rate card, but the bill is decided by things it omits: media multipliers, endpoint choice, and a read cap that changed three times.

URL: https://voicemoat.com/blog/x-api-pricing-2026

## Key facts
- Published: 2026-09-08
- Category: Industry
- Read time: 15 minutes
- Author: Prateek Singh
- Publisher: VoiceMoat
- Topics: X API pricing; Twitter API cost; Pay-per-usage; API rate limits; Developer tooling

## Key points
- Creating a post costs $0.015. A post containing a URL costs $0.200, which is over thirteen times more. That gap arrived in a repricing on 20 April 2026, it was not always there.
- Billable events are not API calls. Reads bill per resource returned, so a search giving you 100 posts bills 100 reads. Writes bill per request, but each attached image counts as its own post creation.
- The same post costs $0.005 or $0.001 to read depending purely on which endpoint you use. That is a five-fold difference decided by a line of code.
- The monthly read cap has been three different things this year. No cap in January, two million in March, no sentence at all in April, three million now. No changelog entry announces any of it.
- The old Basic and Pro plans are not grandfathered. Basic was force-migrated after 1 June 2026 and Pro after 1 September 2026, and X's wording is that the migration is final and cannot be reversed.
- When your balance hits zero the API returns a 402. X's documentation does not mention 402 anywhere, and tells you to expect a 429 instead. We found this out the hard way.

## Related articles
- Will a LinkedIn MCP get your account restricted? What the terms actually say: https://voicemoat.com/blog/is-linkedin-mcp-safe
- Does LinkedIn have an analytics API? Yes, and almost no guide mentions it: https://voicemoat.com/blog/linkedin-analytics-api
- The 10 best Chrome extensions for Twitter/X creators in 2026: https://voicemoat.com/blog/best-chrome-extensions-for-twitter-creators-2026

## FAQ
Q: How much does the X API cost in 2026?
A: It is pay-per-usage with no subscription. Creating a post costs $0.015, or $0.200 if the post contains a URL. Reading a post costs $0.005 per post returned, dropping to $0.001 for your own data through certain endpoints. Pay-per-usage accounts are capped at three million post reads per monthly billing cycle.

Q: Why does a post with a link cost so much more?
A: X charges $0.200 for a post containing a URL against $0.015 without, a difference of more than thirteen times. The rate was introduced on 20 April 2026 alongside a rise in the base rate. X has never published a definition of what counts as containing a URL, so whether an attached image or a shortened link triggers it is unknown.

Q: Is there still a free tier for the X API?
A: Not for new developers. The documentation describes a three-step signup with no approval step and no free allowance. Apps classified as Public Utility Apps keep free scaled access, but no criteria are published and it is granted case by case. Legacy free-tier users received a one-time $10 voucher when pay-per-usage launched.

Q: Are the Basic and Pro plans still available?
A: No. Both were force-migrated to pay-per-usage: Basic after 1 June 2026 and Pro after 1 September 2026. X states that opting out means losing API access and that the migration is final and cannot be reversed. Any guide presenting them as current options is describing a model that has ended.

Q: What is the monthly read cap on the X API?
A: Three million post reads per monthly billing cycle, as stated on four separate documentation pages today. It said two million in March 2026 and had no cap at all in January. None of the changes were announced in the changelog, which is why current articles disagree with each other.

Q: What happens when your X API credits run out?
A: The API returns HTTP 402 with the problem type credits-depleted, and it blocks reads and writes alike. Only adding credit clears it. Note that 402 does not appear anywhere in X's published documentation, which instead describes 429 as covering usage cap exceeded, so handlers written from the docs will miss it.

Q: Do attached images cost extra on the X API?
A: Yes, though the pricing page does not say so. X staff confirmed that each media object is recorded as its own post-creation event in addition to the post itself, so a post with one image bills twice and one with four images bills five times. The chunked upload calls themselves are not billed as post creations.

Source: https://voicemoat.com/blog/x-api-pricing-2026
Site overview: https://voicemoat.com/llms.txt. AI usage policy: https://voicemoat.com/ai.txt.