Twitter enterprise API pricing and cheaper options
Twitter enterprise API pricing: what X publishes, what it does not, how the Premium API name fits in, and what the same reads cost on pay-per-use or ChatterAPI.
Piyushh · November 13, 2026 · 3 min read

X does not publish Twitter enterprise API pricing. Its pricing page tells higher-volume customers to upgrade to an Enterprise plan and points them to a contact form, so the cost comes as a quote. X does publish its pay-per-use rate card, and for many read-only jobs that card is where the cost question gets answered. Below: what is public, what the Premium API name refers to today, and what the same reads cost elsewhere.
All of X's prices below come from X's pricing page, checked 2026-11-13. Prices change, so confirm them there before you budget.
What X publishes about enterprise pricing
The page presents pay-per-use as the main plan: "No contracts, subscriptions, or minimum spend." For volume past that, it tells you to upgrade to an Enterprise plan, but it lists no price and no tiers for Enterprise. I couldn't find a number on the page, and I won't make one up. If you need a figure, the contact form is the only way to get one.
So if you searched "twitter enterprise api cost", the answer is to ask X. Expect the price to depend on your volume and on which products you need.
The premium API name
Older articles describe a Twitter API premium plan, with its own price and tiers. X's pricing page today lists only pay-per-use and Enterprise, with no Premium tier. I did not research the plan's history, so if you find an older quote for "twitter premium api pricing", treat it as out of date and check with X.
People use enterprise API Twitter, premium Twitter API and Twitter API enterprise loosely for the same idea. What matters is what X sells now, and the pricing page shows that.
What the pay-per-use rate card says
These are the listed read prices for each resource:
| Resource read | Price |
|---|---|
| Posts | $0.005 |
| Users | $0.010 |
| DM events | $0.010 |
| Following and followers | $0.010 |
| Likes, mutes, blocks | $0.001 |
| Owned reads (your own data) | $0.001 |
Writes are priced per request. A post costs $0.015, or more when it includes a URL. That is the current published rate card. Reading 100,000 posts comes to $500 at the listed post rate, before any other reads.
Full-archive search, the endpoint that goes back to March 2006, is not limited to Enterprise. X's search docs say pay-per-use and Enterprise customers can both use it. Historical Twitter data explains how it works. For a calculator and a summary of the rates, see the X API pricing calculator.
When enterprise makes sense
Enterprise is for volume and guarantees. X's filtered stream docs list some limits that differ between pay-per-use and Enterprise, such as the number of connections and rules. If you need many simultaneous connections, a contract or support terms, you have to talk to X.
If you only need to read public tweets, profiles and followers, you may not need Enterprise at all.
A cheaper way to read X data
ChatterAPI is an independent read API for Reddit and X, with no affiliation to X Corp. It charges in credits rather than per resource, and the unit is a page:
- 2 credits for a page of about 20 tweets from search or a timeline
- 2 credits for a page of about 20 followers
- 2 credits for a tweet lookup
Plans: Starter $19 for 35,000 credits, Growth $49 for 98,000, Scale $149 for 336,000. At 2 credits a page, Starter covers about 17,500 pages, or around 350,000 tweets if every page is full. Run your own count at X's listed rate for comparison: 350,000 post reads at $0.005 is $1,750.
That comparison is arithmetic on two public price lists. It says nothing about quality, and the two are different products. An independent read API gives you fewer guarantees than a contract with X, and X is the right choice when you need a first-party agreement. We do not offer a push stream, webhooks, a trends endpoint or likes.
A search call:
curl -s "https://api.chatterapi.com/v1/x/tweets/search?q=enterprise%20api&sort=latest" \
-H "Authorization: Bearer $CHATTERAPI_KEY"
The response carries data, a page with nextCursor, and credits with what was charged. Failed calls cost nothing. See the search endpoint docs.
How to decide
- Write down the calls you need each month and how many rows each one returns.
- Price them at X's rate card, then at a credit plan.
- If you need a contract, a stream, or more guarantees than a self-serve plan gives, ask X for an enterprise quote.
- If you read public data on a schedule, test the cheaper route first.
The pricing page shows what the same reads cost here. For everything a hosted route needs, read does Twitter have an API.