Migrate a Twitter/X API integration from legacy subscription tiers to pay-per-use pricing
domain: developer.x.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the legacy tier structure (Free, Basic $100/mo, Pro $5,000/mo, Enterprise) documented at developer.x.com/en/support/x-api/developer-account1
Confirm that as of February 6, 2026 X launched credit-based pay-per-usage pricing per docs.x.com/x-api/getting-started/pricing, replacing new signups for Basic/Pro subscriptions
Instrument the GET /2/usage/tweets endpoint to monitor consumption under the new per-request billing model
Reprice your integration's expected cost using the documented per-endpoint rates (e.g., Post: Read and Post: Create pricing) rather than assuming a flat monthly tier cost
Confirm whether your account was auto-migrated from a legacy subscription to pay-per-use, and audit billing after the transition
Known gotchas
New developer signups can no longer choose Basic/Pro tiers — only pay-per-use or Enterprise are available going forward
Published per-request pricing is explicitly "subject to change" — don't hardcode dollar amounts into cost-estimation logic
The exact date legacy subscribers were force-migrated to pay-per-use is reported in secondary sources but not confirmed on an official page — verify current billing status directly in your developer portal
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?