Twitter & X API Pricing 2026: Pay Per Use, Tiers & Costs
Both GetXAPI and the official X API use pay-per-use pricing, but the units differ. GetXAPI costs $0.05 per 1,000 tweets ($0.001 per call, ~20 tweets per call). The official X API bills reads per returned resource, $0.005-$0.010 each, or $5-$10 per 1,000 tweets. On single-resource operations that is 5x-15x cheaper; on multi-result reads like search, where every returned Post bills separately, it is about 100x per tweet. The full per-endpoint breakdown is below.
X pricing facts verified August 16, 2026 against X's API documentation on that date.
How much does the Twitter API cost?
The official X API is billed per use, with reads and writes priced separately; its current public pricing page does not list a general Free tier. GetXAPI prices per call instead of per seat, which changes the unit economics: you pay for the requests you make rather than a monthly floor you may never consume.
X's pricing table is the source for the official access options and rates.
GetXAPI
$0.001, $0.002
Per call, pay as you go
- Standard endpoints: $0.001 / call (~20 tweets)
- DM endpoints: $0.002 / call
- $0.05 per 1,000 tweets fetched
- $0.10 free credits, no card required
Official X API (Pay-Per-Use)
$0.005, $0.20
Per resource, pay as you go
- Posts: Read: $0.005 / resource
- User: Read: $0.010 / resource
- DM Event: Read: $0.010 / resource
- Content: Create: $0.015 / resource
- Content: Create (with URL): $0.200 / resource
- DM Interaction: Create: $0.015 / resource
- User Interaction: Create: $0.015 / resource
Current official pricing model
The current official X API pricing page lists prepaid pay-per-use access for standard usage and custom-priced Enterprise access. Standard pay-per-use access has a 3 million Post-read monthly cap. docs.x.com/x-api/getting-started/pricing. GetXAPI remains 5x-15x cheaper on single-resource operations and writes, and about 100x cheaper per tweet on multi-result reads, where the official API bills every returned Post as a separate resource while a GetXAPI call is a flat $0.001.
Current official X API pricing facts
Verified against X's public pricing table on August 16, 2026. The table does not publish an effective date for these prices.
- Billing: standard access uses prepaid credits. Reads are billed per resource returned and writes are billed per request.
- Core prices: a Post read is $0.005, a User or follower read is $0.010, standard Post create is $0.015, and Post create with a URL is $0.20.
- Limits and access: standard pay-per-use access has a 3 million monthly Post-read cap. Enterprise pricing is custom, and the public table does not list a general Free tier.
The URL-post tax
A standard post costs $0.015. A post with any link costs $0.20. Auto-publishing newsletter, blog, or affiliate URLs at volume multiplies your write bill fast.
Owned reads
Owned reads cost $0.001 per resource, but only when the authenticated user ID matches the app owner's user ID. It is not a discount for client or managed accounts.
24-hour deduplication
Requesting the same post or user twice within one UTC day is charged once. The window resets at midnight UTC. Per-resource billing still applies, so a call returning 100 posts is 100 reads.
Official X API Access and Pricing (2026)
The current public documentation lists pay-per-use and Enterprise. It does not list general Free, Basic, or Pro plans, and it does not document account-specific legacy access.
| Tier | Monthly cost | Included / limits | GetXAPI equivalent |
|---|---|---|---|
| Public Free tier | Not listed | No general Free-tier allowance appears in the current public pricing table | $0.10 free credits (~2,000 tweets), no card |
| Pay-per-use (Reads) | From $0.005/resource | $0.005 post read, $0.010 user read; ~$5-$10 per 1,000 tweets | $0.001/call (~20 tweets) = $0.05 / 1,000 tweets |
| Pay-per-use (Writes) | Standard Post: $0.015/request | $0.015 per post, $0.20 per post with a URL; 3M post-read monthly hard cap | $0.001-$0.002/call, no monthly cap |
| Enterprise | Custom quote | Custom contract; the standard 3M monthly Post-read cap does not apply | Same pay-per-call rate at any volume, no contract |
Is there a free X API tier in 2026? The current public pricing page does not list one. GetXAPI gives every new account $0.10 in signup credits, about 100 standard calls or 2,000 tweets, with no credit card required at signup.
Historical tier claims need historical sources
Current X documentation does not provide a complete, dated history of Basic, Pro, or Free access, and it does not state the status of every legacy subscriber. We therefore do not use old tier prices or unsourced cutover dates as current purchasing guidance. What we can source, we publish as history rather than as pricing: the retired tiers, as they actually appeared on X's own page.
If your account has legacy access, use the Developer Console or X support for the limits and billing terms that apply to that account.
X API retired subscription tiers
History, not current pricing. None of these tiers can be bought today; X now sells prepaid pay-per-use access.
Across the official captures reviewed here, Enterprise had no numeric price: each one shows Monthly subscription tiers next to an Apply link. We found no official source for the widely quoted $42,000 per month figure. By the November 11, 2024 capture, Basic was $200 per month. Every table below is transcribed from the single capture named above it, checked on 2026-08-20.
2023-08-04: Four tiers: Free, Basic $100, Pro $5,000, Enterprise on application
Transcribed from the 2023-08-04 capture. These prices were also confirmed on 2023-07-05 and 2023-09-02, though the limits on those dates were not transcribed.
| Tier | Monthly | Limits as published |
|---|---|---|
| Free | Free | Write-only. 1,500 posts per month at the app level. 1 app ID. |
| Basic | $100 | 3,000 posts per month per user, 50,000 per app, 10,000 posts per month read cap. 2 app IDs. |
| Pro | $5,000 | 1,000,000 posts per month GET at the app level, 300,000 posting. Search and filtered stream. 3 app IDs. |
| Enterprise | No price published | The page read "Monthly subscription tiers" next to an Apply now link. |
The earliest full table we transcribed. Pro carried no user-level posting limit yet, and Free was capped at the app level only.
2024-10-29: Same prices, changed limits
Transcribed from the 2024-10-29 capture. These prices were also confirmed on 2024-08-20, though the limits on those dates were not transcribed.
| Tier | Monthly | Limits as published |
|---|---|---|
| Free | Free | Write-only. 1,500 posts per month at the user level and 1,500 at the app level. 1 app ID. |
| Basic | $100 | 3,000 posts per month per user, 50,000 per app, 10,000 posts per month read limit. 2 app IDs. |
| Pro | $5,000 | 288,000 posts per month per user posting, 300,000 per app, 1,000,000 posts per month read limit. 3 app IDs. |
| Enterprise | No price published | Unchanged from the 2023 page, Apply now link only. |
Prices identical to 2023, but the limits had already moved: Free gained a user-level cap and Pro gained a 288,000 user-level posting limit. This is the capture that proves limits and prices changed at different times.
2024-11-11: Basic doubled to $200, Free cut, annual options added
Transcribed from the 2024-11-11 capture.
| Tier | Monthly | Limits as published |
|---|---|---|
| Free | Free | 500 posts per month at both user and app level, 100 reads per month. 1 app ID. |
| Basic | $200$175 on annual ($2,100/yr) | 3,000 posts per month per user, 50,000 per app, 10,000 posts per month read limit. 2 app IDs. 2 top-ups allowed. |
| Pro | $5,000$4,500 on annual ($54,000/yr) | 288,000 posts per month per user posting, 300,000 per app, 1,000,000 reads per month. 3 app IDs. 2 top-ups allowed. |
| Enterprise | No price published | Unchanged, Apply now link only. |
Basic went from $100 to $200 between the 2024-10-29 and 2024-11-11 captures, so the repricing is datable to that window and no more precisely. X's page printed the Pro annual rate as "$4.500"; the $54,000 annual total confirms the intended figure was $4,500.
We do not state when these tiers started or ended. A capture proves the table was live that day; it does not prove when X began or stopped charging that way, and X published no dated announcement we have been able to read. Anyone giving you exact cutover dates for this period should be able to show you the source.
Per-Endpoint Cost Comparison
Units matter: GetXAPI bills per call, while the official X API bills reads per returned resource and writes per request. Rows marked with a per-20-results figure are paginated reads where one official request bills every result it returns.
| GetXAPI Endpoint | Type | GetXAPI (per call) | Official X (per unit) | Comparison |
|---|---|---|---|---|
tweet/advanced_search | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
tweet/detail | read | $0.001 | $0.005 per Post resource | 5x cheaper per operation |
tweet/replies | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
article/get | read | $0.001 | $0.005 per Note resource | 5x cheaper per operation |
tweet/create | write | $0.002 | $0.015 per request | 7.5x cheaper per operation |
tweet/favorite | write | $0.001 | $0.015 per request | 15x cheaper per operation |
tweet/retweet | write | $0.001 | $0.015 per request | 15x cheaper per operation |
user/search | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
user/info | read | $0.001 | $0.010 per User resource | 10x cheaper per operation |
user/info_by_id | read | $0.001 | $0.010 per User resource | 10x cheaper per operation |
user/user_about | read | $0.001 | $0.010 per User resource | 10x cheaper per operation |
user/followers | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
user/following | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
user/verified_followers | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
user/media | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/tweets | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/tweets_and_replies | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/likes | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/home_timeline | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/bookmark_search | read | $0.001 | $0.005 per Post resource | ~$0.10 per 20-result call vs $0.001 |
user/followers_you_know | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
user/check_follow_relationship | read | $0.001 | $0.010 per User resource | 10x cheaper per operation |
list/members | read | $0.001 | $0.010 per User resource | ~$0.20 per 20-result call vs $0.001 |
dm/list | read | $0.002 | $0.010 per DM event | ~$0.20 per 20-result call vs $0.002 |
dm/send | write | $0.002 | $0.015 per request | 7.5x cheaper per operation |
What Does a Real Workload Cost?
This page keeps the current prices; the arithmetic lives elsewhere. For per-1,000-tweet math, 10K to 1M read workloads, mixed read/write/DM examples, and reusable budgeting formulas, see the Twitter API workload cost examples. For an interactive estimate at your own volumes, use the cost calculator.
Sources
Official X API pay-per-use pricing from docs.x.com/x-api/getting-started/pricing. GetXAPI pricing from getxapi.com/pricing.
Pricing values last verified on August 16, 2026. X's page metadata was last modified on August 13, 2026, but that metadata is not a pricing effective date.
Pricing alone does not capture the full cost of a Twitter API integration. For the per-endpoint quotas and 429-handling patterns, see the Twitter API rate limits comparison. For a worked monthly bill at your projected volume, plug numbers into the cost calculator.
Pricing this page covers reads, writes, and DMs at $0.001-$0.002 per call. The same rate powers the data products built on it: the Twitter scraper API for tweets and profiles, the Twitter search API for keyword and operator queries, and the Twitter followers API for follower and following exports, all at $0.05 per 1,000.
What Will You Actually Pay?
Plug in your monthly read, write, and DM volumes, see the real bill against the official X API and GetXAPI side by side.
Frequently Asked Questions
The official X API uses prepaid pay-per-use pricing. Standard post reads cost $0.005 per resource, user and follower reads cost $0.010, standard post creation costs $0.015 per request, and a post containing a URL costs $0.20. GetXAPI charges $0.001 per call for standard endpoints and $0.002 for DM endpoints. One standard GetXAPI call returns about 20 tweets, or about $0.05 per 1,000 tweets.
No subscription is required. GetXAPI's primary model is pay-per-call with no minimum spend and no commitment, and you get $0.10 in free credits at signup and only pay for what you use. Optional subscription plans, a fixed monthly call quota at a lower effective rate, are also available if you prefer.
The current public X pricing documentation lists prepaid pay-per-use access and custom-priced Enterprise access. It does not list public Free, Basic, or Pro plans. Standard pay-per-use access has a 3 million Post-read monthly cap; Enterprise is the custom option for workloads that need different limits. GetXAPI charges $0.001 per standard call with no mandatory subscription.
The current official table lists a standard text or media post at $0.015 per request and a post containing a URL at $0.20, roughly 13 times more. X does not provide a dated effective date in that table. If you auto-publish links at volume, model this line item separately because it can dominate the write bill.
The units differ: GetXAPI bills per call, the official X API bills reads per returned resource. On single-resource operations (one profile lookup, one tweet) GetXAPI is 5x-10x cheaper: $0.001 per call versus $0.005-$0.010 per resource. On multi-result reads the gap is about 100x, because a 20-result official search request bills 20 Post resources (about $0.10) while the same GetXAPI call costs $0.001. For worked monthly examples at 10K to 1M volumes, see the Twitter API workload cost examples.
Among the providers in our comparison, GetXAPI has the lowest published standard-read price at $0.001 per call (~20 tweets per call), about $0.05 per 1,000 tweets. The official X API starts at $0.005 per single resource, which works out to roughly 100x more per tweet on multi-result reads.
The current public X pricing page does not list a general Free tier. It lists prepaid pay-per-use access and Enterprise access. GetXAPI gives every new account $0.10 in signup credits, about 100 standard calls or 2,000 tweets, with no credit card required at signup.
X's current public pricing documentation does not list Basic or Pro. It lists prepaid pay-per-use access and custom-priced Enterprise access, but it does not establish a dated migration history or say what happens to every legacy subscriber. If your account previously used a fixed tier, check the Developer Console or contact X support for account-specific status.
Next read
Continue exploring related pages:
GetXAPI pricing
Brand pricing page with endpoint-level costs and quick totals.
Twitter API cost calculator
Estimate monthly spend using your request volume.
Twitter scraper API
Scrape tweets, profiles, and followers via a managed API at $0.05 per 1,000, no developer account.
GetXAPI vs TwexAPI comparison
Pay per call vs per endpoint subscription, 72 endpoints vs smaller catalog, 3 cost scenarios.