Twitter API Pricing 2026: X API vs TweetAPI
Compare current X API pay-per-use pricing with TweetAPI request-based plans. See billing units, example calculations, limits, and tradeoffs.
If you last priced the X API when it sold Basic and Pro subscriptions, your spreadsheet needs an update. As of July 2026, the old $200 and $5,000 tiers are gone. Self-serve access uses prepaid credits and pay-per-use billing, while Enterprise remains a custom contract.
TweetAPI takes a different approach: fixed monthly plans with request quotas and per-minute limits. X bills a read per resource returned; most TweetAPI public-data calls consume one request from the plan quota, while a few specialized operations have higher weights. One TweetAPI request that returns 20 posts is not the same billing unit as 20 X Post reads.
So the useful question is not which headline number looks lower. It is what your real workload would cost under each model. That is what this guide helps you calculate.
Last verified: July 16, 2026.
Disclaimer: TweetAPI is a third-party service. Not affiliated with X Corp.
Official X API Pricing in 2026
Here is how the official X API pricing page describes self-serve access:
- You purchase credits in the X Developer Console.
- Read operations are charged per resource returned.
- Write operations are charged per request.
- There is no self-serve subscription or minimum monthly spend.
- Different resources and actions have different unit prices.
Selected X API Read Prices
As of the verification date, these are selected prices from X's self-serve read table:
| Resource returned | Price per resource |
|---|---|
| Post | $0.005 |
| User | $0.010 |
| Follower/following record | $0.010 |
| Direct Message event | $0.010 |
| List, Space, Community, or Note | $0.005 |
| Like, Mute, or Block | $0.001 |
| Profile Update | $0.005 |
Some reads of data owned by the authenticated user receive lower pricing. Check the Developer Console before estimating a production workload because X can update endpoint pricing and access rules.
Selected X API Write Prices
Writes and account actions are billed per request rather than per returned object. Selected published prices include:
| Action | Price per request |
|---|---|
| Create content | $0.015 |
| Create content with a URL | $0.200 |
| Create a DM or user interaction | $0.015 |
| Delete an interaction | $0.010 |
| Manage content | $0.005 |
| Create a list | $0.010 |
| Manage a list or bookmark | $0.005 |
These are pricing units, not rate limits. X maintains separate per-endpoint rate limits, usually across 15-minute or 24-hour windows.
Daily Deduplication
X says that a resource requested more than once during the same UTC day is generally charged once. The deduplication window resets at midnight UTC, and X describes this as a soft guarantee rather than an absolute one.
That can make the official API economical when an application repeatedly refreshes a known set of posts or user records. It is less helpful when every request discovers new resources.
Monthly Cap and Enterprise Access
Self-serve pay-per-use accounts are subject to a 2 million Post-read monthly cap. X directs higher-volume customers to Enterprise.
X Enterprise pricing is custom. Enterprise can add custom or unlimited Post-read volumes, higher rate limits, volume streams, account management, and dedicated support. X does not publish a universal Enterprise price, so any fixed $42,000 figure should be treated as historical rather than current pricing.
How to Estimate an X API Bill
For reads, estimate the number of unique billable resources returned, not just HTTP calls:
estimated read cost = resources returned × resource unit price
Examples using the published rates:
- 50,000 unique Post reads:
50,000 × $0.005 = $250 - 10,000 User reads:
10,000 × $0.010 = $100 - 20,000 follower records:
20,000 × $0.010 = $200 - 5,000 standard content-creation requests:
5,000 × $0.015 = $75
These examples isolate one resource type. A real response can include multiple billable resources or expansions, and same-day deduplication may reduce charges. Use X's Developer Console to confirm the price of the exact endpoints and fields you plan to call.
TweetAPI Pricing in 2026
TweetAPI takes the more predictable budgeting route. You choose a monthly request allowance and a per-minute limit rather than loading credits for each resource returned. Current public prices are listed on the TweetAPI pricing page.
| Plan | Price | Quota | Rate limit | Billing |
|---|---|---|---|---|
| Free | $0 | 100 one-time requests | 10 requests/minute | One-time trial; no credit card |
| Pro | $17/month | 100,000 requests/month | 60 requests/minute | Monthly |
| Ultra | $57/month | 500,000 requests/month | 120 requests/minute | Monthly |
| Mega | $197/month | 2,000,000 requests/month | 180 requests/minute | Monthly |
Endpoint categories stay consistent across the public plans; quota and per-minute limits change by plan. Card subscriptions renew automatically; cryptocurrency purchases require manual renewal.
The effective subscription price per 1,000 quota requests is:
| Plan | Subscription price per 1,000 requests |
|---|---|
| Pro | $0.17 |
| Ultra | $0.114 |
| Mega | $0.0985 |
This calculation describes the TweetAPI subscription quota only. It does not establish a cost-per-Post comparison with X.
Most public data calls follow the request model shown in the API documentation. Some specialized authentication or messaging operations can consume additional quota units, so check the relevant endpoint documentation and your usage dashboard instead of assuming every operation has identical weight.
Why the Two Pricing Models Are Not Directly Comparable
This is the part most pricing comparisons get wrong: the billing unit is different.
| Question | Official X API | TweetAPI |
|---|---|---|
| What is purchased? | Prepaid credits | Monthly plan |
| How are reads measured? | Per resource returned | Against a request quota |
| How are writes measured? | Per action request | Against the plan's applicable quota |
| Does repeated reading help? | Same-day resource deduplication can reduce charges | A repeated API call still uses quota |
| Is there a monthly commitment? | No self-serve minimum | Fixed monthly subscription after trial |
| High-volume option | Custom Enterprise contract | Mega public plan; contact support for private/custom needs |
One TweetAPI collection request may return multiple posts or users. One X API request can likewise return many resources, but X charges for the resources returned. Comparing “100,000 TweetAPI requests” with “100,000 X Post reads” would therefore be misleading.
Where Each Model Fits
Start With the Official X API When
- You need first-party X credentials, OAuth flows, or a procurement-approved source.
- You rely on the official filtered stream or complete archive search. Both are available to self-serve pay-per-use customers, with Enterprise offering higher limits.
- Your application repeatedly reads the same resources and benefits from daily deduplication.
- You need Enterprise-only streams, custom limits, or dedicated account support.
- X data is business-critical and your risk review requires a direct contract with X Corp.
Consider TweetAPI When
- You want a fixed monthly budget for common public Twitter data workflows.
- You need profiles, posts, followers, timelines, search, lists, communities, or supported interaction workflows through one API structure.
- You prefer an
X-API-Keyheader and do not need a separate X developer app for public-data reads. - A 100-request trial is enough to validate response shapes before choosing a plan.
TweetAPI does not replace every official X capability. It does not advertise the official full-archive search, official filtered stream, Enterprise firehose, or an X Corp SLA.
A Simple Estimation Process
- List the exact endpoints you need.
- Estimate pages per job, jobs per day, and resources returned per page.
- For X, apply the published resource or action price and account for same-day deduplication.
- For TweetAPI, estimate monthly API calls and peak calls per minute.
- Add retries, pagination, cache misses, development traffic, and a reasonable safety margin.
- Recheck both pricing pages before launch.
Other Costs Worth Planning For
API charges are only one line in the budget. A production data workflow also needs:
- Storage and retention appropriate to your use case
- Request scheduling, caching, and retry queues
- Monitoring for quota exhaustion and provider errors
- Data deletion and policy-compliance workflows
- Authentication and secret management
- Engineering work if a provider changes an endpoint or response
We have deliberately left dollar estimates out of this section. Storage and compute vary too much with response size, retention, indexing, and cloud provider for one number to be useful.
Twitter API Pricing FAQ
Is the official X API still $200 per month?
No. That was part of the previous subscription-tier model. In July 2026, the self-serve X API uses prepaid credits and pay-per-use pricing. Enterprise is custom.
Is there a free official X API tier?
The current pricing documentation describes pay-per-use credits rather than a general free subscription tier. Some reads of resources owned by the authenticated user have lower published prices, but you should budget from the current Developer Console rather than old Free/Basic/Pro tables.
How much does it cost to read 100,000 Posts from X?
At the published $0.005 Post-read price, 100,000 billable Post resources would cost $500 before considering daily deduplication or any other resources returned. Confirm the exact endpoint price in the Developer Console.
Is TweetAPI cheaper than the official X API?
It depends on the workload. TweetAPI's public plans have lower fixed entry prices, but the units differ. X charges per returned resource and can deduplicate repeated same-day reads; TweetAPI uses a request quota. Model your actual endpoints rather than comparing headline counts.
What happens when I exhaust a TweetAPI quota?
Quota-exhausted requests return HTTP 429 rather than creating an automatic overage bill. You can change plans or, after an active paid card subscription has used at least 80% of its quota, renew the billing cycle early from the dashboard. Do not create multiple accounts to bypass plan limits.
Can I use either API commercially?
Commercial suitability depends on the provider terms, the data workflow, applicable platform rules, and law. Review the TweetAPI terms, X's Developer Agreement and Policy, and your own compliance requirements. This guide is not legal advice.
Put Your Own Workload Through the Numbers
Pick one real job—such as checking 50 profiles every hour or collecting three pages of search results each morning—and estimate both the API calls and the resources returned. That small exercise will tell you more than a headline price comparison.
Use the TweetAPI documentation to count calls, compare the result with current plans, or follow the Node.js tutorial to measure a working integration. The alternatives guide covers cases where the official API or another access model makes more sense.
Try the calculation with 100 free TweetAPI requests. No credit card is required.