Guide · By PostBoost team · · Markdown
Short answer: the X API is pay-per-use in 2026. You buy credits up front and every request takes its price from them: $0.015 to create a post, $0.200 for a post that contains a link, $0.010 for a summoned reply, and $0.005 for every post you read. There is no free tier and no monthly plan to choose, and pay-per-use accounts are capped at 3 million post reads per billing cycle. To turn your own numbers into a monthly bill, use the free X API cost calculator.
The prices below were checked against X's pricing page and changelog on 20 October 2026. Many pages that rank for this question still quote the old $200 Basic plan or a $0.01 post price; both are out of date.
X API prices at a glance
The rates people ask about most:
| What your app does | Price | Billed per |
|---|---|---|
| Create a post | $0.015 | request |
| Create a post that contains a URL | $0.200 | request |
| Create a summoned reply | $0.010 | request |
| Read a post | $0.005 | post returned |
| Read a user | $0.010 | user returned |
| Read your own data (owned reads) | $0.001 | resource returned |
| Read DM events | $0.010 | event returned |
| Read followers or following | $0.010 | resource returned |
| Create a DM interaction | $0.015 | request |
| Delete an interaction | $0.010 | request |
Reads are charged for every resource that comes back, so a search that returns 100 posts costs 100 × $0.005 = $0.50. Writes are charged once per request. X lists more rows (lists, Spaces, bookmarks, counts, trends, webhook events), and its pricing page notes that current rates are always shown in the Developer Console, so check there before you budget.
How pay-per-use billing works
- Prepaid credits. You buy credits in the X Developer Console. The balance drops in real time and can go slightly negative; requests are then blocked until you top up.
- No contract, no minimum. X lists no subscription fee and no minimum spend.
- Auto-recharge. Set an amount and a threshold (X's example: add $25 when the balance falls under $5). It tops up at most once every 5 minutes and never when the balance is already at zero or below.
- Spending limit. You can set a maximum per billing cycle; once you reach it, requests are blocked until the next cycle.
- Deduplication. A resource you already paid to read is not charged again within the same UTC day, which resets at midnight UTC. X calls this a soft guarantee.
- Read cap. Pay-per-use stops at 3 million post reads per monthly billing cycle. Above that you need an Enterprise plan.
- Usage endpoint.
GET /2/usage/tweetsreturns your daily post consumption, so your own code can watch the meter.
Free credits, not a free tier
There is no free tier, but there are two one-time credits for new paying accounts: $20 after you save an eligible card and make your first credit purchase, and a match of your first auto-recharge, up to $50. X's changelog of 2 October 2026 says these credits expire three months after they are granted.
X also pays back part of what you spend as xAI (Grok) API credits once you link an xAI team to your developer account: nothing below $200 of spend in a billing cycle, 10% from $200, 15% from $500 and 20% from $1,000.
What changed, and when
X's API pricing has moved several times, which is why search results disagree. From X's changelog:
| Date | Change |
|---|---|
| 20 Oct 2025 | Pay-per-use pilot: credits bought up front, $0.005 per post read, $0.01 per user read |
| 6 Feb 2026 | Pay-per-use launched for everyone. Basic and Pro "remain available" and existing subscribers can opt in; recently active legacy Free users got a one-time $10 voucher |
| 23 Feb 2026 | Programmatic replies only allowed when the original post's author has "summoned" your account (by @mentioning it or quoting one of its posts), on self-serve tiers |
| 16-20 Apr 2026 | Pricing update (announced 16 April, owned reads effective 20 April): owned reads at $0.001; post creation set to $0.015 and posts containing a URL to $0.200; summoned replies stay at $0.010. Following, likes and quote posts removed from all self-serve tiers |
| 2 Oct 2026 | Free credit incentives: $20 for a first card, first auto-recharge matched up to $50 |
Before pay-per-use, the self-serve options were flat monthly plans: Basic at $200 and Pro at $5,000 (prices as Open Terms Archive recorded them; plan names from X's 6 February 2026 changelog entry). If you are not already on one of them, pay-per-use is where you start.
What a month actually costs
Every figure below comes from the X API cost calculator at the rates above.
| Example | What it does in a month | Bill |
|---|---|---|
| A blog bot | 90 posts (3 a day), every one with a link to the article | $18.00 |
| The same bot, links removed | 90 plain posts | $1.35 |
| A small product's posting tool | 1,000 posts, 20% with a link | $52.00 |
| A mixed app | 300 posts (10% with a link), 200 summoned replies, 50,000 post reads, 2,000 user reads, 10,000 owned reads | $292.05 |
| Read cap reached | 3,000,000 post reads | $15,000.00 |
Two things stand out. In the 1,000-post example, the 200 link posts cost $40 of the $52, and $37 of that is the premium over the plain-post price. In the mixed app, the 50,000 post reads cost $250, more than everything the app wrote. Writing is cheap unless it carries links; reading is where volume gets expensive.
How to keep your X API bill down
- Count your links first. A link turns a $0.015 post into a $0.200 one. X turns text that looks like an address into a link (see how X counts links), so a bare
example.comin a post may be billed as a link too. - Do not expect a link in your own reply to be cheaper. The $0.010 rate is for summoned replies, where the other post's author has @mentioned or quoted you. X's pricing page lists no cheaper rate for a link in a reply to your own post, so plan on $0.200 for any post that carries one.
- Read only what you need. Reads are charged per resource returned: ask for fewer results per request and stop paging when you have enough.
- Read the same thing once a day. Deduplication means a second read of the same post in the same UTC day is normally free, so cache results instead of re-fetching them every hour across midnight.
- Use owned reads for your own account. Reading your own posts, mentions, followers or bookmarks through your own developer app costs $0.001 per resource instead of $0.005 or $0.010. X applies it only when the user ID matches the authenticated user and that user owns the app.
- Set a spending limit and watch the meter. A limit per billing cycle stops a runaway loop;
GET /2/usage/tweetsshows what you used each day.
Scheduling on X without your own API bill
If you only want to schedule and publish posts, you do not need an X developer account or credits. PostBoost publishes through its own X app and folds the cost into a flat plan. Each plan includes a monthly X allowance instead of a per-post charge, as the X policy explains. Every other network is unaffected.
Because X's cost depends on links and thread length, PostBoost counts X posts the same way X bills them:
- Each part of a thread counts as one X post, and a part that contains a link (including a bare domain) also counts as a link post. A thread on X of five parts is five posts.
- A post sent to two X accounts counts on both.
- The allowance resets on the 1st of each month (UTC). The PostBoost docs note that it is tracked and shown today, not yet enforced.
You can check it in three places:
- Dashboard: open the Tools menu and choose X usage under Insights. It shows two meters, X posts and X posts with a link, against the allowance, and a By account table for each X account that has published to X this month.
- API:
GET /{workspaceUuid}/usage/xreturnsperiod_startandperiod_end,postsandlink_posts(each withusedandlimit),enforced, andestimated_cost_usd, our estimate of what X charged for those posts (you are never billed per post).
curl https://postboost.co/app/api/YOUR_WORKSPACE_UUID/usage/x \
-H "Authorization: Bearer YOUR_API_TOKEN"
- MCP: an AI agent on the advanced
/mcp/postboostserver callsgetXUsage; on the connector,get-account-healthincludes this month's X usage. Ask it: "How many X posts and link posts have we used this month?"
The estimate uses the same $0.015 and $0.200 rates as the table above: a month of 42 X posts, 3 of them with a link, comes to 39 × $0.015 + 3 × $0.200 = $1.185.
Estimate a bill from code
The calculator is also a free API with no token, so a script or an agent can price a plan before you build it:
curl -X POST https://postboost.co/app/api/tools/x-api-cost-calculator \
-H "Content-Type: application/json" \
-d '{"posts": 1000, "link_share": 20, "post_reads": 50000}'
It returns line_items (one per billed resource, each with label, count, unit_usd and cost_usd), total_usd, link_premium_usd and prices_last_verified, the date the prices were last checked against X's page. The calculateXApiCost reference lists every field. The same tool is on the free tools MCP server, so an agent can answer "what would 500 X posts a month with links cost?" from the current table.
Where to go next
- Price your own month in the X API cost calculator, then check posts against X's 280-character count in the social media character counter.
- Turn an article into a thread with the X thread maker, or read how to turn a blog post into an X thread.
- See how PostBoost watches X usage, failed posts and expiring accounts on the reliable publishing feature page, or compare the API with MCP in social media API vs MCP.
Do this in PostBoost
Free tools for this guide
Free tool
X API cost calculator
Estimate your monthly X (Twitter) API bill from posts, link posts, replies and reads at X's pay-per-use prices, with the link-post premium shown.
Free tool
Social media character counter
Free character counter for X, Threads, Bluesky, Instagram, LinkedIn, TikTok and more. Counts as each network does, live in your browser.
Free tool
X thread maker: split long text into numbered posts
Split long text into numbered posts for X, Threads, Bluesky or Mastodon. Never cuts a word or a link. Free, no signup, runs in your browser.
FAQ
How much does the X API cost in 2026?
It is pay-per-use. Creating a post costs $0.015, a post that contains a URL $0.200, and a summoned reply $0.010. Reading a post costs $0.005, a user $0.010 and your own data $0.001. You buy credits up front and each request takes its price from them.
Is there still a free X API tier?
No. X's pricing page lists pay-per-use only, with no free tier. New paying users can get a one-time $20 credit after saving a card and buying credits, and X matches the first auto-recharge up to $50. Those credits expire three months after they are granted.
What happened to the $200 Basic and $5,000 Pro plans?
When X launched pay-per-use on 6 February 2026 it said Basic and Pro remain available and existing subscribers can opt in to pay-per-use. X's pricing page now lists only pay-per-use, with an Enterprise plan for volume above the 3 million post reads a month cap, so new developers start on pay-per-use.
Why does a post with a link cost so much more?
X prices a post that contains a URL at $0.200 against $0.015 for a plain post, about 13 times as much. X introduced the URL rate with its April 2026 pricing update and has not published a reason on its pricing page.
Does reading the same post twice cost twice?
Usually not. X deduplicates resources within a UTC day, so a post you already paid to read is not charged again until midnight UTC. X calls this a soft guarantee: outages can produce duplicate charges.
Do I need my own X API credits to schedule posts with PostBoost?
No. PostBoost publishes through its own X app, and your plan includes a monthly X allowance instead of a per-post bill. You can see how much of it you have used under X usage in the dashboard, through the API or through MCP.
Sources
- X developer docs: X API pay-per-usage pricing and credits
- X developer docs: changelog (pay-per-use launch, summoned replies, owned reads, free credits)
- Open Terms Archive: X replaces its $200 entry-level API plan with a pay-per-use model
- X developer docs: counting characters (links and t.co)
- PostBoost docs: X (Twitter) policy
- PostBoost API reference: getXUsage
- PostBoost API reference: calculateXApiCost