xtwitterapiprices JSON
All providers
S

SocialCrawl

The flattest X price sheet of the five: every X endpoint a buyer normally wants - search, user timeline, profile, single tweet, followers and replies - is 1 credit per request, with only AI search (5), the composite profile call (5) and video transcripts (10) costing more, and empty pages and cache hits refunded. The catch is that it sells in GBP one-time packs (GBP 15 / 2,500, GBP 49 / 20,000, GBP 299 / 150,000) with no printed USD rate at all, so every monthlyUsd here is null by the schema's currency rule and a USD buyer is exposed to the exchange rate; list endpoints also bill per page, so a deep follower crawl is many credits, not one.

Cheapest way in
on request
Free tier
100 calls
Unused credits
roll over
Credits per request
1 credit per request

Tweet search request, by volume

Tweets per month Monthly bill Per 1,000 Cheapest route Allowance unused
1k price on request - - -
10k price on request - - -
100k price on request - - -
1M price on request - - -

How SocialCrawl compares

SocialCrawl publishes no price at 10,000 tweets a month: price on request. The cheapest published route here costs $0.033 per 1,000.

Provider 1k a month10k a month100k a month1M 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 SocialCrawl price on request price on request price on request price on request

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 "Try every endpoint, free - 100 credits (one-time), $0." No credit card. Community support.
Starter on request 2,500 hard cap Priced in GBP only: 2,500 credits for GBP 15, a one-time pack, not a subscription. monthlyUsd is null because the schema is USD and SocialCrawl prints no USD figure.
Growth on request 20,000 hard cap Marked "Most popular". GBP 49 for 20,000 credits; the card shows 8,000 struck through and 20,000 as the current amount, and claims "60% cheaper per credit". The pack sizer on the same page quotes this pack as GBP 0.0074 per call.
Pro on request 150,000 hard cap GBP 299 for 150,000 credits; the card shows 50,000 struck through and 150,000 as the current amount, and claims "67% cheaper per credit".
Enterprise on request - not published "Custom - Contact us" for dedicated support, SLAs and volume pricing. No public price.

The endpoint list at /llms-twitter.txt prints a credit cost beside each of the 15 X endpoints. All six verticals here are standard-tier endpoints at 1 credit per request: GET /v1/twitter/search/tweets, /v1/twitter/user/tweets, /v1/twitter/profile, /v1/twitter/tweet, /v1/twitter/user/followers and /v1/twitter/tweet/replies. The dearer X endpoints are /v1/twitter/ai-search at 5 credits, /v1/twitter/profile/full at 5, and /v1/twitter/tweet/transcript at 10. Pagination is billed per page: a list endpoint returns one page plus a cursor and each further page is another billed call. Cache hits and empty pages cost 0 credits. Credits are bought in GBP packs, so there is no printed USD per credit; minPerRequestUsd is null for that reason, not because a minimum is absent.

Cost by endpoint

Per 1,000, at 10,000 tweets a month.

Tweet search price on request
User timeline price on request
Profile lookup price on request
Single tweet price on request
Followers list price on request
Replies price on request

What it can do

Only what the provider's own pages state.

Can post, like or follow not published
Full historical search
Reads login-walled data not published
Published rate limit
A failed request is free
Bulk or batch endpoint not published
Real-time stream not published
Self-hosted option not published
Published uptime SLA not published
Provider states it carries the legal risk not published
twitter

Where these numbers came from

Something out of date? Send the provider's own page to hello@xtwitterapiprices.com and it is corrected on the next capture.