Twitter (X) API Cost — A Straight Answer

Twitter (now X) API cost is one of the most confusing developer-pricing questions on the internet — and part of the confusion is that the pricing model itself has changed. The old ladder most articles still describe — a free tier, then fixed monthly plans — is gone: X used to sell fixed monthly tiers, and since 2026 it bills per resource read. What you get today is different, and usually more expensive than people expect. For comparison, TwitterAPI.io, a pay-per-use X (Twitter) API that needs no X developer account, charges $0.15 per 1,000 tweets returned.
This page lays out the real cost math for the official X API as it stands now: the pay-per-use rates every account gets, the monthly read cap, and Enterprise above it. Then it compares all of that against third-party APIs that resell the same public data per result. The short version: for read-heavy work below a few million tweets a month, third-party pricing runs about 33× cheaper per read.
Quick decision rule: if your project mostly reads public tweets, a third-party pay-per-result API will almost certainly be cheaper and simpler. If you need write access at volume, or metadata only the official API exposes, you are looking at official pricing. The full numbers — and where each path stops making sense — are below.
TwitterAPI.io is pay-per-result — about $0.15 per 1,000 tweets returned, with no subscription required and no monthly minimum. You pre-pay a credit balance and only spend on the calls you actually make
How X Changed Its API Pricing
The Twitter API most tutorials describe — a usable free tier and a ladder of fixed monthly plans — no longer matches what a developer can actually buy. X now bills per resource read with no subscriptions (docs.x.com, 2026), and what you get depends on your volume. Our Twitter API pricing guide lists the current official rates and what the old Basic and Pro plans cost.
Every developer lands on pay-per-use: you are billed for each post or user you read and each post you write, with no flat monthly tier to sit on. There is no free tier in the old sense — the only free usage is $20 of credits when you save a first eligible card, plus a match of your first auto-recharge up to $50.
Flat monthly plans are gone. If an article quotes a fixed monthly price for the Twitter API, it is describing a plan X no longer sells.
Above 3 million Post reads per monthly billing cycle, pay-per-use stops and X points you to Enterprise through an interest form, with no public price. So in practice a new project today chooses between metered pay-per-use, an Enterprise contract, or a third-party API — not the old three-rung ladder.
The Official X API: Pay-Per-Use Rates
Pay-per-use is the default for new developer accounts. You are billed per request rather than per month, which sounds flexible but adds up quickly because the per-unit prices are not small.
Reading posts — roughly $0.005 per post retrieved. A timeline pull, a search result, a single looked-up tweet: each post in the response is metered.
Writing posts — roughly $0.015 per standard post (text or media, no link). This rate stepped up from $0.010 — writes got more expensive, not less.
Posts containing a URL — roughly $0.20 per post. A link in the post moves it into a far higher pricing bracket. For anything that publishes links programmatically, this single line item dominates the bill.
Read ceiling — pay-per-use read volume is capped at 3 million post reads per monthly billing cycle. It is metered and bounded: past the cap you are pushed toward Enterprise.
What Pay-Per-Use Actually Costs at Volume
Run the read rate of ~$0.005 per post through realistic volumes and the picture is clear:
10,000 posts/month read → about $50/month.
100,000 posts/month read → about $500/month.
1,000,000 posts/month read → about $5,000/month, and it scales straight up with usage; there is no flat fee.
3,000,000 posts/month read → about $15,000/month, the pay-per-use ceiling; beyond it you need Enterprise.
Writes compound the bill independently. 50,000 standard posts a month at ~$0.015 is about $750; if those posts carry links, the same 50,000 at ~$0.20 each is $10,000. For a publishing or automation product, the write side — especially link posts — is often the larger number, and the one teams forget to model.
Why a Post With a Link Costs $0.20 on the X API
The X API cost per post depends on one thing: whether the post contains a URL. On X's pay-per-usage rate card, Post: Create is $0.015 per request and Post: Create (with URL) is $0.200 per request, about 13 times more. Both rates took effect on April 20, 2026, according to X's changelog and the X Developer Platform Team's forum announcement, which raised plain writes from $0.01 to $0.015 and priced posting a URL at $0.20 per post. The one exception is a summoned reply, which stays at $0.010.
What counts as a link post. X's rate card names the line Post: Create (with URL) and the announcement says "Posting a URL via X API will be priced at $0.20 per post". Neither page defines edge cases such as a link to another post or an attached image, so plan for any URL in the text to be billed at $0.20 until X documents otherwise. A summoned reply is one X allows because the original post's author @mentioned your account or quoted one of its posts (X changelog, February 23, 2026); those stay at $0.010 even with a link.
What link posts cost at volume. The table uses only the rates on docs.x.com/x-api/getting-started/pricing. The study-mix column applies the share of link posts we measured across 12 organization accounts (below). The last column is TwitterAPI.io's /twitter/create_tweet_v2, billed per call with no separate URL line.
How often real accounts post links. We pulled the recent timelines of 12 organization accounts and kept 526 original posts (reposts removed). 74% carried an external URL, and 8 of the 12 accounts put a link in most of their posts. News publishers sit at the top: @TechCrunch, @verge and @nytimes linked in 100% of sampled posts and @Reuters in 95%. Developer brands vary more: @vercel 81%, @github 71%, @stripe 28%, @OpenAIDevs 7%. At the pooled mix, publishing through the X API averages $0.1515 per post, or $151.46 per 1,000 posts against $15.00 if none of them had a link. For a link-heavy publisher the URL line is the bill.
Workarounds that do not save money. Moving the link into the first reply turns one post into two: the plain post at $0.015 plus a reply that still contains a URL. X's documentation does not list a reply to your own post as summoned, so budget it at $0.200, for $0.215 per link instead of $0.200. A URL shortener is still a URL. The only cheaper option on the rate card is dropping the link. The read side is not affected: reading a post that contains a link is $0.005 like any other post.
Owned Reads: $0.001 for your own data. The same April 20, 2026 update added Owned Reads at $0.001 per resource (1,000 resources for $1). The rate applies to 12 endpoints, including GET /2/users/{id}/tweets, /mentions, /liked_tweets, /bookmarks, /followers and /following, but only when {id} matches the authenticated user and that user owns the developer app. That is 5 times cheaper than the $0.005 post read and 10 times cheaper than the $0.010 user or follower read: pulling 10,000 of your own posts costs $10 instead of $50. Search, other people's timelines, and the same endpoints called for any other user stay at the standard rates.
Expansions are billed from November 22. On October 23, 2026 the X Developer Platform Team announced on the developer forum that, from November 22, objects returned through expansions (post, user, media, poll and place) will be billed at the standard pay-per-use rate for that resource, the same as direct lookups. Until then, expansion objects are not counted. Example: a recent search that returns 100 posts with expansions=author_id costs 100 x $0.005 = $0.50 in post reads today. From November 22, the includes.users block adds up to 100 user objects at $0.010, up to $1.00 more, so the same call can cost three times as much. In two 100-post Latest searches we ran, the results came from 94 and 97 distinct authors, so the author expansion would add $0.94 and $0.97. X deduplicates a resource billed earlier in the same UTC day, which helps only when the same authors keep coming back. The public rate card has no separate line for media, poll or place reads, so check the Developer Console for those.
The pay-per-result comparison. On TwitterAPI.io, tweet endpoints cost $0.15 per 1,000 tweets returned (15 credits per tweet, minimum 15 credits per request), and every tweet already embeds its author object, so there is no separate expansion charge. Posting runs through an authenticated session: one /twitter/user_login_v2 login ($0.10, with a proxy you supply) returns login_cookies, and each /twitter/create_tweet_v2 call is then $0.0006, link or not. The call acts as that account, so X can rate-limit, lock or suspend it; keep a human pace, expect the session to need a re-login now and then, and note that billing is per HTTP 200 call.
How we collected this. Question: how often do link-publishing organization accounts put an external URL in a post, and how many distinct authors does a 100-post search return? Accounts: @nytimes, @Reuters, @verge, @TechCrunch, @github, @vercel, @NASA, @OpenAIDevs, @XDevelopers, @stripe, @Cloudflare and @ProductHunt, about 60 recent posts each via /twitter/user/last_tweets, plus two /twitter/tweet/advanced_search Latest queries of 100 posts each. Collected in 2026: 46 requests, 920 tweets, about $0.14. A post counts as a link post when it has an external URL; links to other posts and attached media are not counted. The sample cannot show how X classifies edge cases, small accounts' habits, or how many authors repeat over a full day. Privacy: aggregates only; search authors are counted, never named or stored.

