![X API gateway showing the different costs of text posts and link posts](/editorial/x-api-costs-cover.webp)Blog

# X API request pricing: what the public table does and does not tell you

X lists rates for successful API operations. Learn what its Content Create prices cover—and why they are not a Naasher customer-cost calculator.

Last updated August 28, 2026 · 3 min read · The Naasher team · [Editorial and corrections policy (Arabic)](/editorial-policy) · [اقرأ بالعربية](/blog/x-api-costs)

Share[Share on X](https://twitter.com/intent/tweet?text=X%20API%20request%20pricing%3A%20what%20the%20public%20table%20does%20and%20does%20not%20tell%20you&url=https%3A%2F%2Fnaasher.com%2Fen%2Fblog%2Fx-api-costs)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fnaasher.com%2Fen%2Fblog%2Fx-api-costs)[Share on WhatsApp](https://wa.me/?text=X%20API%20request%20pricing%3A%20what%20the%20public%20table%20does%20and%20does%20not%20tell%20you%20https%3A%2F%2Fnaasher.com%2Fen%2Fblog%2Fx-api-costs)

**In short:** X charges its developer customers for API operations. The public table is useful for understanding provider cost, but it is not a customer invoice and it cannot be turned into a Naasher calculator without a separate, approved billing behavior matrix.

## What X's official table says

X says write operations are charged per request and failed requests are not billed. Its current public table lists:

__Selected X API pay-per-use rates__
| Operation                           | Published unit                   | Published rate       |
| ----------------------------------- | -------------------------------- | -------------------- |
| OperationContent: Create            | Published unitSuccessful request | Published rate$0.015 |
| OperationContent: Create (with URL) | Published unitSuccessful request | Published rate$0.200 |
| OperationAnalytics: Read            | Published unitResource returned  | Published rate$0.005 |

Primary source: [X API pay-per-use pricing](https://docs.x.com/x-api/getting-started/pricing) and [X usage and billing](https://docs.x.com/x-api/fundamentals/post-cap), checked 28 August 2026\. X can change rates; verify the live table and Developer Console before budgeting.

The unit matters. X describes a successful API request, not a marketing calendar item, a campaign, or a customer credit. Its public table also does not explain every URL-classification edge case or every additional operation a publishing flow may perform.

## Why a thread is not one create request

Naasher's X integration sends stored thread parts sequentially. It creates the first part, then uses the returned X identifier in the next request's `in_reply_to_tweet_id`, repeating that process for the remaining parts. A follow-up reply is also sent through a separate create request.

This establishes the reply relationship when the run succeeds. It does not make the sequence atomic: if a later part fails, earlier parts may already be public. An uncertain provider response also cannot safely be treated as either success or failure without checking X.

## What this page deliberately does not calculate

Naasher's current runtime holds one metered usage record per X channel target and settles it after the provider reports success. That internal target-level meter is not the same thing as X's per-request invoice, especially for a multi-part thread or a separate follow-up reply.

Not a Naasher billing calculator

Do not use the rates above to infer what Naasher will charge for thread parts, follow-up replies, retries after failure, URL-bearing posts, prepaid-credit holds or releases, annual-plan overages, or checkout-provider reconciliation. These rules require a confirmed behavior matrix, matching checkout products and prices, formula tests, and product/billing approval before a calculator can be published.

For purchasing, use the live Naasher pricing and checkout terms presented to your account. Before a high-volume X campaign, ask support to confirm how the exact content shape will be counted. For the publishing and recovery behavior, read the [X scheduling guide](/en/guides/x).

## Test the workflow with your real accounts

Start free, then compare the composer, calendar, and channel limits with what your team actually needs before choosing a plan.

[Start free](https://app.naasher.com/sign-up)[Review pricing in Arabic](/pricing)

## Frequently asked questions

What does X currently charge for a create request?

X's public table lists Content Create at $0.015 per successful request and Content Create with a URL at $0.200 per successful request. Check the live table because X can change its rates.

Is one scheduled thread one X request?

No. Each thread part is created separately, and each part after the first is a reply request. A partial failure can leave earlier parts live.

Can I use the X rate table to calculate my Naasher bill?

No. X's rates describe charges to the developer app. They do not define Naasher's customer units for threads, replies, retries, URLs, credits, or annual-plan overages.

## Read next

[![A connected sequence of short posts arranged on a publishing calendar](/editorial/schedule-x-cover.webp)GuidesXthreadsHow to schedule posts and threads on X in 2026Schedule X posts, understand how successful thread runs are chained, and verify partial or uncertain outcomes before retrying.August 28, 2026·3 min read](/en/guides/x)

[![Gulf social media calendar mapping test slots above the Riyadh skyline](/editorial/best-posting-times-saudi-cover.webp)BlogPosting timesSaudi ArabiaHow to find your best posting time in Saudi ArabiaA practical Gulf posting-time test that replaces generic charts with account data, clean comparisons, and a separate plan for Ramadan.August 15, 2026·9 min read](/en/blog/best-posting-times-saudi)

---

Canonical URL: https://naasher.com/en/blog/x-api-costs