X API Pricing in 2026: Current Rates and Verified Facts

The current official X API pricing page lists prepaid pay-per-use access and custom Enterprise access. Standard Post reads cost $0.005 per resource, standard Post create requests cost $0.015, and Post create requests containing a URL cost $0.200.

TL;DR: These prices were verified against the official X API pricing page on August 16, 2026. That verification date does not prove when the prices became effective. The page does not provide a July or August 2026 change date, a complete legacy-plan migration history, or a fixed Enterprise minimum. This guide separates what the source confirms from what it does not.

That distinction matters. A current price table can establish today's listed prices. It cannot, by itself, establish that a price changed on a particular earlier date or that every existing account moved at the same time.

Current Official X API Read Prices

The following values come from the current official table.

The unit matters. X bills by resource, not simply by HTTP request. A response containing multiple billable resources can therefore cost more than its request count suggests.

The table also describes a 24-hour deduplication period. Re-reading the same resource during that period is not charged again under the stated rule, and the period resets at midnight UTC.

Current Official X API Write Prices

Write operations do not share one universal price.

This is why the shorthand claim that "X writes cost $0.010" is stale. A standard Post create is $0.015 in the current table, while a Post containing a URL is $0.200 and several other actions have separate prices.

The Owned-Read Rule

The current table lists owned reads at $0.001. The official condition is narrow: the authenticated user ID must be the same as the app owner's user ID.

Do not generalize that rate to every account an agency manages, every brand owned by the same company, or any arbitrary resource returned while using user authentication. If the identity condition is not met, use the standard resource price in cost estimates.

The Monthly Post-Read Cap

The current pay-per-use table lists a monthly cap of 3,000,000 Post reads. This is separate from endpoint rate limits and separate from the 24-hour deduplication rule.

Above the self-serve cap, the public pricing page points to Enterprise access. Enterprise is listed as custom pricing. The page does not publish a fixed $42,000 monthly minimum, so budgets above the cap should use an actual X sales quote rather than a third-party estimate presented as an official fact.

What the Current Page Does Not Prove

The official table is strong evidence for current listed values, but it does not establish all of the history often repeated in 2026 API articles.

It does not establish:

1. That pay-per-use first began in February 2026.
2. That every Basic or Pro account closed or migrated on one date.
3. That every legacy subscriber received the same voucher or switch-back option.
4. That the current rates became effective in April, July, or August 2026.
5. That Enterprise starts at a fixed public monthly price.

An archived version of the official documentation already showed pay-per-use on January 22, 2026. That makes a blanket "introduced in February" claim unsafe. Historical plan details should be attached to a dated primary announcement or archived page for the period being discussed.

The official page's metadata was last modified on August 13, 2026, and this article verified the page on August 16. Neither date is an effective date for the rate card.

Cost Examples at Current Rates

For 100,000 standard Post reads with no deduplication benefit:

The GetXAPI estimate assumes about 20 tweets returned per standard search or list call. Real cost depends on endpoint, result count, pagination, and whether a specially priced endpoint is used.

For 1,000 standard Post create requests on the official X API, the current listed price is $15. For 1,000 Post create requests containing a URL, the current listed price is $200. Those are current-rate calculations, not claims about a prior price or the date of a change.

GetXAPI Pricing and Plan Facts

GetXAPI remains pay-per-call by default:

Optional plans are also available: Starter at $5 one time, Pro at $15 per month, Growth at $49 per month, and Scale at $99 per month. Plan credits follow each plan's stated validity rules, while purchased top-up credits do not expire.

How to Keep Pricing Content Accurate

For any integration or comparison page, store four fields with an external price: the value, the official source, the date you verified it, and the effective date only when an official dated source provides one.

When the effective date is unknown, keep it unknown. A page update timestamp is useful for freshness checks but should not be converted into a pricing-change date.

For account-specific access, check the X Developer Console. A public table can describe the current offer, but a console or contract may show legacy or negotiated terms that do not appear on the public page.

The Verdict

The source-safe summary is simple: X currently lists prepaid pay-per-use and custom Enterprise access; standard Post reads are $0.005; standard Post create requests are $0.015; Post create requests with a URL are $0.200; owned reads are $0.001 under a specific identity condition; and pay-per-use access has a 3-million monthly Post-read cap.

There is no reliable basis on the current page for calling these July or August 2026 prices, assigning them an April 20 effective date, promising how legacy accounts were handled, or quoting a fixed Enterprise floor.

For public-data workloads, compare the official per-resource calculation with GetXAPI's current pricing, then test the required endpoint using the $0.10 signup credit before choosing a production path.