# X (Twitter) API Pricing in 2026: What Every Call Actually Costs

> X replaced its monthly API tiers with pay-per-usage credits. Creating a post costs $0.015, but a post containing a link costs $0.200. Here is the full price list and what a real posting schedule costs.

**Source:** https://posteverywhere.ai/blog/x-twitter-api-pricing
**Author:** Jamie Partridge
**Published:** 2026-09-01

---

_Last updated: September 2026._

X API pricing changed shape in 2026. There are no monthly tiers to choose from any more. You buy credits, and every API call deducts from the balance.

The number that matters most is not on the front of the pricing page. Creating a post costs $0.015. Creating a post that contains a link costs $0.200. That is 13 times more expensive, and since almost every marketing post carries a link, it is the line item that will dominate your bill.

This guide lists every published rate from [X's official pricing documentation](https://docs.x.com/x-api/getting-started/pricing), works out what a real posting schedule costs per month, and covers the cases where paying per call is the wrong choice.

## Table of Contents

1. [The 30-Second Answer](#the-30-second-answer)
2. [What Changed in 2026](#what-changed-in-2026)
3. [Write Pricing: Every Published Rate](#write-pricing-every-published-rate)
4. [The $0.20 Link Tax](#the-020-link-tax)
5. [What a Real Posting Schedule Costs](#what-a-real-posting-schedule-costs)
6. [Read Pricing and the 3 Million Cap](#read-pricing-and-the-3-million-cap)
7. [Ways to Publish Without Paying Per Post](#ways-to-publish-without-paying-per-post)
8. [When the X API Is Still the Right Call](#when-the-x-api-is-still-the-right-call)
9. [FAQ: X API Pricing](#faq-x-api-pricing)

## The 30-Second Answer

X API pricing in 2026 is pay-per-usage with no subscription. You purchase credits upfront and each request deducts from the balance. Creating a post costs $0.015 per request. Creating a post that contains a URL costs $0.200 per request. Reading a post costs $0.005 per resource, capped at 3 million post reads per monthly billing cycle. Reading your own data through owned-read endpoints costs $0.001 per resource.

For a publishing workload, budget on write calls and assume most of your posts will carry a link. Thirty link-bearing posts a month costs $6.00 in API fees. Three hundred costs $60.00. If publishing is all you need, a scheduling tool that holds its own X credentials is normally cheaper, because the per-post fee disappears into a flat subscription. We break the alternatives down in [ways to publish without the API](/x-scheduler).

## What Changed in 2026

X previously sold fixed monthly access tiers. Those have been replaced. X's own documentation now describes the model in four lines: "No subscriptions, pay only for what you use", "No contracts or minimum spend. Stop anytime", credit-based billing where you "purchase credits upfront", and live cost monitoring in the developer console.

The practical consequences are worth spelling out, because they cut both ways.

The good news is that small projects got dramatically cheaper. A hobby bot that posts twice a day and reads nothing used to require a monthly subscription. It now costs cents. There is no floor, so a script that runs occasionally costs almost nothing.

The bad news is that costs now scale linearly with volume and are much harder to forecast. A fixed tier gave you a ceiling. Credits give you a meter. If a retry loop misfires, or an [automation workflow](/social-media-automation) fans out across more accounts than you expected, the bill grows with it. Anyone building on the [X API](https://docs.x.com/x-api/introduction) should set up cost monitoring before shipping, not after.

One detail that catches people out: reads are deduplicated within a 24-hour UTC day window. Requesting the same resource twice in one UTC day is billed once. Requesting it either side of midnight UTC is billed twice.

> **Publishing to X without touching the API.** PostEverywhere holds its own X credentials, so scheduling to X is included in the plan price with no per-post fee. Plans start at $9/mo. [See pricing](/pricing).

## Write Pricing: Every Published Rate

These are the write operations and their published rates. Every figure comes from X's pricing documentation.

| Operation | Cost per request |
|---|---|
| Post creation | $0.015 |
| **Post containing a URL** | **$0.200** |
| Summoned post | $0.010 |
| DM and user interactions | $0.015 |
| Interaction deletion | $0.010 |
| Content management | $0.005 |
| List operations | $0.005 to $0.010 |
| Bookmarks | $0.005 |
| Privacy updates | $0.010 |
| Trends | $0.010 |

If you are writing code against the [post creation endpoint](https://docs.x.com/x-api/posts/creation-of-a-post), those first two rows are your entire cost model. Everything else is noise unless you are building a full client. For a walkthrough of the request itself, see our guide to [scheduling X posts programmatically](/blog/schedule-x-twitter-posts-api).

## The $0.20 Link Tax

A post with a URL in it costs $0.200. A post without one costs $0.015. Nothing else about the request changes.

That ratio deserves more attention than it usually gets. Most pricing roundups list it in a table and move on, which badly understates its effect on anyone doing marketing rather than engineering demos. Social media marketing is largely the business of pointing people somewhere else. Blog posts, landing pages, product launches, sign-up forms: they all carry a link. If your posting schedule is built around driving traffic, you are paying the higher rate on nearly every post you publish.

Two things follow from this.

First, the cost of publishing to X is roughly 13 times what a naive estimate based on the headline post price suggests. If you budgeted using $0.015 and your posts carry links, your actual bill will be more than an order of magnitude higher.

Second, it changes the economics of tactics that were previously free. Splitting a link out into a reply, a long-standing trick for [X algorithm](/blog/how-the-x-twitter-algorithm-works) reasons, now has a direct and measurable cost attached to the reply rather than the parent post. That does not make it wrong, but it is now a decision with a price on it rather than a free optimisation.

## What a Real Posting Schedule Costs

Here is the arithmetic for common publishing patterns, assuming a 30-day month. The middle column is the realistic case for marketing accounts, where most posts carry a link.

| Schedule | All posts carry links | Mixed (1 link post/day, rest plain) |
|---|---|---|
| 1 post/day | $6.00/mo | $6.00/mo |
| 3 posts/day | $18.00/mo | $6.90/mo |
| 5 posts/day | $30.00/mo | $7.80/mo |
| 10 posts/day | $60.00/mo | $10.05/mo |
| Agency, 10 clients at 3/day | $180.00/mo | $69.00/mo |

The mixed column shows the obvious lever. Moving from every-post-has-a-link to one-link-post-a-day cuts a three-per-day schedule from $18.00 to $6.90. Whether that trade is worth making depends entirely on whether those links were driving anything, which is a question about your analytics rather than your API bill.

For teams running many accounts, the agency row is the one to look at. At 900 link posts a month, X API fees alone come to $180. That is before hosting, before the engineering time to build and maintain the integration, and before you have posted to a single other network. A [multi-account setup](/multi-account-management) on a scheduling platform covers the same volume inside a flat subscription.

> **Running client accounts?** Scale covers 20 connected accounts across 11 networks with unlimited posts and 5 seats at $39/mo. Every plan includes a 7-day trial (card required). [Compare plans](/pricing).

## Read Pricing and the 3 Million Cap

Read operations are cheaper per call but easier to run up by accident, because a single timeline fetch can return many billable resources.

| Read operation | Cost per resource |
|---|---|
| Posts | $0.005 |
| Lists, Spaces, Communities, Notes, profile updates | $0.005 |
| Users, DM events, following/followers | $0.010 |
| Likes, mutes, blocks | $0.001 |
| Owned reads (your own data) | $0.001 |

Two details matter here. Pay-per-usage is capped at 3 million post reads per monthly billing cycle, so this model is not intended for large-scale research or firehose ingestion. And the owned-read discount at $0.001 is worth designing around: if your application only needs to see the account's own posts and engagement, routing through owned-read endpoints costs a fifth of a generic post read.

Note that several widely-shared pricing guides state the read cap as 2 million. X's own documentation says 3 million post reads per monthly billing cycle. Where third-party summaries and the official docs disagree, check [the source](https://docs.x.com/x-api/getting-started/pricing), because these figures have moved more than once.

Rate limits are separate from pricing and still apply. Credits govern what you are charged; [rate limits](https://docs.x.com/x-api/fundamentals/rate-limits) govern how fast you may call. Exceeding the latter returns errors regardless of your credit balance. Handling both cleanly is one of the harder parts of building on platform APIs directly, which is why many teams reach for [a managed publishing layer](/blog/automate-social-media-posting-api) instead.

## Ways to Publish Without Paying Per Post

If your goal is to get content onto X rather than to build an X client, there are three routes that avoid per-post billing entirely.

**Use a scheduling platform's credentials.** Tools like PostEverywhere maintain their own X application and absorb the platform fees into a subscription. You connect your account with OAuth and publish through the tool. This is the cheapest option for pure publishing, and it is the reason a $9/mo plan can cover posting volumes that would cost more than that in raw API fees. PostEverywhere's own [scheduling tool for X](/x-scheduler) works this way, as do most established tools in the category.

**Use a unified publishing API.** If you need programmatic control but not X-specific features, a [unified social media API](/social-media-api) gives you one endpoint that publishes to X alongside the other networks. You write one integration instead of eleven, and you are not exposed to per-call pricing changes on any single platform. We cover the trade-offs in detail in our guide to [social media APIs for developers](/blog/best-social-media-apis).

**Connect an assistant or agent.** If the publishing is being driven by an assistant rather than a scheduled queue, you can wire the assistant directly to a publishing layer. Our [library of assistant integrations](/connectors) covers Claude, ChatGPT, Cursor and others, and the [MCP approach](/blog/social-media-api-vs-mcp) removes the need to write an integration at all. For teams building autonomous posting systems, this is usually less work than the API route.

All three sidestep the $0.20 link charge, because the platform relationship sits with the tool rather than with you.

> **Building an agent that posts?** Wire Claude, ChatGPT or Cursor straight into publishing across 11 networks. [See the full connector list](/connectors) or read the [agent build guide](/blog/build-social-media-agent-api).

## When the X API Is Still the Right Call

Direct API access remains the correct choice in several situations, and it is worth being clear about them rather than pretending the answer is always a third-party tool.

You need X-specific features that publishing tools do not expose, such as Spaces, Communities, detailed DM handling, or bookmark management. You are building a product where X access is the product, in which case the API cost is cost of goods sold rather than overhead. You need read access to public data, which no scheduling tool provides. Or you require control over the exact request, including tuning [OAuth 2.0 flows](https://docs.x.com/resources/fundamentals/authentication/oauth-2-0/authorization-code) and error handling that a wrapper would hide from you.

For everything else, and particularly for scheduled publishing at any volume, the arithmetic above tends to favour a flat subscription. The comparison is not close once link posts are involved.

It is also worth noting that X is now an outlier in charging for write access at all. [TikTok's Content Posting API](https://developers.tiktok.com/doc/content-posting-api-get-started) and [LinkedIn's marketing APIs](https://developer.linkedin.com/product-catalog) do not bill per post, though both gate access behind approval processes with their own friction. If you are planning to [publish the same content across several networks](/cross-posting), X will usually be the only line item with a per-call charge attached, which is worth factoring into where you build first. Our [comparison of publishing tools](/blog/best-cross-posting-tools) goes through the options.

## FAQ: X API Pricing

### How much does the X API cost in 2026?

X API pricing is pay-per-usage with no monthly subscription. You buy credits upfront and each call deducts from the balance. Creating a post costs $0.015, creating a post containing a link costs $0.200, and reading a post costs $0.005 per resource with a cap of 3 million post reads per monthly billing cycle.

### Why does a post with a link cost more?

X charges $0.200 for a post containing a URL against $0.015 for a post without one, a difference of roughly 13 times. X has not published a detailed rationale in its pricing documentation. In practical terms it means marketing accounts, which nearly always post links, pay substantially more than the headline post price suggests.

### Is there still a free X API tier?

No. The current documented model requires purchasing credits before making calls, and there is no free allowance published in the pricing documentation. Small workloads are inexpensive rather than free, since a handful of plain posts costs a few cents.

### What happened to the Basic and Pro monthly plans?

X replaced fixed monthly access tiers with the credit model described in its current pricing documentation, which states there are no subscriptions and no minimum spend. If you hold legacy access, check your developer console directly, because migration timelines have shifted and third-party summaries of them have often been out of date.

### How do I estimate my monthly X API bill?

Count the posts you intend to publish, split them into link-bearing and plain, then multiply by $0.200 and $0.015 respectively. Add read costs if your application fetches data, remembering that reads are deduplicated within a 24-hour UTC window. Monitor actual usage in the developer console during the first billing cycle, as fan-out and retries commonly push real usage above estimates.

### Can I post to X without paying per post?

Yes. Scheduling platforms hold their own X application credentials and include publishing in a flat subscription, so no per-post fee reaches you. PostEverywhere plans start at $9/mo with unlimited posts, and every plan includes a 7-day trial with a card required. This is normally cheaper than direct API access for publishing-only workloads.

### Do rate limits still apply under pay-per-usage?

Yes. Credits and rate limits are separate systems. Credits determine what you are charged, while rate limits determine how frequently you may call an endpoint. Exceeding a rate limit returns an error regardless of how much credit you hold.

### Is the X API cheaper than a scheduling tool?

For very low volumes, yes. Ten plain posts a month costs $0.15 in API fees. Once posts carry links the position reverses quickly: 45 link posts a month costs $9.00, which already exceeds an entry-level scheduling subscription that also covers 10 other networks. Compare against our [published plan prices](/pricing) using your own posting volume.