X API Limits in 2026: Rate Limits, Pricing and What You Can’t Do

You build a small bot to post for you. It works for a week. Then you get a 429 error, or a bill that is bigger than you planned. This page has the full rate card, the limits per endpoint and what the API no longer lets you do. At the end: when you don’t need a key at all.

How X API access works in 2026

You pay for what you use. There are no subscriptions, contracts or minimum spend. You buy credits in the Developer Console at console.x.com, and X takes a little for each request.

You can set a spending limit per billing cycle. When the limit is hit, or your balance hits zero, your requests stop until you top up. That protects you from a runaway loop, but it also means your bot can go quiet mid-month.

New accounts get up to $70 in free credits: $20 after your first card purchase, and a match of your first auto-recharge up to $50. They expire after 3 months. X says they are still rolling out. Buying X API credits also earns up to 20% back in xAI credits.

What happened to Free, Basic and Pro?

New developers sign up for pay-per-use. X’s changelog says recently active Legacy Free users got a one-time $10 voucher. It also says Basic and Pro remain available, and existing subscribers can opt in to pay-per-use. Some third-party sites report that Basic and Pro have since been retired, but X’s docs don’t say that yet. If you are on an old plan, check your Developer Console.

Enterprise is custom

Enterprise is for big data jobs: firehose streams, full-archive search at scale and the Engagement API. You apply through X, and there is no public price. If you are reading this page, you probably don’t need it.

X API pricing per post, read and action

Writes are cheap until you add a link. A normal post costs $0.015. The same post with a URL costs $0.20, more than 13 times as much.

From the X API pricing page, checked October 17, 2026.

Three rules change what you really pay.

Every link post pays the link price. X bills per post request. A reply or a thread post is its own request, so a link anywhere in a thread costs $0.20 for that post.

Owned reads are only for the app owner. Since April 20, 2026, reading your own posts, mentions or followers costs $0.001. That only counts when the account is the one that owns the developer app. If you build a tool for other people, their data costs the normal rate.

You pay once a day per item. Read the same post twice on the same UTC day and you are charged once. The count resets at midnight UTC.

What a normal creator’s month costs

Less than you think, as long as you skip links. Say you post 3 times a day for 30 days. That is 90 posts at $0.015, so $1.35. Put a link in 30 of them and the month costs $6.90. Put a link in all 90 and it is $18.

Add some reads for your own stats, like 90 of your own posts at the owned rate, and that is about $0.09 more. So the API bill is rarely the big cost. Your time is. You still need OAuth, media upload, retries, 429 handling and a way to see what worked.

X API rate limits by endpoint

Most limits reset every 15 minutes, a few every 24 hours. Per-user limits apply when you call with a user token. Per-app limits apply to your app as a whole. Go over and you get HTTP 429 until the window resets.

From the X API rate limits page, checked October 17, 2026. “None” means the endpoint has no limit of that kind listed.

How to check your remaining limit

Every response tells you. Read three headers: x-rate-limit-limit is your max, x-rate-limit-remaining is what’s left and x-rate-limit-reset is when the window resets, in Unix time. On a 429, wait until that reset time. Retrying right away just burns more requests.

The 3 million read cap

Pay-per-use plans can read at most 3 million posts per monthly billing cycle. Above that, X sends you to Enterprise. For a posting bot that is far away. For a research or monitoring tool it can come fast: 3 million reads at $0.005 is already $15,000.

What you can’t do with the self-serve X API

The API is now built for posting and reading, not for growth tricks. X removed most of what bots used to do.

From the X changelog and rate limits page, checked October 17, 2026. The rate limits page still lists like and follow endpoints, but the changelog says they were removed from self-serve tiers with the April 2026 pricing update.

How schedulers are reacting to the new costs

They ration link posts. A scheduler pays X for every post you send, so the $0.20 link price lands on them.

Nuelink is open about it. Its help center says “X charges Nuelink $0.20 for every post with a link.” On its Standard plan you get 10 X credits a day. A normal post uses 1 credit, a link post uses 10, and you get 10 link posts a month. A reply with a link counts as a link post too.

ClimbX blocks links in scheduled posts. Links can cut a post’s reach by 50 to 90%, and they cost 13 times more to publish. When you need a link, the Post button opens X and you post it yourself. That costs nothing. Other ways to share a link without the reach hit are in how to share links on X.

Should you build on the X API or use a tool?

Build if you need data or a product feature. Use a tool if you just want to post and grow.

Want your own AI agent to post? ClimbX has an API and an MCP server for that. They allow 5 posts a day per account, with no links. See the ClimbX developer docs and how to get X data through MCP. For a plain scheduling walkthrough, read how to schedule posts and threads on X.

Frequently asked questions

Bottom line

The X API costs $0.015 a post, $0.20 a link post and $0.005 a read, with 100 posts per 15 minutes per user and 3 million reads a month at most. Posting is cheap. Links, replies and growth automation are where it gets expensive or blocked. If all you want is to post and grow, skip the key.