cheapxapi vs Official X API
cheapxapi vs the official X API (pay-per-usage).
For reading public X data, cheapxapi costs $0.03 per 1,000 posts against $5.00 on the official API, with no monthly ceiling. Stay on the official API if your app acts for users through OAuth or needs webhooks.
What each one does.
| Item | cheapxapi | Official X API |
|---|---|---|
| Billing | Per call, prepaid balance | Per resource returned, prepaid credits |
| Monthly ceiling | None | 3 million post reads, then Enterprise |
| Credential | One API key (x-api-key header) | X developer app, Bearer token or OAuth |
| Acting for other users | Your own X accounts, by logging in ($0.10) | Any user who authorizes your app (OAuth) |
| Push events (webhooks) | No, you poll | Yes, X Activity API, billed per event |
| Response format | JSON with full author profile on every tweet | JSON, fields chosen per request (expansions) |
Price per 1,000, side by side.
| Job | cheapxapi | Official X API |
|---|---|---|
| 1,000 posts from search or a timelineUp to 20 tweets per call | $0.03 | $5.00 |
| 1,000 profiles by ID (batches of 20) | $0.03 | $10.00 |
| 1,000 profiles, one lookup each | $0.60 | $10.00 |
| 1,000 followers with profilesUp to 100 per call | $0.006 | $10.00 |
| Post one tweetOfficial: $0.20 if the post has a link | $0.0006 | $0.015 |
“The X API uses pay-per-usage pricing. No subscriptions—pay only for what you use.”
The code change.
Same search query syntax. Swap the Bearer token for the x-api-key header and rename a few fields.
curl "https://api.x.com/2/tweets/search/recent?query=from%3ANASA&max_results=100&tweet.fields=created_at,public_metrics" \
-H "Authorization: Bearer $X_BEARER_TOKEN"
# posts in data[], likes in public_metrics.like_count,
# next page: meta.next_token -> pagination_tokenQuestions.
Does the official X API still have Basic and Pro plans?
Its pricing page now reads: “The X API uses pay-per-usage pricing. No subscriptions—pay only for what you use.” Reads are charged per resource returned ($0.005 per post, $0.01 per user), and pay-per-usage accounts are capped at 3 million post reads a month (checked 19 November 2026).
Why is cheapxapi cheaper per post?
The official API charges for every post in the response. cheapxapi charges per call, and a search or timeline call returns up to 20 posts, so a full page costs $0.0006 instead of $0.10. Pages can hold fewer posts when X leaves some out, which raises the cost per post.
When should I stay on the official API?
When your app acts for users who sign in with X (OAuth), when you need webhooks, or when you need X's own terms and support. cheapxapi reads public data and acts only as X accounts you log in to yourself.
How long does switching take?
For reads, change the URL, swap the Bearer token for the x-api-key header, and map a few field names (data to tweets, public_metrics.like_count to likeCount, next_token to next_cursor). Search uses the same X query syntax.