X API Pay-Per-Use Pricing 2026
Pure consumption pricing for the X / Twitter API. $0.001 per call on GetXAPI (~20 tweets per call) vs $0.005 per resource on the official X API pay-per-use tier. No subscription, no monthly minimum, no surprise tier upgrade.
What “pay-per-use” actually means for the X API
Pay-per-use (also called consumption-based or usage-based pricing) means you are billed for each API call you make, instead of a flat monthly fee for a tier. The official X API moved to pay-per-use on February 9, 2026, retiring the old Basic / Pro / Enterprise tiers. GetXAPI has run on pay-per-use from day one.
Two things make pay-per-use cheap or expensive: the cost per call, and how much data each call returns. On the official X API, one resource = one tweet, so 1,000 tweets costs about $5. On GetXAPI, one call returns about 20 tweets, so 1,000 tweets costs $0.05. For the brand-level breakdown of every endpoint see the GetXAPI pricing page. For the head-to-head comparison against the official X API pay-per-use rates, see Twitter API pricing 2026.
Cost per call, every endpoint
Every endpoint, the cost per call, and the implied cost per 1,000 calls. Standard reads (tweets, users, lists) are $0.001 per call. DM endpoints and Create Tweet are $0.002. Article publishing is $0.005–$0.01.
Endpoint Price List
Showing 44 of 44 endpoints
| Endpoint | Price / Call | Price / 1,000 Calls |
|---|---|---|
tweet/advanced_search | $0.001 | $1.00 |
tweet/detail | $0.001 | $1.00 |
tweet/replies | $0.001 | $1.00 |
tweet/create | $0.002 | $2.00 |
tweet/favorite | $0.001 | $1.00 |
tweet/retweet | $0.001 | $1.00 |
tweet/bookmark | $0.001 | $1.00 |
tweet/unbookmark | $0.001 | $1.00 |
article/get | $0.001 | $1.00 |
article/create | $0.010 | $10.00 |
article/publish | $0.005 | $5.00 |
article/unpublish | $0.005 | $5.00 |
article/delete | $0.005 | $5.00 |
article/list | $0.005 | $5.00 |
article/update | $0.005 | $5.00 |
user/search | $0.001 | $1.00 |
user/info | $0.001 | $1.00 |
user/info_by_id | $0.001 | $1.00 |
user/user_about | $0.001 | $1.00 |
user/followers | $0.001 | $1.00 |
user/following | $0.001 | $1.00 |
user/followers_v2 | $0.001 | $1.00 |
user/following_v2 | $0.001 | $1.00 |
user/verified_followers | $0.001 | $1.00 |
user/media | $0.001 | $1.00 |
user/tweets | $0.001 | $1.00 |
user/tweets_and_replies | $0.001 | $1.00 |
user/likes | $0.001 | $1.00 |
user/home_timeline | $0.001 | $1.00 |
user/mentions | $0.001 | $1.00 |
user/bookmarks | $0.001 | $1.00 |
user/bookmark_search | $0.001 | $1.00 |
user/followers_you_know | $0.001 | $1.00 |
user/check_follow_relationship | $0.001 | $1.00 |
user/affiliates | $0.001 | $1.00 |
user/update_avatar | $0.001 | $1.00 |
user/update_banner | $0.001 | $1.00 |
user/update_profile | $0.001 | $1.00 |
list/members | $0.001 | $1.00 |
dm/list | $0.002 | $2.00 |
dm/send | $0.002 | $2.00 |
user_login | $0.001 | $1.00 |
account/me | Free | Free |
account/payments | Free | Free |
3 ROI scenarios: light, medium, heavy
Three real-world usage profiles, each modeled with monthly call volume, approximate tweets returned, and the pay-per-use bill on GetXAPI vs the official X API pay-per-use tier.
Light usage
Indie hacker, prototype, weekend project with small daily tweet pulls.
- Monthly calls: 5,000
- ~Tweets: 100,000
- GetXAPI: $5/mo
- Official X API: $25/mo
- Save $20/mo (80%)
Medium usage
Funded startup, growth dashboard, daily sentiment runs at moderate scale.
- Monthly calls: 50,000
- ~Tweets: 1,000,000
- GetXAPI: $50/mo
- Official X API: $250/mo
- Save $200/mo (80%)
Heavy usage
Production analytics platform, full firehose-style ingestion, multi-tenant.
- Monthly calls: 500,000
- ~Tweets: 10,000,000
- GetXAPI: $500/mo
- Official X API: $2,500/mo
- Save $2,000/mo (80%)
Scenario rates assume tweet/user/search reads at the official X API $0.005 per-resource rate. Run your exact bill in the cost calculator.
Official X API pay-per-use rates (Feb 2026 onwards)
Source: developer.x.com/#pricing. One resource on the official API = one tweet, one user, or one DM event.
| Resource | Official X API | GetXAPI Equivalent | Notes |
|---|---|---|---|
| Posts: Read (tweet search, lookup) | $0.005 | $0.001–$0.002 per call | 1 tweet returned per resource |
| User: Read (profiles, followers) | $0.010 | $0.001–$0.002 per call | 1 user returned per resource |
| DM Event: Read | $0.010 | $0.001–$0.002 per call | 1 DM event per resource |
| Content: Create (post tweet) | $0.010 | $0.001–$0.002 per call | 1 tweet write per resource |
| User Interaction: Create (like, retweet) | $0.015 | $0.001–$0.002 per call | 1 interaction per resource |
| DM Interaction: Create (send DM) | $0.015 | $0.001–$0.002 per call | 1 DM send per resource |
GetXAPI typically returns ~20 tweets per call, so the effective per-tweet cost is 100x cheaper than the official X API single-resource read. Last verified May 30, 2026.
Pay-per-use pricing FAQ
Pay-per-use means you pay only for each API request you make, with no monthly subscription, no minimum spend, and no fixed tier. The official X API moved to a consumption-based pay-per-use model on February 9, 2026. GetXAPI has used pay-per-use pricing from day one at $0.001 per call (~20 tweets per call).
Yes. For tweet search and tweet detail (the most common use case), GetXAPI is 5x cheaper per call ($0.001 vs $0.005) and 100x cheaper per tweet because each GetXAPI call returns ~20 tweets while the official resource returns 1 tweet. For user reads it's 10x cheaper per call, and for DM operations it's 5x to 7.5x cheaper.
Tweet search on GetXAPI uses the tweet/advanced_search endpoint at $0.001 per call, returning ~20 tweets per page. So 1,000 tweets of search results costs $0.05. The official X API charges $0.005 per single tweet returned via search, so 1,000 tweets costs $5, a 100x markup.
Yes. Use the cost calculator to plug in your tweet, user, and DM call volumes and see the side-by-side monthly bill for GetXAPI vs the official X API pay-per-use rates, with total savings percentage. For per-endpoint cost detail, see the pricing page.
The old X API tiers (Basic $200/mo, Pro $5,000/mo, Enterprise $42,000/mo) have been replaced by per-resource pay-per-use pricing: $0.005 to $0.015 per resource depending on whether it is a read, write, user, or DM. GetXAPI charges $0.001 per call and returns ~20 tweets per call, so the effective rate is $0.05 per 1,000 tweets vs $5 per 1,000 single-tweet reads on the official API.
No. There is no minimum monthly spend and no subscription. You buy credits starting at $10 (10,000 API calls / ~200,000 tweets) and they never expire. New accounts get $0.10 in free credits at signup with no credit card required.
Because pricing is per-call with no tier, a usage spike just consumes credits faster. There is no overage penalty, no rate ceiling beyond standard fair-use, and no surprise tier upgrade. You can also set spend alerts in the dashboard. For comparison, the official X API also has no monthly caps under pay-per-use, but each request costs 5x to 100x more.
Next read
Continue exploring related pages:
GetXAPI pricing
Brand pricing page with endpoint-level costs and quick totals.
Twitter API pricing and X API pricing comparison
Compare monthly economics and derived request-level cost.
GetXAPI vs TwexAPI comparison
Pay per call vs per endpoint subscription, 49 endpoints vs smaller catalog, 3 cost scenarios.
Twitter API cost calculator
Estimate monthly spend using your request volume.