Twitter API Pricing 2026

2026 X API at a glance

X API Pricing at a Glance

X API pricing in 2026 is pay-per-use. The old Free, Basic, and Pro monthly subscriptions are gone for new customers — you now buy credits upfront, each endpoint call deducts from that balance, repeated reads of the same resource are deduped within a 24-hour UTC window, and live usage is visible in the Developer Console. Enterprise remains a separate, custom-priced tier for volumes above the pay-per-use caps. X public docs also call out owned reads at $0.001 per resource and a 2M monthly Post-read cap on pay-per-use plans.

Important: X now tells developers to view current per-endpoint rates in the Developer Console because rates can vary by endpoint type, operation, and data scope. Treat any copied public rate card as a snapshot, not as the source of truth. Use the math below as a planning model, then replace the rate with the value shown in your own console before committing architecture.

What X Publishes Publicly vs What Lives in Developer Console

For May 2026 planning, these are the public pricing facts we can verify from X docs without logging into your developer console:

This is the main buyer gotcha: public docs explain the model, but your account console is the only current source for endpoint-level rates. The planning question is not only price per request; it is how many unique Posts your monitored accounts produce, how much dedupe helps, whether you hit the 2M cap, and how much infrastructure you need to run the stream reliably.

Operational Limits That Cap Throughput

Pay-per-use changes billing, but every endpoint still has rate limits, connection caps, and usage caps that bound real throughput:

• Filtered stream: 1 concurrent connection, 1,000 rules per project, 1,024-character rule length
• Sampled stream: 1 concurrent connection, ~1% sample of public posts
• Filtered stream latency and delivery behavior should be measured in your own workload before relying on it for trading alerts
• Search and lookup endpoints: per-15-minute caps still apply per endpoint
• Write and URL-bearing write costs should be checked in Developer Console before bulk posting
• No backfill on streams — disconnects lose data unless you have an out-of-band recovery path

Hit a rate limit and you receive a 429 with an x-rate-limit-reset header. Build exponential backoff and idempotency from day one. The 1-connection filtered-stream cap is the binding constraint for serious real-time work — Enterprise (25,000+ rules, multiple concurrent connections, contact sales) is the only way to run multiple parallel streams.

Filtered Stream on Pay-Per-Use: One Connection, Metered Delivered Posts

Filtered stream is available on pay-per-use. Register rules, open a long-lived HTTP connection, and X pushes matching Posts as newline-delimited JSON. Each unique delivered Post counts toward usage, with public docs noting daily dedupe and a 2M monthly Post-read cap on pay-per-use plans.

X's stream is HTTP chunked transfer (not WebSocket). Your client handles the long-lived connection, parses newline-delimited JSON, manages reconnects with exponential backoff, and watches for the keep-alive newlines X sends roughly every 20 seconds to detect stalled connections.

For trading alerts, the practical question is not just X API access; it is delivery timing, reconnect behavior, what signals you actually receive, enrichment, and operational burden. If you need push delivery for deletes, pins, profile/follow moves, and token/OCR/price context, a managed WebSocket service can be simpler to operate than building on raw stream events.

The latency reality

Pay-per-use X API is not a 170ms median monitored-account alert path. The fast lane starts around $42k/mo.

X's fastest publicly priced stream is the Filtered Stream, which X's own documentation reports at approximately 6-7 seconds P99 latency. TweetStream's published speed metric is 170ms median server detection, before you write reconnect, dedupe, OCR, or $ticker code.

X does sell a faster stream — PowerStream — which their docs describe as their "lowest-latency streaming API." But X publishes it as a "premium offering available under select Enterprise plans," with no list price, no published latency number, and access gated behind a sales contract. Third-party reporting puts X's Enterprise tier starting price around $42k/mo. TweetStream's flat $199/mo Basic plan provides WebSocket alerts with 170ms median server detection.

What Pay-Per-Use Actually Costs at Your Volume

Total cost depends on your Developer Console rates and unique delivered-resource volume. The examples below show the planning model for monitored-account reads; replace the assumed Post-read rate with your current console rate before budgeting:

Twitter API Cost Calculator

X charges $0.005 per delivered Post on pay-per-use plans. Adjust accounts and Posts/day to compare metered X cost against TweetStream's flat price.

Flat-Rate Alternative for Monitored-Account Workloads

If you reached this page sizing the X API for tweet alerts, model unique delivered Posts first. Tracking 50 accounts at roughly 200 Posts/day each is ~300,000 reads/month before dedupe. At an example $0.005 delivered-Post rate that is about $1,500/mo in API reads alone, before you build the stream client, reconnect logic, storage, enrichment, and alert routing.

TweetStream reports 170ms median server detection for monitored-account events, measured from production database event timestamps, then delivers WebSocket alerts for posts, updates, deletes, pins, profile changes, follows, and unfollows with token detection, OCR on attached images, and live crypto prices for $199/month flat (Basic, 50 accounts) or $499/month (Elite, 250 accounts plus Discord webhook delivery). For monitored-account alerts specifically, that can be materially cheaper than metered usage once volume grows, while also removing the stream infrastructure work.

Build it faster with TweetStream

This guide explains the workflow, but production teams should not rebuild tweet ingestion, reconnects, token detection, OCR, and downstream delivery from scratch. TweetStream is the better production starting point: posts, updates, deletes, pins, profile changes, follows, unfollows, enriched JSON payloads, history on supported plans, and a 3-day trial you can test against your own accounts.

Frequently Asked Questions

Sources

• X API pricing (developer.x.com)
• X API usage and billing
• X API documentation
• Filtered stream rate limits

TweetStream Team

Last verified: May 2026