X replaced fixed monthly tiers with pay-per-use credits in early 2026. Reading posts costs $0.005 each. Pulling trending topics through the official API still requires credits and developer onboarding. This page isolates what X API access actually costs when the goal is trend data, not tweet archives.
X overhauled developer pricing in February 2026. Fixed monthly plans are legacy-only for existing accounts. New signups buy credits upfront and pay per API call. For trend research, the distinction matters: reading thousands of individual posts to infer what is trending costs far more than pulling a pre-aggregated trending topics feed.
For the broader multi-vendor picture, see the trend data API pricing comparison. For live X trending topics without X credentials, see the X trending topics API.
Price: No monthly fee. Credits purchased upfront in the X Developer Console.
Model: Consumption-based. Each endpoint deducts credits at a published per-resource rate.
Published rates (verify in console before building):
| Action | Approximate cost |
|---|---|
| Read a post | $0.005 per post |
| Read owned post | $0.001 per post |
| Read user profile | $0.010 per user |
| Create a post | $0.010 to $0.015 per post |
| Create post with link | Higher (published as ~$0.20 in some docs) |
Deduplication: Requesting the same resource twice within a 24-hour UTC window incurs one charge.
Monthly cap: Pay-per-use accounts face a 2 million post-read cap per month. Above that threshold, X requires an Enterprise contract.
What you get: Full API access to posts, users, direct messages, filtered streams, and trends endpoints. Real-time and historical tweet data depending on endpoint.
Hidden costs: Volume math. Monitoring 50 trending topics by pulling recent posts for each (say 100 posts per topic daily) runs 150,000 reads per month at $0.005 each, roughly $750 before any user lookups or writes. Trend inference built on raw tweet reads scales linearly with post volume.
Verdict: Right model for apps that post, reply, or analyze specific accounts. Expensive for broad trend monitoring built on per-post reads.
Price: $200/month.
Model: Fixed monthly subscription. Not offered to new signups as of 2026.
What you get: A fixed monthly post-read allowance (tier details vary by account age). Write access included. Suitable for small bots and posting tools.
Hidden costs: Only available if the account already subscribed. New projects cannot enroll. Read limits still apply; exceeding them requires upgrading or switching to pay-per-use.
Verdict: Good value for legacy accounts with modest, predictable volume. Not an option for new trend-monitoring pipelines.
Price: $5,000/month.
Model: Fixed monthly subscription for high-volume existing accounts.
What you get: Higher read and write limits, filtered stream access, and support suitable for data-heavy products.
Hidden costs: Same legacy-only restriction. $5,000/month is the floor before Enterprise for teams that outgrew Basic.
Verdict: Appropriate for companies whose product depends on high-volume X data. Overkill when the requirement is a daily trending topics snapshot.
Price: Negotiated. Public estimates place entry around $42,000 to $50,000 per month.
Model: Annual or multi-year contract with custom rate limits, dedicated support, and team management.
What you get: Volume above the 2 million monthly pay-per-use read cap, filtered streams at scale, compliance features, and negotiated endpoint pricing.
Hidden costs: Sales cycle, legal review, and annual commitment. No self-serve signup.
Verdict: Required for large-scale social listening platforms and enterprise media monitoring. Disproportionate for a single trending-topics dashboard.
Price: 100 requests per month free (see pricing). Paid plans from $19/month for 1,000 requests.
Model: Subscription with monthly request allocation. No X developer account required.
What you get: Live X trending topics as ranked JSON via get_top_trends. No per-post metering. Cross-platform growth and search data (Google, TikTok, Reddit, news) in the same API for context on whether an X trend is building or spiking.
Example request:
{
"mode": "top_trends",
"type": "X (Twitter) Trending",
"limit": 25
}
Response shape (snapshot June 23, 2026): Ranked topic names such as sports and news terms returned as [rank, name] pairs with an as_of_ts timestamp.
Limitation: Live trending feed only. No historical X mention volume, no individual tweet text, no user timelines. For those, the official X API (or an enterprise social listening vendor) is the path.
Verdict: Lowest cost when the workflow needs "what is trending on X right now" rather than tweet-level archives. Pairs naturally with Google Search growth checks on the same topic.
| Workflow | X API (pay-per-use) | Trends MCP |
|---|---|---|
| Daily trending topics list (1 call/day) | Trends endpoint still consumes credits; cost depends on endpoint pricing in console | ~30 requests/month on free tier |
| Pull 500 posts/day for sentiment | ~500 × $0.005 × 30 ≈ $75/month minimum | Not available (no tweet text) |
| Monitor 20 topics × 50 posts each daily | ~30,000 reads/month ≈ $150/month | Use trending feed + Google/TikTok growth: ~60 requests/month |
| Full social listening suite | Enterprise ($42k+/month) or Pro legacy ($5k/month) | Partial coverage: trends + cross-platform growth, not tweet archives |
Official X API: Building posting tools, reply bots, account analytics, or products that need tweet text, user objects, or filtered streams.
Trends MCP X trending feed: AI agents, dashboards, and research workflows that need the current X trending topics list as structured JSON without X developer onboarding.
Enterprise social listening (Meltwater, Brandwatch): Full mention archives, sentiment, and crisis monitoring across X and other networks. See social listening API pricing for contract ranges.
The pay-per-use shift lowered the entry barrier for light usage but made high-volume read pipelines more unpredictable. Teams that only need trending topic names should not model costs around per-post reads.
FAQ