Enterprise Pricing
Above 3 million Post reads per monthly billing cycle, the official route is Enterprise — a quote-based, usage-negotiated contract.
X publishes no Enterprise price: you apply through an interest form, and the contract is negotiated on volume and data scope. It buys read volume above the pay-per-use cap, higher and customizable rate limits, and dedicated support. Full-archive search does not need it: docs.x.com lists that endpoint as available to pay-per-use and Enterprise customers. For what the contract includes feature by feature, where the 3 million cap sits in dollars, and the package prices reported in 2023, see our Twitter Enterprise API guide.
It is built for large platforms, ad-tech companies, and well-funded research consortia — organizations for whom social data is core infrastructure with a budget line to match. For a startup, an indie developer, a single research project, or a small marketing team, Enterprise is not a realistic line item.
Third-Party Pay-Per-Result APIs
Third-party APIs aggregate the same publicly available Twitter/X data and resell it with per-result billing. They are the reason a small project can still afford Twitter data at all. If you are on the other side and pricing your own API, our guide to API monetization models and per-result metering shows what per-call versus per-result billing does to a real bill.
Per-tweet rate — on TwitterAPI.io, $0.15 per 1,000 tweets retrieved (about $0.00015 a tweet, with a $0.00015 minimum per request) for search, advanced search, timelines, replies and retweeters; profile lookups run about $0.18 per 1,000. Follower and following data is typically cheaper still, scaling down toward roughly $0.0045–$0.01 per 1,000 records on higher-volume calls.
No subscription required, no monthly minimum. You pre-pay a credit balance and draw it down as you make calls. A month where you pull nothing costs nothing — there is no tier to keep paying for.
No monthly read ceiling. There's no monthly quota to upgrade past; throughput is a per-second limit instead (20 requests/s once you've paid, 50 on Scale, 500 on Business), with HTTP 429 if you exceed it (no Retry-After header, so back off about a second and retry).
The trade-off: third-party APIs serve public data and standard tweet/user objects. If you need to publish at scale, or need official-only signals, the official API still has a role — covered below.
Cost at Common Volumes — Side by Side
Read-only operations, approximate monthly cost in USD. The official column is pay-per-use (the model a new account actually gets); the third-party column is pay-per-result at ~$0.15 per 1,000 tweets.
1,000 reads — official ≈ $5 · third-party ≈ $0.15.
10,000 reads — official ≈ $50 · third-party ≈ $1.50.
100,000 reads — official ≈ $500 · third-party ≈ $15.
1,000,000 reads — official ≈ $5,000 · third-party ≈ $150.
3,000,000 reads — official ≈ $15,000 (the pay-per-use cap) · third-party ≈ $450.
The ratio holds steady — about 33× ($0.005 / $0.00015) — across the whole range, because both models now scale with usage; the official API simply meters each post far higher. The gap only closes if you genuinely need Enterprise-class scale and the official-only capabilities that come with it.

