X API Pricing in 2026: What Each Tier Really Costs

As of 2026, the X (Twitter) API defaults to pay-per-use for new developers: you load credits and pay per call, roughly $0.005 per post read, $0.015 per post created, and $0.001 per owned resource, with post reads capped at 2 million per month before Enterprise is required. The old subscription tiers ($200 and $5,000 per month) are closed to new signups, and Enterprise starts around $42,000 per month. For anyone doing cold outreach, that pricing is the whole story: the official API prices you out, so most people use an alternative.

Here is the full breakdown, verified against X's own documentation as of July 2026, plus the alternatives that actually make outreach viable.

The X API pricing model in 2026

X moved to a pay-per-usage model instead of the old fixed monthly buckets. Rather than subscribing to a tier with a set allowance, you load credits into the developer console and get billed per API request (source: X API pricing docs, verified July 2026).

The per-call rates, as documented:

• Post read: about $0.005 per post
• User read: about $0.010 per user
• Owned reads (your own posts, bookmarks, followers, lists): about $0.001 per resource
• Post created: about $0.015 per write
• Post with a link: about $0.20 per write

There is one useful mechanic: resources are deduplicated within a 24-hour UTC window. If you request and pay for a post, requesting that same post again inside the same day does not incur another charge.

The caps and the tiers

Pay-per-use is not unlimited. It is capped at 2 million post reads per month. Cross that threshold and you are pushed onto Enterprise, which starts around $42,000 per month.

The legacy subscription tiers still exist, but only for people already on them:

• Basic, $200/month, existing subscribers only
• Pro, $5,000/month, existing subscribers only
• Free tier, discontinued for practical purposes

So a new developer in 2026 has two real options from X directly: pay-per-use with per-call billing, or Enterprise at five figures a month. There is no cheap on-ramp anymore.

Why this prices outreach out

Run the math for cold outreach and the problem is obvious.

Outreach is read-heavy before it is write-heavy. To build one lead list you read a target's followers, then read each profile to check follower count, bio, verified status, and whether they can receive a DM. At roughly $0.005 to $0.010 per read, a few thousand prospects turns into real money before you have sent a single message. Scale to the volume that makes outreach worthwhile and you approach the 2 million read cap, which throws you onto Enterprise.

Then there is DM access itself. The official API's direct message endpoints are built for messaging people who already interact with your app, not for reaching strangers at scale, and they carry their own rate limits. The API is designed for products that read timelines and post content, not for a pipeline of cold DMs.

The result: for outreach, the official X API is either too limited (pay-per-use caps and DM restrictions) or too expensive (Enterprise). Neither fits a founder or agency trying to book calls.

A quick cost example

Say you want to build a single 5,000-lead list from a competitor's followers and enrich each profile. Reading the follower list plus one read per profile to check bio, follower count, verified status, and DM-ability is thousands of read calls. At roughly $0.005 to $0.010 per read, that one list runs into tens of dollars before any message goes out. Do that a few times a week across multiple targets, add the reads for reply tracking, and you are pacing toward the 2 million monthly read cap and the Enterprise cliff behind it. The write side is cheaper per unit, but by then the reads have already made the case: the official API bills you for the exact behavior outreach depends on, at every step.

Developers are already routing around it

The pricing is not just a line item, it is actively pushing builders to find another way. In an r/webdev thread titled "X / Twitter data is too expensive, so I fixed it" (63 upvotes), the developer u/Even_Leading4218 explained why he built a free workaround:

"I know the struggles of dealing with expensive data at an early stage ... you can gather roughly 30k tweets in less than an hour, and Twitter would charge you $400 to get the exact same data through their API."

Treat the $400 as one developer's own estimate rather than an official quote, but the direction is what matters: the cost gap is large enough that people build their own tools instead of paying. That is the entire reason a market of cheaper alternatives exists. When the official price forces every early-stage builder to become a scraper, the alternatives below are not corner-cutting, they are the rational default.

Cheaper alternatives

There are two categories of alternative, depending on what you actually want.

1. Third-party X API providers (for developers)

If you want to build something and just need data cheaply, Third-party X API providers resell X access at a fraction of the official cost. Reads run around a fraction of a cent per call, DM sends a few cents, flat, with no monthly minimum and no Enterprise cliff. They also expose endpoints the official API prices out of reach, including reading DM conversations, which is what makes reply tracking possible.

You still build the outreach layer yourself: pacing, personalization, retries, dedupe, and reply detection. The API is cheaper, but the engineering is on you. Our guide to sending Twitter DMs programmatically covers what that build involves.

2. A managed outreach tool (for booking calls)

If your goal is calls, not infrastructure, the cheapest path is to not touch the API at all. A managed tool connects an account, sources leads, sends, paces, and tracks replies for one flat price.

XAutoDM works this way. You connect your X account by pasting session cookies, no developer app, no API keys, no per-call billing. Pricing is a flat per-account monthly rate starting at $29 for a single account, with a free Test plan that needs no card. That covers scraping targeted lead lists, launching campaigns with follow-up sequences that stop on reply, safe pacing with warm-up, and a reply inbox to track every conversation.

Compare the models honestly. On pay-per-use, the reads alone to build and message a few thousand-lead pipeline can run well past a flat monthly plan, and you still have to build the outreach system. A per-account tool is predictable and includes the parts that actually matter for replies.

Which should you choose?

• You are building a data product or a niche integration: a third-party provider on price and endpoint coverage.
• You need one transactional DM inside your own app: the official X API v2, budgeted for per-call costs.
• You want booked calls from cold DMs: a managed tool. The API economics do not favor outreach, and a flat per-account price does.

For the sourcing side, see the Twitter scraper API guide. For the strategy, the complete Twitter lead generation playbook and Twitter mass DM strategy. A developer API for XAutoDM is on the roadmap as early access.

The takeaway: X API pricing in 2026 is pay-per-use with a hard read cap and a five-figure Enterprise cliff, and the free and cheap tiers are gone for new signups. For outreach, that math rarely works. Start with the free plan, one account, no card, and skip the API bill entirely.

Frequently Asked Questions

How much does the X API cost in 2026?

As of 2026, the X API defaults to pay-per-use for new developers. You load credits and are billed per call: about $0.005 per post read, $0.010 per user read, $0.001 per owned resource read, $0.015 per post created, and $0.20 per post that contains a link. Pay-per-use is capped at 2 million post reads per month before Enterprise is required.

Is there a free X API tier?

The free tier has been discontinued for practical purposes. New developers start on pay-per-use, which means you pay per API call from the first request. The old Basic ($200/month) and Pro ($5,000/month) subscription tiers remain available only to existing subscribers, not new signups.

Why is the X API so expensive for outreach?

The X API is priced for apps that read and post, not for cold outreach at scale. Per-call read and write costs add up quickly across thousands of prospects, DM-specific access is limited, and going past the 2 million monthly read cap forces you onto Enterprise, which starts around $42,000 per month. For outreach the economics rarely work.

What are cheaper alternatives to the official X API?

For reading data, third-party X API Third-party X API providers charge a fraction of a cent per call with no monthly minimum. For outreach specifically, a managed tool such as XAutoDM skips the API entirely: you connect an account by pasting cookies and pay a flat per-account price with safe pacing built in.

Do I need the official X API to send cold DMs?

No. The official API is one route, but it is expensive and limited for DMs. Most cold outreach runs through session-based tools that act on behalf of a logged-in account, no developer app or API keys required. A managed tool handles the sending, pacing, and reply tracking so you do not touch the API at all.