X API Pricing 2026: What the Twitter API Really Costs

Short answer: X sells API access as pay-per-usage credits, not subscriptions. Reading a post costs $0.005, reading a user costs $0.010, creating a post costs $0.015, and creating a post that contains a link costs $0.200. Pay-per-usage accounts are capped at 3 million post reads per monthly billing cycle. For brand monitoring, post reads are the only line that matters: tracking a brand that generates 100,000 relevant posts a month is $500 a month in raw API spend before you have written any code.

Last updated August 2026. Every rate below was read from X's own developer pricing documentation on August 23, 2026. Nothing here has been estimated to fill a gap.

How much does the X API cost in 2026?

It depends entirely on what you read and how much of it. That is the whole change. The old model was a subscription: you picked a tier, you got a monthly post quota, and your bill was the same whether you used the quota or not. The new model prices each request, so your bill tracks your usage and your usage tracks how loud your brand is that month.

Here are X's published per-unit rates.

The gap between an owned read at $0.001 and a post read at $0.005 is worth sitting with for a second. Reading your own account is cheap. Reading what everyone else says about you is five times the price, and that second thing is the entire product a brand monitoring team needs. X has priced listening as the premium operation, which is a reasonable commercial decision and an expensive one for anybody building on top of it.

What happened to the Basic and Pro tiers?

X's current pricing documentation describes only pay-per-usage credits and does not list Free, Basic or Pro subscription tiers. If you are working from a comparison written before 2026, the $100 or $200 Basic tier and the $5,000 Pro tier it quotes are describing a model that new developers can no longer sign up for.

This matters for anyone reading older build-it-yourself guides. The advice in those posts was usually some version of "Basic is $200 a month and gives you 10,000 posts, so monitoring is cheap." Under credit pricing, 10,000 post reads is $50 and 200,000 post reads is $1,000. The cost is now a straight function of volume, which is fairer for tiny projects and considerably worse for anything with real conversation behind it.

What does brand monitoring actually cost on the X API?

Only one number decides this: how many posts a month mention the things you track. Not how many mention your @handle, which is a small fraction, but how many contain your brand name, your product names, your misspellings, your campaign hashtags and your competitors. Here is the arithmetic at $0.005 a post read.

Two things to notice. The first is how fast this scales past the price of a finished product: a brand generating half a million relevant posts a month is looking at $30,000 a year in raw data fees for a feed of untagged text with no sentiment scoring, no theme clustering, no alerting and no interface. The second is that ceiling. Pay-per-usage is capped at 3 million post reads per monthly billing cycle, so above that you are not comparing prices any more, you are negotiating an enterprise agreement.

The link fee that catches people out

Creating a post costs $0.015. Creating a post that contains a URL costs $0.200. That is a 13x multiplier for including a link, and judging by what people type into search after they read the price list, it is the line that surprises them most.

It does not affect monitoring, because monitoring reads rather than writes. It affects anyone automating publishing: a scheduler pushing 500 link posts a month pays $100 for those alone, against $7.50 if the same posts carried no link. If your plan was to build one tool that both watches X and posts to it, price the two halves separately, because they behave completely differently.

X API rate limits and the 3 million read cap

The cap that shapes architecture is the 3 million post reads per monthly billing cycle on pay-per-usage. Practically, it means a genuinely high-volume brand cannot run on self-serve credits at all. It also means any vendor selling you X monitoring is either operating under that same ceiling or holds an enterprise agreement, and which of the two is true will not be on their pricing page.

This is why so few monitoring vendors publish how far back their X data goes. Historical depth is bought by the post read, so it is a direct cost line rather than a storage decision. Awario is the only tool we have found that states the number publicly: 7 days of X history, attributed on its own site to X API restrictions. We put that against thirteen other products on our comparison of Twitter monitoring tools and X monitoring software, where the same column is mostly the words "not published".

Should you build X monitoring or buy it?

Build if X data is your product. Buy if X data is an input to your job. That sounds glib, so here is the actual comparison for a team that wants to know what people are saying about their brand.

The line people underestimate is the second to last one. An X pipeline is not a project you finish. Credits run out mid-month, a schema field gets renamed, a day of posts silently fails to land and nobody notices until someone asks why the dashboard looks quiet. Watching your own pipeline for late arrivals, volume drops and schema changes is a discipline of its own, and it is real engineering headcount that never appears in the build-versus-buy spreadsheet.

There is a genuine case for building. If you need custom sampling logic, if X data feeds a model you own, or if you are a data business reselling analysis, then owning the pipeline is the point and the API fee is cost of goods. For a marketing, PR or founder-led team that needs to know when a post about them starts spreading, it is a large bill and a permanent maintenance job to reproduce something that already exists.

Is the X API free?

No, not for new developers. X ended free API access as part of the February 2026 move to pay-per-usage, and its current pricing documentation lists per-unit credit rates with no free allowance for reading other people's posts. The only near-free operation is an owned read at $0.001, which returns your own account's data.

Free scraping tools exist and some of them work for a while. They also break without warning, violate X's terms, and cannot be the basis of anything a business depends on. If your budget is genuinely zero, manual searching inside X is the honest answer, with the understanding that it will not tell you when volume spikes at 2am.

How much does the X API cost per month?

There is no monthly subscription figure to quote any more. You load credits and spend them per request, so the monthly cost is your request volume multiplied by the per-unit rate. For read-only brand monitoring, multiply your expected monthly mention count by $0.005 and treat that as the floor. The ceiling on pay-per-usage is 3 million post reads a month, which is $15,000.

What does this mean for your monitoring shortlist?

Three practical things. First, ask every vendor how far back their X data goes for your keywords, in writing, because it is now a cost decision on their side rather than a technical one. Second, ask how often they collect, because 12 hour batching is common on entry plans and it makes X monitoring close to useless when a post is spreading. Third, be skeptical of anything free or suspiciously cheap that claims deep X coverage, because the underlying data has a published price and nobody is getting it for nothing.

EyeOut tracks X alongside web, news, Reddit, Instagram, TikTok, YouTube, forums, podcasts and review sites, scores every mention for sentiment and theme, and fires a graded alert when volume or negativity is genuinely abnormal for that source. Collection is real time on every plan from $59 a month billed yearly, seats included, no annual lock-in. You can see how that works on the Twitter and X monitoring page, compare it against the rest of the market on our Twitter monitoring tools comparison, or read what the wider category costs in our guide to social listening software pricing.