Pricing & Billing Guide
TwexAPI pricing model: prepaid Credits at about $0.05 per 1,000 reads, 20,000 free Credits to start, zero-cost failed requests, and a cost comparison against official X API credit consumption.
TwexAPI uses prepaid Credits. Every new account starts with 20,000 free Credits, a typical read costs about 5 Credits per post or profile (roughly $0.05 per 1,000 reads), and you top up with a one-time pack or a monthly plan.
While the official X (Twitter) API has transitioned to a credit consumption model (developer.x.com/#pricing), it charges $0.005 per tweet and $0.010 per follower fetched and imposes a $0.20 surcharge per tweet with a link. At a typical 5 Credits per read, TwexAPI works out to about $0.00005 per post or profile.
Core Pricing Structure
$1 buys about 100,000 Credits.
| Operation | Typical Cost | Approx. USD | Cookie Required? |
|---|---|---|---|
| Read a post (search results, timelines, tweet details, replies) | 5 Credits per post | ~$0.05 per 1,000 | No (API Key only) |
| Read a user (profiles, followers, following) | 5 Credits per user | ~$0.05 per 1,000 | No (API Key only) |
| Create a post | 50 Credits per post (zero URL penalty) | ~$0.50 per 1,000 | Yes (BYOC: Your own Cookie/Token) |
Credit costs can vary by endpoint. See the pricing page for current details, or model your own volume with the X (Twitter) API pricing calculator.
Plans
| Plan | Price | Credits | Validity |
|---|---|---|---|
| Starter | Free | 20,000 | 7 days |
| Mini | $20 one-time | 2,000,000 | 1 day |
| Basic | $50 / month | 5,000,000 per month | Refreshes monthly |
| Pro | $99 / month | 11,000,000 per month | Refreshes monthly |
| Standard | $100 one-time | 10,000,000 | Never expire |
| Plus | $199 one-time | 20,000,000 | Never expire |
| Scale | $499 one-time | 60,000,000 | Never expire |
| Power | $999 one-time | 120,000,000 | Never expire |
Lifetime and enterprise options, plus the rate limit included with each plan, are listed on the pricing page.
The TwexAPI Fair Billing Guarantee
20,000 Free Credits
Every new account starts with 20,000 Credits, enough for about 4,000 typical reads, with no credit card required.
Failed Requests Are Free
If an upstream request fails (e.g. rate-limited by Twitter or target post deleted), TwexAPI returns an error code and deducts 0 Credits from your balance.
No URL Penalty
Posting updates with website links or blog URLs costs the standard 50 Credits (~$0.0005), with no extra fee for links, versus Official X’s $0.200 per-link fee.
Packs or Subscriptions
Buy a one-time Credit pack or a monthly plan. One-time packs from Standard upward never expire; subscription Credits refresh each billing month.
TCO Comparison: TwexAPI vs Official X API
Understanding the total cost of ownership (TCO) across different usage volumes, at about 100,000 Credits per $1:
| Monthly Usage Scenario | Official X API (Credit Pay-As-You-Go) | TwexAPI (Prepaid Credits) | Your Cost Savings |
|---|---|---|---|
| 50,000 tweets read | $250.00 ($0.005 / resource) | $2.50 (250,000 Credits) | 99% saved |
| 250,000 tweets read | $1,250.00 ($0.005 / resource) | $12.50 (1,250,000 Credits) | 99% saved |
| 1,000,000 tweets read | $5,000.00 ($0.005 / resource) | $50.00 (5,000,000 Credits) | 99% saved |
| Exporting 20,000 Followers | $200.00 ($0.010 / resource) | $1.00 (100,000 Credits) | 99.5% saved |
| Posting 1,000 Tweets with URLs | $200.00 ($0.200 / URL request) | $0.50 (50,000 Credits) | 99.75% saved |
| 2,000,000 tweets read | $10,000.00 ($0.005 / resource; pay-per-use is capped at 3M post reads per month) | $100.00 (10,000,000 Credits) | 99% saved |
To model your own monthly volume, use the X (Twitter) API pricing calculator. For an in-depth breakdown of endpoint restrictions, OAuth requirements, and per-resource rates, see our TwexAPI vs Official X API Comparison.
Checking Your Account Balance
You can monitor your remaining account balance programmatically via our balance API or within your user dashboard:
curl -X GET "https://api.twexapi.io/api/balance" \
-H "Authorization: Bearer YOUR_API_KEY"Example response:
{
"code": 200,
"msg": "success",
"data": {
"balance": 48.7525,
"currency": "USD",
"tier": "standard",
"rate_limit_per_minute": 6000
}
}Frequently Asked Questions (FAQ)
How does Credit billing work?
Each successful request made with your Authorization: Bearer <KEY> deducts Credits from your balance based on what it returns, typically 5 Credits per post or profile. Responses returning 4xx or 5xx status codes are never deducted.
Why is Official X Pay-As-You-Go more expensive than TwexAPI?
Official X bills $0.005 per post and $0.010 per follower returned, and adds a $0.20 fee for posts with links. A search returning 50 tweets costs $0.25 on Official X; the same 50 tweets cost about 250 Credits (~$0.0025) on TwexAPI.
Do Credits expire?
It depends on the plan. One-time packs from Standard ($100) upward never expire. Mini ($20) is valid for one day, the free Starter Credits for 7 days, and Basic and Pro subscription Credits refresh each billing month. You can cancel a subscription anytime from the dashboard.
Can I set up automated balance alerts or auto-recharge?
Yes. Through the dashboard or webhook integrations, you can configure email notifications when your balance dips below a custom threshold to avoid any interruption to your live production bots.
How does TwexAPI compare to building an in-house Puppeteer scraper?
A self-hosted scraping setup costs an average of $350–$800/month for residential proxies, anti-bot CAPTCHA solvers, and headless browser servers, plus dozens of engineering hours maintaining broken DOM selectors. TwexAPI handles all proxies and browser fingerprinting internally for a fraction of the cost. Read the Self-Hosted Scraper vs TwexAPI Analysis for full cost modeling.