xtwitterapiprices 
ScrapeBadger
The widest X surface here - 46 documented endpoints covering search, timelines, followers, replies, lists, communities, spaces and trends, plus a real-time stream product with WebSocket and signed webhook delivery - and the only one with a no-commitment wallet, $10 minimum at $0.15 per 1,000 credits, credits that never expire. The catch is the billing shape: X is charged 1 base credit plus 1 credit per item returned, so a search page of 20 tweets is 21 credits, roughly 21x a single-object lookup, and the per-1K credit rate on the plan table is not a per-call rate. Nothing on the site names an operating company or country, and the plan table is client-rendered, so the prices above had to be read in a browser rather than from the served HTML.
Tweet search request, by volume
| Tweets per month | Monthly bill | Per 1,000 | Cheapest route | Allowance unused |
|---|---|---|---|---|
| 1k | $0.150 | $0.150 | pay as you go | - |
| 10k | $1.50 | $0.150 | pay as you go | - |
| 100k | $15.00 | $0.150 | pay as you go | - |
| 1M | $129 | $0.129 | Growth | 800,000 units |
How ScrapeBadger compares
At 10,000 tweets a month ScrapeBadger costs $0.150 per 1,000, 4.6x the cheapest published route and 4.6x AnyAPI.
| Provider | 1k a month | 10k a month | 100k a month | 1M a month |
|---|---|---|---|---|
A  AnyAPI | $0.033 | $0.033 | $0.032 | $0.032 |
| S ScrapeBadger | $0.150 | $0.150 | $0.150 | $0.129 |
A  Apify X Tweet Scraper (xquik) | $0.150 | $0.150 | $0.150 | $0.150 |
T  twitterapi.io | $0.150 | $0.150 | $0.150 | $0.150 |
List prices, dollars per 1,000 tweets at the cheapest published route to each volume. How this is worked out
Every published plan
| Plan | Price | Included credits | Overage each | Note |
|---|---|---|---|---|
| PAYG | $0 per month | 0 | $0.0001 | "Pay As You Go is a prepaid wallet: you top up from $10 at $0.15 per 1,000 credits and use them at your own pace (they do not expire)." The plan table prints $0.150 per 1K credits and a 60 req/min rate limit; the credit-value table prints "$10 pack, ~67K requests". |
| Starter | $49.00 per month | 600,000 | hard cap | 600,000 credits a month at $0.082 per 1K, "46% cheaper than PAYG", 300 req/min. On the annual toggle the same plan prints $41/mo at $0.068 per 1K. |
| Growth | $129 per month | 1,800,000 | hard cap | Marked "Most popular". 1,800,000 credits a month at $0.072 per 1K, "52% cheaper than PAYG", 300 req/min. Annual: $108/mo at $0.060 per 1K. |
| Pro | $299 per month | 5,000,000 | hard cap | 5,000,000 credits a month at $0.060 per 1K, "60% cheaper than PAYG", 10K req/min, ENTERPRISE rate tier. Annual: $249/mo at $0.050 per 1K. |
| Scale | $699 per month | 13,000,000 | hard cap | 13,000,000 credits a month at $0.054 per 1K, "64% cheaper than PAYG", 10K req/min. Annual: $583/mo at $0.045 per 1K. |
| Enterprise | on request | - | not published | "Need more volume? Custom credit packages, negotiated pricing, SLA guarantee, and a dedicated account manager - Talk to Sales." The FAQ says to email support when 13M credits a month is not enough. No public price. |
The docs state one rule for every X endpoint: "Each request costs 1 base credit plus 1 credit for every item (tweet, user, etc.) in the response - so a request that returns N items costs N + 1 credits", with the worked example that an advanced_search call returning 20 tweets costs 21 credits. The credit table on the docs page applies that same rule to all seven X categories (Tweets 11 endpoints, Users 11, Lists 3, Communities 3, Trends 2, Geo 2, Spaces 2), and the pricing page's per-API list prints "Twitter Scraper API - 1 credit base, +1 per item". So units is 1 per returned item for all six verticals, with a further 1 base credit on top of each request; that base credit is in credits, not dollars, so minPerRequestUsd stays null. A single-object lookup such as a profile or one tweet therefore costs 2 credits in total. No page size is printed for any X endpoint, so resultsPerRequest is null. Failed requests (4xx/5xx, blocks, timeouts, empty responses) cost 0 credits.
Cost by endpoint
Per 1,000, at 10,000 tweets a month.
What it can do
Only what the provider's own pages state.
Where these numbers came from
- https://scrapebadger.com/pricing read 2026-09-08 / read in the Aside browser because the plan table is client-rendered and absent from the served HTML. Monthly toggle: PAYG from $10 at $0.150/1K, Starter $49/600K, Growth $129/1.8M, Pro $299/5M, Scale $699/13M with per-1K rates $0.082/$0.072/$0.060/$0.054 and rate limits 60/300/300/10K/10K req per minute. Annual toggle ("Get 2 FREE months!"): $41/$108/$249/$583 a month at $0.068/$0.060/$0.050/$0.045 per 1K. Also the per-API credit list including "Twitter Scraper API - 1 credit base, +1 per item", the 1,000 free credits with no card, and the FAQ on expiry, unbilled failures and the PAYG wallet
- https://docs.scrapebadger.com/credits-and-pricing read 2026-09-08 / "Twitter/X is billed per item. Each request costs 1 base credit plus 1 credit for every item in the response - so a request that returns N items costs N + 1 credits", the advanced_search 20-tweets-equals-21-credits example, the X-Credits-Used header, the seven X endpoint categories, and "credits never expire"
- https://docs.scrapebadger.com/openapi-twitter.json read 2026-09-08 / 46 X paths, confirming all six verticals exist: tweets/advanced_search, users/{username}/latest_tweets, users/{username}/by_username, tweets/tweet/{tweet_id}, users/{username}/followers, tweets/tweet/{tweet_id}/replies, plus batch user lookups and the stream monitors and filter rules
- https://scrapebadger.com/legal/terms read 2026-09-08 / checked for an operating entity; the terms name only "the laws of the European Union" and no company or country, so hq is unknown
Something out of date? Send the provider's own page to hello@xtwitterapiprices.com and it is corrected on the next capture.