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

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 and X usage and billing, 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.

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.