Hidden Costs You'll Hit With the Official API
The headline rate is not the whole bill. Four things routinely surprise teams:
The URL-post surcharge. A post containing a link is billed at roughly $0.20 versus ~$0.015 for a plain post — more than a 13× jump. Any workflow that auto-posts links needs to model this line on its own; it is frequently the single largest cost.
Retries count. A network blip, your client retries, and both attempts meter. Without idempotency and careful retry logic you pay for failures.
Endpoint gating. Full-archive search, the filtered stream, and some advanced filters are not available on every plan. Paying the pay-per-use rate does not automatically unlock every endpoint — capability and price are separate questions.
Commitment above the cap. Past 3 million Post reads per monthly billing cycle you move to a negotiated Enterprise contract, committing spend before you know your real usage curve. Pay-per-result third-party billing carries none of that lock-in.
When the Official API Is Worth the Cost
Paying X directly still makes sense in specific situations:
Heavy write operations. Posting, replying, liking, following and DMs at volume are first-class on the official API. If publishing is your product, the official write side is the first-party route — just model the URL-post rate carefully.
Official-only metadata. If your product depends on signals the official user and tweet objects expose authoritatively, the official API is the source of record.
Compliance posture. Agencies running paid ads, or partners building official integrations, may need the official API for terms-of-service reasons that simply do not apply to read-only public-data use cases.
For everything else — research datasets, social listening, dashboards, monitoring, analytics — a third-party pay-per-result API delivers the same public data at a fraction of the metered official price.
def estimate_monthly_cost(reads, plain_writes=0, link_writes=0):
"""Rough monthly cost: official X API pay-per-use vs a third-party API."""
# Official X API pay-per-use (approximate published rates)
official = reads * 0.005 + plain_writes * 0.015 + link_writes * 0.20
# Third-party pay-per-result (~$0.15 per 1,000 tweets returned)
third_party = reads * 0.00015
print(f"{reads:,} reads + {plain_writes:,} posts + {link_writes:,} link-posts / month")
print(f" Official X API (pay-per-use): ${official:,.2f}")
print(f" Third-party (reads only): ${third_party:,.2f}")
if reads:
print(f" Read-cost ratio: {official / max(third_party, 1e-9):,.0f}x")
# Example: a brand-monitoring project — 100k reads, no posting
estimate_monthly_cost(reads=100_000)
# Example: a publishing tool that posts links
estimate_monthly_cost(reads=5_000, plain_writes=0, link_writes=20_000)
Researching this?Free starter credits cover end-to-end testing — Google sign-in, no card. Get a key.
Questions readers ask
How much does the Twitter API cost?
For a new developer account the official X API is pay-per-use: roughly $0.005 per post read, $0.015 per standard post written, and about $0.20 per post containing a link, with pay-per-use capped at 3 million post reads per monthly billing cycle. Above that you need an Enterprise contract, requested through an interest form with no public price. Third-party APIs resell the same public data at about $0.15 per 1,000 tweets with no monthly minimum.
Is there still a free Twitter API tier?
Not in the old sense. Developer accounts are metered pay-per-use rather than given a free monthly allowance; the only free usage is $20 of credits when you save a first card, plus a match of your first auto-recharge up to $50. Third-party APIs are also paid, but they bill per result with no subscription required — you can start with a small pre-paid balance and only spend what you use.
Why does a post with a link cost $0.20 on the X API?
X's pay-per-usage rate card prices Post: Create (with URL) at $0.200 per request against $0.015 for a post without a URL. The change took effect on April 20, 2026, per X's changelog and developer forum, along with the step-up of plain writes from $0.01 to $0.015. Summoned replies (replies to a post whose author @mentioned or quoted your account) stay at $0.010. Putting the link in a reply does not help, because the reply is itself a post with a URL.
What are Owned Reads on the X API, and do expansions cost extra?
Owned Reads cost $0.001 per resource when your own developer app reads your own data through 12 endpoints such as GET /2/users/{id}/tweets, /bookmarks and /followers, with {id} matching the authenticated user who owns the app. Expansions are free today, but from November 22 X bills objects returned through expansions (post, user, media, poll, place) at the standard rate, so a 100-post search with the author expansion can add up to $1.00 in user reads.
Can I still get a flat monthly Basic plan?
No. X no longer sells fixed monthly plans: the official API is pay-per-use with no subscriptions ($0.005 per post read, $0.010 per user read), capped at 3 million Post reads per monthly billing cycle, with Enterprise above that. A new project today chooses between official pay-per-use, an Enterprise contract, or a third-party API — not the old Basic/Pro ladder.
How can I access Twitter data at low cost?
For read-heavy work — research, monitoring, analytics, dashboards — third-party pay-per-result APIs are dramatically cheaper than the official metered rates. A 100,000-tweet month costs roughly $15 on a third-party API versus about $500 on the official pay-per-use model, a gap of about 33x that holds across volumes.
Why is the Twitter API so expensive?
The official pricing reflects positioning more than delivery cost. Metered per-post rates and a hard cap on pay-per-use volume keep casual and small-scale use off the platform and concentrate access among large, well-funded organizations. Third-party APIs exist precisely because that pricing left a gap for everyone who only needs public data.
How much does it cost to post links via the Twitter API?
Posting a tweet that contains a URL is billed at a much higher rate than a plain post — on the order of $0.20 per link post versus about $0.015 for one without a link. Any tool that publishes links programmatically should model this line separately; at volume it is often the single largest cost on the bill.
How much does the official X API Enterprise tier cost?
X publishes no Enterprise price: you request it through an interest form, and the contract is negotiated on usage and data scope. It is the route for more than 3 million Post reads per monthly billing cycle. It is intended for large platforms, ad-tech firms, and major research programmes — not for startups, indie developers, or single projects.
Do third-party Twitter APIs have monthly fees?
Typically no. A pay-per-result provider like TwitterAPI.io requires no subscription and has no monthly minimum — you pre-pay a credit balance and draw it down per request. A month with no calls costs nothing, which is the opposite of a fixed-tier plan you pay for whether or not you use it.
What does it cost to pull 1 million tweets a month?
On the official pay-per-use model, 1,000,000 reads at roughly $0.005 each is about $5,000/month. On a third-party pay-per-result API at about $0.15 per 1,000 tweets, the same volume is roughly $150/month. The official route only becomes competitive at genuinely large scale, where you would also need its Enterprise-class capabilities.
Is using a third-party Twitter API allowed?
Third-party APIs serve publicly available Twitter/X data. They are widely used for research, social listening, and analytics. If your use case specifically requires official partner status — for example running paid ads or an official integration — you will need the official API for those compliance reasons; for read-only public-data work, a third-party API is the standard, cost-effective choice.
Continue
- X API pay-per-usage pricing and credits (docs.x.com)
- X Developer Platform changelog
- X API Pricing Update: Owned Reads $0.001 + other changes, effective April 20, 2026 (X Developer Community)
- [Inform] X API PPU - Expansions Update (X Developer Community)
- TwitterAPI.io API documentation
- /
- /pricing
- 'Rate Limit Exceeded' on the Twitter (X) API
- /blog/twitter-api-pricing-2025
- /is-twitter-api-free
- /twitter-scraper
- /blog/twitter-api-python-complete-guide
- X API cost breakdown by endpoint
- X API news and pricing changes
- the X Developer Portal and Console
- auto-posting to Twitter (X)
- API monetization models and per-result metering
- /blog/twitter-enterprise-api
- 01How to Log Out of Twitter (X) on Web, iPhone and Android
- 02How to Change Your Twitter (X) Username, Step by Step
- 03Twitter (X) API timeline: get a user's tweets, page by page
- 04Twitter (X) User API: Get Profiles and Understand Every Field of the User Object
- 05Twitter (X) Feed API: How to Build Your Own Feed in 2026
- 06How Much Does the X (Twitter) API Cost in 2026?
- 07Brand24 vs Mention — the X (Twitter) Data Cost Perspective
- 08Twitter (X) API 1.1 in 2026: What Still Works and Where Each Endpoint Went
Writing about something you built with TwitterAPI.io? Our community rewards program pays API credits for honest tutorials, build logs and videos.
Stop reading. Start building.
Starter credits cover real testing on real data. Google sign-in, no card, no application queue.
Get an API keyAlready building with TwitterAPI.io? Publish an honest tutorial or build log about it and earn up to $200 a month in API credits.