TwexAPI and TwittrAPI both sell access to public X data without an X developer account. TwexAPI bills credits for each tweet or profile it returns. We bill per call, whatever the call returns.
We run TwittrAPI. TwexAPI details below come from its own pages, checked on 19 October 2026. Each number links to its source.
At a glance (as of October 2026)
X-API-KEY headerAuthorization: Bearer headerTwexAPI's range runs from its largest one-time pack to its list rate; its own figure is about $0.05 per 1,000 reads on Proas of Oct 2026. Monthly plans count as if used in full. Per 1,000 tweets assumes 20 tweets per search or timeline call; TwexAPI returns up to 20 tweets per search pageas of Oct 2026.
Tweets: per call vs per item
TwexAPI charges for every tweet it returns, so a page of 20 tweets is 20 reads. On TwittrAPI that page is one call. At 20 tweets per call, 1,000 tweets cost $0.00325 to $0.005, about 8 to 15x less than $0.0416 to $0.05 per 1,000 tweets or profiles, depending on planas of Oct 2026. X decides the real page size, so measure with your own queries.
Bulk profiles
We return up to 500 profiles per call to GET /user/users/by/ids, so 1,000 profiles cost $0.00013 to $0.0002. TwexAPI bills each profile, in a batch too: several profiles by username in one request, $0.05 per 1,000 usersas of Oct 2026. That is at least 208x more per profile. For follower lists, lead lists or CRM syncs, this is the biggest difference.
One profile at a time is different. A single lookup is one call on TwittrAPI ($0.065 to $0.10 per 1,000), which is more than TwexAPI's $0.0416 to $0.05 per 1,000 tweets or profiles, depending on planas of Oct 2026. If you only look up profiles one by one, TwexAPI costs less.
Account actions
Posting, replying, liking or sending a DM is one call on TwittrAPI, at the same price as a read ($0.000065 to $0.0001). TwexAPI charges 50 credits ($0.0005) per post, reply, like or DMas of Oct 2026, about 5x our Standard price. Both use your own X session for this (account actions).
Speed (measured)
We measured live, uncached requests for fresh accounts against both APIs from the same server:
| Endpoint | TwittrAPI p50 / p95 | TwexAPI p50 / p95 |
|---|---|---|
| Profile by username | 591 ms / 780 ms | 592 ms / 842 ms |
| User timeline (by ID) | 953 ms / 1,236 ms | 1,166 ms / 1,510 ms |
| Search, Latest (from:account) | 1,276 ms / 1,594 ms | 1,302 ms / 1,975 ms |
TwexAPI has user timelines by username, not by numeric IDas of Oct 2026, so its timeline was requested by username. Its requests ran on a trial key, paced at half of the trial's rate limit.
Live numbers for TwittrAPI over the last 24 hours are on the status page.
Where TwexAPI is the better fit
- More SDK languages, a CLI and Terraform: SDKs for Python, TypeScript, Go, Java, Kotlin, C#, Ruby and PHP, a CLI and a Terraform provideras of Oct 2026.
- Agent and workflow plugins: n8n nodes, Haystack and Prefect components, and plugins for OpenClaw, Hermes and Paperclipas of Oct 2026.
- No-code browser tools: no-code web tools: follower export, search by date, location finder, hashtag and trend monitoring, profile vieweras of Oct 2026.
- Single lookups: one tweet or profile per call costs less, $0.0416 to $0.05 per 1,000 tweets or profiles, depending on planas of Oct 2026 against our $0.065 to $0.10.
Where TwittrAPI is the better fit
- Tweets: $0.00325 to $0.005 per 1,000 at 20 per call, about 8 to 15x less.
- Bulk profiles: $0.00013 to $0.0002 per 1,000, at least 208x less.
- Account actions: one call each, about 5x less than TwexAPI.
- Account monitoring with webhooks within 1, 5 or 60 s for any public account, 1 account free (Standard, checked at least every 60 s) (monitoring). On TwexAPI: no account monitoring or webhooks listed in its API referenceas of Oct 2026.
- No subscription, no expiry: one prepaid balance that never expires.
- Refunds on 400, 407, 408, 409 or 5xx responses.
Switching
Both take a key in a header and return JSON. Many TwexAPI reads are POST requests with a JSON body; ours are GET requests with query parameters. Map the paths and the fields you read; our endpoints are in the reference.
TwittrAPI is not affiliated with X Corp. Reading data needs no X account.
Frequently asked questions
Is TwittrAPI cheaper than TwexAPI?
For tweets and bulk profiles, yes: $0.00325 to $0.005 per 1,000 tweets and $0.00013 to $0.0002 per 1,000 profiles in batches, against $0.0416 to $0.05 per 1,000 tweets or profiles, depending on planas of Oct 2026 on TwexAPI. For single lookups, one profile per call, TwexAPI costs less.
How do TwexAPI credits compare with TwittrAPI calls?
100,000 credits per USD; a typical post or profile read is 5 creditsas of Oct 2026. A call that returns 20 tweets is 20 reads on TwexAPI and one call on TwittrAPI.
Which one is faster?
We measured both from the same server; the medians are in the table under Speed. Live numbers for TwittrAPI are on the status page.
Do I need a subscription?
Not on either. TwexAPI sells one-time packs and monthly plans. We have a prepaid balance only.
Does either need an X developer account?
No. Both issue their own API keys.
