We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
Paid plans start at $175/mo. There's also a free plan.
X API does not list a current free tier. Pay-Per-Usage has no base subscription, but access requires prepaid credits and API actions incur usage charges. The plan lists a 3,000,000 post-read monthly billing-cycle cap at $0.005 per read; Enterprise contracts can set custom limits above it. Other charges apply to user and owned-data reads, posts, direct messages and URL posts. Requests stop when credits run out or your spending limit is reached.
01Every plan, line by line
| Plan | Billed annually | Billed monthly | Built for |
|---|---|---|---|
| Pay-Per-Usage | — | $0 | Apps paying for API requests |
| Enterprise | — | Quote | High-volume enterprise API users |
| Legacy Free (retired) | — | $0 | Legacy low-volume apps |
| Legacy Basic (retired) | $175 | $200 | Legacy small API projects |
| Legacy Pro (retired) | $4,500 | $5,000 | Legacy high-volume API projects |
Add-ons and overages
- Usage charges: $0.010 per user read, follower or following read, DM event read, and summoned reply; $0.001 per owned-data read; $0.015 per post created or direct message sent; $0.200 per post created with a URL.
- Requests stop when credits reach zero or a user-defined spending limit is reached; overage costs are not published.
02What the plan grid doesn't tell you
Other billable reads
User, follower or following reads, DM event reads and summoned replies are listed at $0.010 each; owned-data reads are $0.001 each.
Publishing charges
Created posts and sent direct messages are $0.015 each. A post created with a URL is listed at $0.200.
Credit exhaustion
Requests stop when prepaid credits reach zero or a user-defined spending limit is reached. Overage costs are not published.
Enterprise contract
Custom limits above the standard monthly post-read cap require an Enterprise contract; the vendor does not publish its price.
03Which plan should you buy?
| If you are… | Get | Why |
|---|---|---|
| New app or pay-as-you-go project | Pay-Per-Usage | No base subscription, but reads and actions are metered, with a listed 3,000,000 monthly post-read cap. |
| High-volume API team | Enterprise | Custom contract and limits above the Pay-Per-Usage post-read cap; pricing is custom. |
| Existing legacy account | Legacy Basic (retired) | The listed $200 monthly or $175 annual-billed plan is retired, not a current sign-up option. |
04Is X API worth the money?
Pay-Per-Usage can suit a project that needs official X access and can forecast its reads and actions, but the lack of a base fee does not make it free. At $0.005 per post read, a read-heavy application can spend thousands per month before publishing and other action charges. Set a spending limit, monitor credits and model each billable endpoint. Enterprise is the route for custom limits, but its price is not published. Retired legacy plans are not a current budget alternative.
X API pricing FAQ
Does X API have a free tier?
No current free plan is listed. Pay-Per-Usage has no base subscription but uses prepaid credits and charges for API activity. Legacy Free is retired, so it is not a free option for new projects.
How much is 1,000,000 X API post reads?
At the listed rate of $0.005 per post read, 1,000,000 reads cost $5,000. This is before charges for other reads, posts or direct messages. Pay-Per-Usage lists a 3,000,000 post-read monthly billing-cycle cap.
What happens when my X API credits run out?
Requests stop when prepaid credits reach zero or when your user-defined spending limit is reached. The pricing information does not publish overage costs. Set a spending limit and build monitoring around credit balance and request volume.
How much does X API Enterprise cost?
Enterprise uses a custom contract, and the price is not published. It is listed for high-volume API users who need custom limits above the 3,000,000 monthly post-read cap. Ask X for a quote based on your expected reads and actions.