X (Twitter) API Pricing: Complete Guide for 2026

If you’re trying to figure out X (Twitter) API pricing in 2026, the short version is this: there is no real free tier anymore, the default for new developers is pay-per-use, and the rules changed again in April. The math gets ugly fast if you’re posting at any kind of volume.

I’ve watched a few founder friends get burned trying to build directly on the X API this year. So I want to lay out exactly what it costs in 2026, walk through real-world dollar amounts at different usage levels, and be honest about when it makes sense to skip the X API entirely and use a wrapper like Blotato instead.

This is the no-fluff version. If you want the official policy doc, X has one. If you want to know what you’ll actually pay, keep reading.

X API Pricing at a Glance (2026)

Tier	Monthly cost	Best for	Key limit
Pay-per-use	$0 base + per-call charges	New developers, low-volume use	2 million post reads/month
Basic (legacy)	$200/mo	Existing subscribers only	Closed to new signups
Pro (legacy)	$5,000/mo	Existing subscribers only	Closed to new signups
Enterprise	$42,000+/mo	Heavy data buyers	Custom terms

Pay-per-use is the only path for anyone signing up today. Basic and Pro still exist, but only for accounts that subscribed before the cutover. Enterprise is a sales conversation, not a self-serve product.

What Changed in 2026

Two things you need to know.

February 6, 2026: pay-per-use launched as the default. Instead of paying a flat monthly fee for a bucket of calls, you load credits into the developer console and get charged per API request. New developers can no longer sign up for the old $200 Basic or $5,000 Pro plans.

April 20, 2026: prices and access shifted again. Three updates landed at once:

• “Owned reads” (your own posts, bookmarks, followers, lists) dropped to $0.001 per resource. A meaningful cost cut for most publishing use cases.
• Standard writes (creating a text or media post without a URL) went from $0.010 to $0.015 per request.
• Posts containing a URL jumped to $0.20 per request. That’s a 1,900% increase over the original $0.010 write price, and it lands on anyone auto-posting links.

X also moved a few actions out of self-serve and into Enterprise-only access on the same date: following accounts, liking posts, and quote-posting are no longer available on pay-per-use. If your build relied on any of those, you need an Enterprise contract or a different approach.

Net effect: light publishers reading their own data win. Anyone posting links at volume, or running a workflow that follows or likes from the API, just got priced or locked out.

Pay-Per-Use, in Plain English

Every API call costs something. Here’s the cheat sheet:

Operation	Price
Read your own post (owned read)	$0.001 per resource
Read a third-party post	$0.005 per resource
Read a user, following, followers, trends	$0.010 per resource
Create a text or media post (no URL)	$0.015 per request
Create a post containing a URL	$0.20 per request
Send a DM	$0.015 per request
User management actions (block, mute)	$0.015 per request
Delete a post	$0.005 to $0.010 per request
Follow, like, quote-post	Enterprise-only (not available on pay-per-use)

A few things to keep in mind:

The 24-hour deduplication rule is your friend. If you fetch the same post or user profile more than once within a UTC day, you’re only charged for the first request. The window resets at midnight UTC. This is built specifically to prevent you from getting hammered when a webhook re-fires or a polling job double-runs.

Per-resource pricing means batched requests still cost real money. A single API call that returns 100 posts isn’t $0.005. It’s $0.005 multiplied by 100. This is the line item that catches almost everyone off guard.

The URL-post tax is the headline gotcha. A standard post is $0.015. A post containing any URL is $0.20. If you’re auto-publishing newsletter links, blog posts, YouTube videos, affiliate URLs, or anything with https:// in the body, every post is more than 13x more expensive than a plain-text post. Run the math before you ship a workflow that does this at volume.

Rate limits are separate from cost. Even on pay-per-use, you’ll hit per-endpoint rate limits (15-minute and 24-hour windows). Spending more credits doesn’t lift them. You’ll see HTTP 429s before you ever hit your cap.

The 2 Million Post Reads Cap

Pay-per-use isn’t unlimited. There’s a hard ceiling of 2 million post reads per month. Above that, X requires you to move to Enterprise.

Enterprise isn’t a checkout-page upgrade. It’s a sales call, a use-case review, and pricing that starts at $42,000 per month. Plan around the 2M cap as a real constraint, not a soft suggestion. If your usage is anywhere close to it, build the alternative path before you hit the wall.

The xAI Credit Kickback (Read This Before You Spend)

X runs a credit-back program tied to cumulative pay-per-use spend. The more you spend, the higher the percentage that comes back as xAI API credits:

Cumulative spend	xAI credit kickback
$0 to $199	0%
$200 to $499	10%
$500 to $999	15%
$1,000+	20%

The credits are usable on xAI’s API, not the X API itself. Useful if you’re already building Grok-powered features. Less useful if you weren’t planning to. Don’t let the kickback talk you into spending more than you would have otherwise.

Real-World Cost Examples

This is where the abstract numbers get concrete. Three personas, with the math.

The Indie SaaS Publisher

You’re a one-person SaaS founder posting 10 updates a day to your company X account. You also pull your own engagement metrics once an hour to power a small dashboard.

• 300 writes/month at $0.015 = $4.50
• 720 owned reads/month at $0.001 = $0.72
• Total: about $5/month

Pay-per-use is genuinely cheap at this scale. If your usage looks like this, the API is fine.

The Agency Posting for 20 Clients (with Links)

