TwitterXAPI and the official X API
Reading 1,000 posts costs $0.10 here and $5.00 on official pay-per-use, with no fixed monthly cap.
Side-by-side comparison
| TwitterXAPI | Official X API | |
|---|---|---|
| Cost per 1,000 posts read | $0.10 | $5.00 ($0.005 per Post read) |
| Cost per 1,000 follower or user records | $0.01 for followers and following | $10.00 ($0.01 per user read) |
| Monthly read cap | No fixed cap; limited by your balance | 2 million Post reads on pay-per-use |
| Getting access | Sign in with Google; the key is in your dashboard | X developer account and app |
| Write actions (post, like, follow, DM) | Not available | Available |
| Private data with user consent | Not available | Available |
| Response formats | Raw, Moderate or Contentful JSON | X API v2 objects |
| AI agent access | Built-in MCP server | Build your own integration |
| Relationship with X | Independent third-party service | Operated by X |
Official figures from X's pricing documentation, checked September 3, 2026. Pricing guide
Choose TwitterXAPI when
- You read public profiles, posts, replies, followers or search results.
- Volume matters more than per-request latency.
- You want an agent to read X data over MCP.
Choose the official API when
- You need to post, like, follow or send messages.
- You need private data with a user's consent.
- You need a direct agreement with X.