Twitter API Cost in 2026 — What You'll Actually Pay Per Request

In January 2026, X killed the old fixed-tier pricing and moved the entire API to a pay-per-use model. No more $200/month Basic or $5,000/month Pro plans for new signups. Every request now has a per-unit cost.

Most guides haven't caught up. They're still listing the old tiers. This post covers the current pricing — what each request actually costs, what a real monthly bill looks like at different volumes, and how it compares to third-party alternatives.

The New X API Pay-Per-Use Model

As of February 2026, the official X API uses consumption-based billing. You buy credits upfront in the Developer Console, and credits are deducted per request.

Here's what each operation costs:

Operation	Cost Per Request
Post read (fetch a tweet)	$0.005
User profile lookup	$0.010
DM event read	$0.010
Post create (write a tweet)	$0.010
DM interaction create	$0.015
User interaction create (follow, like, retweet)	$0.015

Key details:

• No monthly subscription — you only pay for what you use
• 24-hour deduplication — fetching the same resource twice in one UTC day counts as one charge
• Monthly cap — pay-per-use is capped at 2 million post reads. Beyond that, you need Enterprise pricing
• Spending caps available — you can set a max monthly spend in the Developer Console
• xAI credit incentive — spend $200+/month and get 10-20% back as xAI API credits

Sources: X Developer Community announcement, X API pricing page

What Did the Old Tiers Cost?

For context, here's what X charged before January 2026 (these are no longer available to new signups):

Tier	Monthly Price	Post Reads	Post Writes
Free	$0	None (write-only)	1,500/month
Basic	$200/month	15,000/month	50,000/month
Pro	$5,000/month	1,000,000/month	300,000/month
Enterprise	$42,000+/month	Custom	Custom

The Basic tier was originally $100/month, then doubled to $200/month in January 2025. The jump from Basic ($200) to Pro ($5,000) — a 25x increase — was the main complaint from developers.

Pay-Per-Use vs Old Tiers: Which Was Cheaper?

Let's do the math that matters. If you were on the old Basic plan ($200/month for 15K post reads + 50K user reads), here's what the same usage costs under pay-per-use:

Operation	Volume	Pay-Per-Use Cost
Post reads	15,000	$75
User lookups	50,000	$500
Total		$575/month

Pay-per-use is ~3x more expensive than the old Basic plan for the same usage. The new model benefits developers who do less than ~$200 worth of requests. For heavier users, it's actually a price increase.

Where pay-per-use wins: if you only need 5,000 post reads/month, that's $25 — far cheaper than the old $200/month Basic floor.

How GetXAPI Compares

GetXAPI uses per-call pricing with no credits to buy upfront:

Endpoint Type	GetXAPI Cost	Official X API Cost	Savings
Tweet/post read	$0.001	$0.005	5x cheaper
User profile lookup	$0.001	$0.010	10x cheaper
Tweet create	$0.002	$0.010	5x cheaper
DM read	$0.002	$0.010	5x cheaper
DM send	$0.002	$0.015	8x cheaper
Follow / like / retweet	$0.001	$0.015	15x cheaper

No credits to pre-purchase, no monthly cap, no developer account application.

Real Monthly Cost at Different Volumes

Here's what a mixed workload (post reads + user lookups + some writes) actually costs at different scales:

Light usage: 5,000 requests/month

Typical for: side projects, monitoring bots, small research tasks

	Official X API	GetXAPI
3,000 post reads	$15.00	$3.00
1,500 user lookups	$15.00	$1.50
500 post creates	$5.00	$1.00
Monthly total	$35.00	$5.50

Medium usage: 50,000 requests/month

Typical for: SaaS tools, analytics dashboards, content apps

	Official X API	GetXAPI
30,000 post reads	$150.00	$30.00
15,000 user lookups	$150.00	$15.00
5,000 post creates	$50.00	$10.00
Monthly total	$350.00	$55.00

Heavy usage: 500,000 requests/month

Typical for: data pipelines, large-scale scraping, enterprise tools

	Official X API	GetXAPI
300,000 post reads	$1,500.00	$300.00
150,000 user lookups	$1,500.00	$150.00
50,000 post creates	$500.00	$100.00
Monthly total	$3,500.00	$550.00

The gap gets larger as your volume increases, especially if your workload is user-lookup heavy (10x difference per request).

Hidden Costs Beyond the API Bill

Developer account approval

The official X API requires a developer account application. Approval can take days or weeks, and X rejects use cases it considers competitive. GetXAPI has no approval process — sign up and start making requests.

Rate limit engineering

The X API enforces per-endpoint rate limits. You'll need retry logic, exponential backoff, and request queuing. That's engineering time that doesn't show up on your API bill but adds to total cost of ownership.

The 2M monthly cap

Pay-per-use caps at 2 million post reads. If you need more, you're pushed to Enterprise pricing ($42,000+/month). There's no gradual scaling path between $10K/month in pay-per-use spend and $42K/month Enterprise.

When the Official X API Makes More Sense

Third-party APIs aren't always the right choice:

• Compliance requirements — some enterprise contracts or regulated industries require direct API access from the platform provider
• Official OAuth integration — if you're building an X platform app that needs user authentication flows
• Firehose-level streaming — Enterprise tier includes filtered streams and real-time data that third-party APIs don't replicate
• xAI credits matter to you — if you're also building on xAI, the 10-20% credit kickback could offset some cost

For data collection, research, monitoring, analytics, and bot-building, per-call pricing through a third party is almost always cheaper.

Calculate Your Exact Cost

Plug your actual request volumes into the Twitter API Cost Calculator to see a side-by-side monthly estimate.

Or check the full endpoint pricing breakdown to see what every GetXAPI endpoint costs.

Try It Free

GetXAPI gives you $0.10 in free credits at signup — enough to test any endpoint with no credit card required. Get your API key →

---

Pricing data sourced from the X API pricing page and X Developer Community as of March 2026. GetXAPI pricing verified February 9, 2026.