You’re a small agency publishing roughly 5 posts per client per day across 20 client accounts. Half of those posts contain a link (a blog post, a product page, a tracking URL).

• 1,500 plain writes/month at $0.015 = $22.50
• 1,500 URL-containing writes/month at $0.20 = $300
• Weekly engagement pulls: 4,000 owned reads at $0.001 = $4
• Total: about $325/month

The URL tax flips the economics. A workflow that’s mostly link-posting on behalf of clients is no longer a $50 line item. On top of that, you still have to build OAuth, retry logic, queueing, and an approval UI. This is the bracket where most agencies tap out and use a publishing tool that abstracts the whole thing.

The Brand Monitor

You want to track every mention of your brand name across X. Roughly 10,000 mentions a month, plus you pull author profiles and follower counts on each.

• 10,000 post reads at $0.005 = $50
• 10,000 user reads at $0.010 = $100
• Total: $150/month, before any historical backfill

This is where pay-per-use starts to bite. Add competitor monitoring on top, or any kind of historical research, and you’ll see the bill climb fast. If your job is reading X data at volume, the math often points toward a third-party data provider instead of the official API.

Already on Legacy Basic or Pro?

If you subscribed before the February 2026 cutover, you keep your plan. Quick refresh on what they include:

• Basic ($200/mo, $175/mo annual): 50,000 posts/month at the app level (3,000 per individual user), 15,000 reads/month, 2 app IDs.
• Pro ($5,000/mo, $4,500/mo annual): 300,000 posts/month, 1,000,000 reads/month, 3 app IDs, filtered stream and full-archive search included.

Both plans are closed to new signups. Compare your bucket usage against pay-per-use math at your real volume. For most low-to-mid volume publishers, pay-per-use is now cheaper than Basic. For data-heavy users, Pro can still win, but the long-term direction X has signaled is pay-per-use plus Enterprise.

The Honest Pitch: Skip the X API and Use Blotato

I’d be a bad founder if I didn’t tell you the trade-off. Building directly on the X API in 2026 means you sign up for:

• Per-resource billing on every call
• A 2M post-reads ceiling that forces an Enterprise conversation if you grow
• OAuth 2.0 token management (and the refresh logic that comes with it)
• Compliance review for any AI-related use case
• Your own retry, rate-limit, and queue layer
• Building this all over again for every other platform you want to publish to

If your goal is to publish content to X (and to other platforms), most of that work is wasted motion. Blotato handles it for you and gives you one API to publish across X, Instagram, LinkedIn, TikTok, YouTube, Threads, Facebook, Pinterest, and Bluesky.

What you can publish through Blotato:

• Text posts, images, videos, and threads to X
• The same payloads to 8 other platforms in the same call
• Scheduled or immediate publishing
• AI-generated content via the same endpoint

A minimal example of posting to X via Blotato:

curl -X POST https://backend.blotato.com/v2/posts \
  -H "blotato-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "post": {
      "accountId": "YOUR_X_ACCOUNT_ID",
      "target": { "targetType": "twitter" },
      "content": { "text": "Posted via the Blotato API." }
    }
  }'

One call, one auth header, no rate-limit logic on your side. If you want to cross-post the same content to LinkedIn, you change the targetType and reuse the same code path.

The MCP angle matters too. Blotato runs an MCP server at https://mcp.blotato.com/mcp, which means Claude (or any MCP-compatible agent) can publish to your social accounts directly. If you’re building AI-driven content workflows, this is the shortest path from “agent decides to post” to “post is live.”

Worth calling out: there’s no URL-post tax on Blotato. A post containing a link costs the same as a plain-text post on every platform Blotato supports.

Blotato’s API is included on every paid plan, starting at $29/month for Starter with a 7-day free trial.

Sabrina’s Take

The X API in 2026 is a developer product, not a publisher product. If you’re building search, analytics, or research tools, you live with the per-call math and probably look at third-party providers above a certain volume. If you just want to post to X (and probably to four other platforms while you’re at it), the X API is the wrong layer to build on.

I’m biased, obviously. But I built Blotato because I was tired of stitching five APIs together to ship one piece of content. The pricing changes this year made that bet age well.

FAQs

Is there a free X API tier in 2026?

Not in any practical sense. The old free tier is gone for new developers, and pay-per-use requires a credit balance to make calls. Pay-per-use is cheap at very low volume (a few dollars a month for light publishing), but there’s no zero-cost option anymore.

How do I get access to the X API?

Sign up at developer.x.com, create an app inside a project, and go through the pay-per-use onboarding. You’ll add a payment method and load credits before you can make calls. Approval is automated for standard use cases. AI and bot use cases trigger an additional review.

Why did the X API get so expensive?

X moved away from the old open-access model in 2023 and has been tightening monetization since. Pay-per-use is the latest version, and on paper it’s friendlier to small developers (a $5/month indie publisher is genuinely supported). The cost pain hits hardest for anyone reading data at volume.

What happens if I hit the 2 million post reads cap?

Your reads stop until the cap resets at the start of the next month, or until you upgrade to Enterprise. Enterprise is a custom contract starting around $42,000/month, with selective approval and a multi-week sales process. If you’re approaching the cap, start that conversation early or build a fallback path through a third-party provider.

Can I still get the $200 Basic or $5,000 Pro plan?

Only if you already had one before the cutover. New subscribers can’t sign up for either tier. If you’re on Basic or Pro today, you can keep your subscription, but X has signaled that the long-term direction is pay-per-use plus Enterprise.