Blog/
What Does the X/Twitter API Cost in 2026?
Compare official X API pay-per-use and Pro streaming (~$5k/mo) with third-party proxies and XFlux flat plans from free/$19 — including account monitors and webhooks.
Official X API: pay-per-use and high tiers
X’s developer API is the source of truth when you need write access, OAuth on behalf of users, or enterprise-grade streaming. Pricing and packaging change; as of 2026 the practical story for many teams is still: Basic or pay-per-use for light reads, then a steep jump for realtime products.
Filtered / Pro-style streaming is commonly cited around $5,000/month. That is the right product if you need firehose-scale rules across the whole network. It is the wrong product if you only care when a short list of @handles posts.
Always verify current numbers on docs.x.com — treat any third-party comparison (including this one) as directional.
Third-party read APIs: volume vs workflow
Several third-party APIs sell cheaper public reads with pay-as-you-go metering. They win when your workload is pure lookup volume: millions of profile or search calls and nothing else.
Where they usually stop is product surface area: you still build your own poller, signature scheme, dashboard, and agent tooling. If “watch these accounts and push signed JSON” is half the job, raw PPU endpoints alone are incomplete.
XFlux: flat plans, monitors, and webhooks
XFlux is a read-focused X/Twitter API with scheduled account monitors in the same account. Free tier: 1,000 API calls/month, 1 monitor, Dashboard hit history — no credit card. Starter starts at $19/mo with 150K calls, 3 monitors, signed HTTP webhooks, and 1-second minimum poll interval.
Higher tiers (Growth $49, Pro $99, Scale $249) raise quotas and monitor counts. Polling for monitors does not consume your REST API quota. Live webhook delivery on new hits requires Starter+; Free can still configure URLs and send test pings.
You also get MCP (@xflux/xflux-mcp-server) for Claude/Cursor, Smart Money predictors, and live signal digests — tooling that PPU proxies rarely bundle.
# Quick cost intuition (directional)
# Official Pro filtered stream: ~$5,000/mo for network-wide rules
# XFlux Starter monitors: $19/mo for accounts you pick + webhooks
# XFlux Free: $0 — 1k calls + 1 monitor (Dashboard history)When to pick which
Pick official X when you must post, DM, or run enterprise streams with X’s own SLAs. Pick a high-volume PPU proxy when you only need bulk public lookups and already own the alert stack.
Pick XFlux when you want flat monthly predictability, account-level monitors with HMAC-signed webhooks, Make.com routing, and an MCP server — without paying for a $5k stream you will not use.
Worked example: three accounts for trading alerts
Suppose you watch three macro/flow handles and only want webhook alerts when they post. DIY against official Basic means polling timelines yourself (quota + infra). Official streaming means Pro pricing for a use case that only needs three authors.
On XFlux Starter you create three monitors, optional keyword filters, paste a Make.com or server URL, and verify HMAC. Same account also covers on-demand search and profile lookups for your bot or agent.
FAQ
- Is XFlux cheaper than the official X API?
- For read + account alerts, usually yes: Free or $19/mo Starter vs Basic/PPU friction or ~$5k streaming. For write/OAuth/enterprise firehose, use official X — XFlux does not replace those.
- Does XFlux charge per tweet?
- No. Plans are flat monthly quotas for REST calls, plus a fixed number of account monitors. Monitor polling does not burn API call quota.
- Do I need the $5,000/mo stream for trading alerts?
- Only if you need network-wide filtered streaming. Watching specific accounts is what XFlux monitors are for — from $19/mo with signed webhooks on Starter+.
- Where can I see current XFlux prices?
- See /pricing and /docs/compare/pricing. Official X prices should be confirmed on docs.x.com.
Build with XFlux
Free tier for reads and one monitor. Starter from $19/mo for signed webhooks and faster polling.