xdataapi.io as a twitterapi.io alternative
Same endpoints, a public canary instead of an uptime claim, and credits that do not expire.
What is the same
Both read public X data without an X developer account: profiles, tweets, timelines, threads, followers, following and search with the x.com operators. Both sell prepaid credits and both price a tweet or a profile as one unit. Neither is affiliated with X Corp.
What is different
twitterapi.io charges a minimum of $0.00015 per call, so a search that returns nothing still costs, and a page of five tweets costs the same as a page of twenty. xdataapi.io charges per result: an empty result is free, a failed request is free, and a repeated read within the cache window is half price.
twitterapi.io publishes an uptime percentage. xdataapi.io publishes the checks: a probe outside our network calls the public API once a minute and a canary calls X directly, per endpoint, with 30 days of history and every incident with its cause and duration. For each full hour under 99.9% success, customers who had a failed request in that hour get 2% of their last pack back.
twitterapi.io also sells write actions: posting, liking, following, direct messages. xdataapi.io is read-only and public data only, which is what a legal review wants to see before a company buys.
xdataapi.io ships a hosted MCP server with OAuth sign-in, batch reads of 100 objects per call, an OpenAPI 3.1 document, and TypeScript and Python SDKs. twitterapi.io offers REST and community SDKs.
| twitterapi.io | xdataapi.io | |
|---|---|---|
| Price per 1,000 tweets | $0.15 | $0.125 down to $0.06 |
| Per-call minimum | $0.00015 | none |
| Empty result | charged | free |
| Failed request | charged in some cases | free |
| Credit expiry | bonus credits expire | never |
| Batch lookup | limited | 100 profiles or tweets per call |
| Uptime evidence | a percentage | per-endpoint checks, 30 days, every incident |
| Write actions | yes | no, read-only |
| MCP server | no | hosted, OAuth or key |
| Rate limit | 20 requests per second per account | 20 per second from the first pack, 200 at $600 |
Prices
twitterapi.io prices as read on twitterapi.io/pricing on 2026-09-16: $0.15 per 1,000 tweets, $0.18 per 1,000 profiles, minimum $0.00015 per call. xdataapi.io prices are the packs below; one credit is one tweet or one profile, and followers and following cost 0.1 credit per profile.
| Pack | Price | Credits | Per 1,000 tweets or profiles |
|---|---|---|---|
| Free | $0 | 5,000 | once, no card |
| Starter | $10 | 80,000 | $0.125 |
| Builder | $50 | 500,000 | $0.100 |
| Growth | $200 | 2,500,000 | $0.080 |
| Scale | $600 | 10,000,000 | $0.060 |
Moving over
The endpoints have the same names. Change the base URL to https://api.xdataapi.io, send the key in the x-api-key header, and read data from each response. Cursor pagination works the same way: pass next_cursor back as cursor.
Agents need no code at all: connect the hosted MCP server at https://api.xdataapi.io/mcp. It signs in with OAuth, or takes the same header. The migration notes list every field that differs.
Every new account gets 5,000 credits with no card, which is enough to run your existing integration against both providers and compare the answers before you move traffic.