xtwitterapiprices 
ScrapeCreators
The friendliest terms on this list: prepaid credits that never expire, no subscription, no card to start, cached hits free, and a flat 1 credit for every X endpoint including the AI video transcript and the Communities pair - $1.88 per 1,000 calls at $47, $0.99 at $497. The catch is coverage: six X endpoints and no search, no followers and no replies, and User Tweets is capped by what X itself exposes - 'Twitter publicly returns only ~100 of the user's most popular tweets, not chronological or latest'.
Tweet search request, by volume
| Tweets per month | Monthly bill | Per 1,000 | Cheapest route | Allowance unused |
|---|---|---|---|---|
| 1k | not offered | - | - | - |
| 10k | not offered | - | - | - |
| 100k | not offered | - | - | - |
| 1M | not offered | - | - | - |
How ScrapeCreators compares
ScrapeCreators publishes no price at 10,000 tweets a month: not offered. The cheapest published route here costs $0.033 per 1,000.
| Provider | 1k a month | 10k a month | 100k a month | 1M a month |
|---|---|---|---|---|
A  AnyAPI | $0.033 | $0.033 | $0.032 | $0.032 |
T  TwitterAPIs | $0.040 | $0.040 | $0.040 | $0.040 |
G  GetXAPI | $0.050 | $0.050 | $0.050 | $0.050 |
| S ScrapeCreators | not offered | not offered | not offered | not offered |
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 |
|---|---|---|---|---|
| Free | $0 one-time, never expires | 100 | hard cap | One-off 100 credits, no credit card. Up to 7,000 further bonus credits are claimable. |
| Freelance | $47.00 one-time, never expires | 25,000 | hard cap | One-time $47 prepaid pack of 25,000 credits, printed on the pricing card as '$1.88 / 1k requests'. Not a subscription: 'pay as you go', credits never expire, no credit card required to start. |
| Business | $497 one-time, never expires | 500,000 | hard cap | One-time $497 prepaid pack of 500,000 credits, printed as '$0.99 / 1k requests'. |
| Enterprise | on request | - | not published | 'Custom volume, custom pricing, white-glove onboarding', 1M+ credits. No list price. |
'1 credit === 1 request (for most endpoints). A few use more, and the exact cost is shown in the docs.' All six X endpoints are one-credit: the documented example response on Profile, User Tweets, Tweet Details, Transcript, Community and Community Tweets each shows "credits_charged": 1, and no X endpoint costs more. A cached hit costs 0 credits: 'If we have a response in the cache that is this many days old or newer, return the cached response (0 credits ...). Otherwise, scrape a live result (1 credit).' There is no X search, followers or replies endpoint, so those three verticals are null. USD per credit comes from the prepaid packs in plans.
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://scrapecreators.com/ read 2026-09-08 / pricing section: Free $0 / 100 credits, Freelance $47 / 25,000 credits / '$1.88 / 1k requests', Business $497 / 500,000 credits / '$0.99 / 1k requests', Enterprise custom for 1M+ credits; '1 credit === 1 request (for most endpoints)'; 'Credits never expire'; 'No rate limits ... we recommend staying below 500 concurrent requests'; 'Cached results are free'; headline stats 98.2% success rate and 3.12s avg response over the last 30 days; 'Twitter 6 endpoints'; 'Built in Austin, TX'. https://scrapecreators.com/pricing 404s, the live table is the homepage #pricing anchor.
- https://scrapecreators.com/twitter-api read 2026-09-08 / the six X endpoints named and described: Profile, User Tweets, Tweet Details, Transcript, Community, Community Tweets. Also '100 credits on the house. No credit card.'
- https://docs.scrapecreators.com/llms.txt read 2026-09-08 / the Twitter API section lists exactly those six endpoints and no others
- https://docs.scrapecreators.com/v1/twitter/profile read 2026-09-08 / example response shows "credits_charged": 1, and the trim/cache parameter text prints the 0-credit cached hit and 1-credit live scrape. The same 1-credit example response appears on /v1/twitter/user-tweets, /v1/twitter/tweet, /v1/twitter/tweet/transcript, /v1/twitter/community and /v1/twitter/community/tweets.
Something out of date? Send the provider's own page to hello@xtwitterapiprices.com and it is corrected on the next capture.