TwitterAPIs

TwitterAPIs is a pay-as-you-go Twitter/X API with 113 REST endpoints, flat $0.0008 per call returning about 20 tweets, bearer-token auth, and an MCP server for Claude and Cursor. No subscription or X developer account is needed.

TwitterAPIs is a hosted API that gives developers programmatic access to public X (formerly Twitter) data without applying for an official developer account. Authentication is a single bearer token, and every endpoint returns structured JSON. The service exposes 113 endpoints, split into 69 reads and 44 writes, covering tweets, advanced search, user profiles, threads, timelines, and follower and following lists. Billing is purely per call. A read costs $0.0008 and returns roughly 20 tweets, which works out to about $0.04 per 1,000 tweets. Simple writes cost the same, and creating a tweet is priced at double. There are no monthly minimums, seats, or tiers, and a month with no calls costs nothing. New accounts receive $0.50 in free credits without a card, enough for around 625 calls. The site is candid about tradeoffs: empty responses still count as billed calls, and there is no volume discount. In practice, a developer signs up, copies a key from the dashboard, and calls endpoints with curl, Python, Node.js, or any HTTP client. A Python package, an npm package, an OpenAPI 3.1 spec for import into Postman, and interactive docs are available. A first-party MCP server, started with one npx command, lets Claude, Cursor, and Windsurf pull tweets and profiles directly from prompts. Most reads use public data only. Private reads and writes rely on an X session the user registers, stored encrypted, or passed per request and never stored. A flat limit of 600 requests per minute and 20 concurrent requests applies per key. Among alternatives, it sits between the official X API, which bills per resource read and offers contractual guarantees on provenance and deletion, and self-built scraping stacks that demand proxies and ongoing maintenance. It suits prototypes, monitoring, research pipelines, and AI agents that need cheap, high-volume access, while regulated use cases may still require the official route.