# TwitterAPIs: Cheapest Pay-As-You-Go Twitter API Canonical: https://www.twitterapis.com Description: TwitterAPIs is the cheapest pay-as-you-go Twitter and X API. $0.0008 per call returns ~20 tweets ($0.04/1,000). No subscription, no X developer account. Generated: 2026-09-15T19:40:49.896Z --- [Shipped GET /feedback lists every report your account has filed. 109 endpoints now, and counting ](/changelog) # The agent-ready Twitter / X API. One hosted key or MCP server for Claude and Cursor. Every endpoint $0.0008 per call. Returns ~20 tweets per call, just $0.04 per 1,000 tweets. No subscriptions, no developer account needed. [Start for free](/signup)[View pricing](/pricing) $0.0008 per call, every endpoint. STANDARD $0.04/1K tweets, 20 per call. VALUE $0.50 free credits at signup. NO CARD 109 endpoints: 65 reads, 44 writes. COVERAGE What is TwitterAPIs? TwitterAPIs is a pay-per-call Twitter and X API. Each read call costs $0.0008 and returns about 20 tweets ($0.04 per 1,000). There are no subscriptions, no monthly minimums, and no X developer account required. New accounts get $0.50 in free credits, roughly 625 API calls, with no credit card. We priced every read call at a flat $0.0008 (source: our published pricing), about 20 tweets each, so 1,000 tweets cost $0.04, versus the $5 to $10 the official X API charges for the same reads. Endpoints ## 109 endpoints. One bearer token. No developer account. 65 read endpoints and 44 write endpoints covering tweets, users, threads, timelines, and follower graphs. All at $0.0008 per call with JSON responses and standard HTTP auth. ┌──────────┐ │ query\_ │ ├──────────┤ │ ░░░░░░░░ │ └──────────┘ ### Advanced Tweet Search Search by keyword, hashtag, user mention, date range, and more. The same advanced operators you use on X.com. ◉ ┌─────┐ │░░░░░│ └─────┘ ### User Profiles Fetch full user info: bio, follower count, following, tweet count, and verified status by handle or ID. ┌─┐ │ │►── └┬┘ │►── ┌▼┐ │ │ └─┘ ### Thread Lookup Expand any tweet into a full conversation thread. Great for AI summarisation, research, and content analysis. │▄ █ ▄ █ │█ █ █ █ │█ █ █ █ └──────── ### Timeline Access Retrieve any user's recent tweets and replies. Paginate through history without hitting X's rate limits. ◉─◉─◉ │ │ │ └─┼─┘ ◉ │ ### Follower Graph List followers and following for any public account. Build social graphs, find influencers, map communities. \[AI\] ──► API ──► \[you\] ### MCP Server Plug twitterapis.com into Claude, Cursor, or any MCP-compatible AI agent. Fetch Twitter data from your prompts. Quickstart ## Three steps to your first tweet. 01 ### Sign up and get your key Create a free account and get $0.50 in credits instantly. No credit card required. Copy your API key from the dashboard. 02 ### Make your first API call Hit any endpoint with Bearer auth. Standard REST, works with curl, Python, Node.js, or any HTTP client. 03 ### Get structured tweet data Every call returns clean JSON. Tweets, user profiles, follower graphs, and threads, all in a consistent schema. terminal ``` # Sign up at twitterapis.com/signup # Then grab your key from Settings export TWITTERAPIS_KEY="twitterapis-your_api_key_here" echo $TWITTERAPIS_KEY ``` Ready Reliability ## One ceiling. No tiers. Just data. A managed API that returns clean, structured Twitter data on demand. No official X developer app, no API tiers, no quota resets. One flat ceiling of 600 requests a minute per key, and you only pay for the calls you make. ⚡ ### 600 requests a minute per key One flat ceiling of 600 requests per minute and 20 concurrent per key. No per-endpoint quotas, no tier gates, no monthly plan. 🔄 ### Automatic failover Built-in redundancy and automatic retries keep your data flowing, even under heavy load. 🌐 ### No X developer account Skip the official X developer application, approval queue, and app credentials. Sign up and call the API in minutes. 99.9% Uptime 109 Endpoints (65 reads + 44 writes) JSON Structured responses 0 Rate limits imposed // Service status ✓ Uptime: 99.9% target ✓ Failover: automatic ✓ Auth: bearer token ✓ No X developer account required Pricing ## The numbers speak for themselves. All systems operational $0.0008 per call every endpoint, standard $0.04/1K per 1,000 tweets ~20 tweets per call $0.50 free credits no credit card needed 109 API endpoints tweets, users, threads, search Example API calls t+0ms GET /twitter/tweet/advanced\_search us-east-1 200 41ms t+41ms GET /twitter/user/info eu-west-1 200 29ms t+70ms GET /twitter/user/followers ap-south-1 200 67ms t+137ms GET /twitter/tweet/thread us-west-2 200 38ms Build with ## Works with your stack. Instantly. Standard REST + JSON means twitterapis.com slots into any language or framework. Plus a first-party MCP server and an OpenAPI 3.1 spec you can import straight into Postman. >>> ... Python Language -> \[JS\] --- Node.js Language -> curl ──── cURL CLI -> \[AI\] ─── Claude MCP AI Agent -> { } ─── Cursor AI IDE -> GET ──► Postman API Client -> 📄 ─── OpenAPI Interactive Docs -> ### Wire it into your agent over plain REST. Every endpoint is one HTTP GET with a Bearer key, so your AI can fetch tweets, users, and threads directly from your prompts today. A native MCP server for Claude, Cursor, and Windsurf is already live, 109 tools, one npx command. [View Docs](https://docs.twitterapis.com) // One call, Bearer auth curl https://api.twitterapis.com/twitter/tweet/advanced\_search \-H "Authorization: Bearer $TWITTERAPIS\_KEY" // MCP server for Claude and Cursor // live: npx -y @twitterapis/mcp@latest Privacy ## Your credentials stay yours. We never take your X password. Most reads need no login at all, and a session you pass per request is never stored. We keep it simple so you can check it. ╔═══╗ ║ ✕ ║ ╚═══╝ ### We never take your X password We never ask for or store your Twitter/X login or password. Public reads need only your twitterapis.com API key. ┌───┐ │ -> │ └───┘ ### Most reads need no login Most of the 65 read endpoints touch only public data with no credentials. Private reads and write actions use an X session you register, stored encrypted at rest with AES-256-GCM until you replace it, or one you pass per request, which is never stored. ╭───╮ │ 🔒│ ╰───╯ ### HTTPS encryption All API traffic travels over TLS 1.3. Your API key is transmitted only in encrypted request headers. \[===\] \[tok\] ### Bearer token auth Simple revocable bearer tokens. Lost or leaked? Generate a new key from your dashboard instantly. ◉─◉ │pub│ ### Public data by default Reads touch publicly visible tweets and profiles. Anything beyond that needs an X session you register yourself, and reaches only what that account can already see. ▪ ✕ ▪ ───── ### No data resale We never sell, share, or train models on your request data, and we keep no tweet content and no browsing history. 🔒 #### What we store We store your email address, hashed password (if applicable), per-call usage logs for billing, and, if you register one, your X session encrypted at rest until you replace it. That is all. No tweet content and no browsing data. Read our [Privacy Policy ->](/privacy-and-data-handling) For developers ## Integrate in under 5 minutes. One endpoint, one header. Fetch tweets, users, and threads from any language. No OAuth dance, no rate-limit math, no developer account required. ### No X developer account Use twitterapis.com without managing official X developer app credentials or waiting for approval. ### Per-call pricing Pay only for what you use. No monthly minimums. $0.50 free credits to start, no card required. ### Standard REST / JSON Plain HTTP GET requests, JSON responses. Works with any language, framework, or AI agent. ### SDK + OpenAPI + MCP Python package, npm package, OpenAPI 3.1 spec, interactive docs, and an MCP server for AI agents. cURLPythonNode.js ``` export KEY="twitterapis-your_api_key_here" curl -s \ -H "Authorization: Bearer $KEY" \ "https://api.twitterapis.com/twitter/tweet/advanced_search?query=openai%20filter:verified&limit=20" \ | jq '.tweets[].text' ``` $ pip install twitterapis-python MCP server: npx -y @twitterapis/mcp@latest [Read the docs](https://docs.twitterapis.com) ## Frequently asked questions What the API returns, what it costs, and what we do with your data. ### How reliable is the Twitter API at scale? The number worth asking any vendor for is not uptime on a status page, it is what happens to YOUR job when a single call fails. We return a normal HTTP error rather than a partial body, so a failed call is retryable and cannot silently poison a batch, and a call that fails is still a call you were billed for, which is exactly why we would rather it errored loudly than returned half a page. Live availability and incident history are published on the [status page](/status) and the [changelog](/changelog), so you can read the record rather than take a claim. A vendor with no public incident history is not a vendor that has never had one. ### What are the benefits of using a Twitter API instead of scraping it yourself? Three, and they compound. You skip the platform relationship entirely: no developer account, no app review, no tier to be moved off. You skip the maintenance: X changes its surface without notice, and absorbing that is our problem rather than a week of yours. And you get parsed, typed responses instead of HTML you have to keep re-deriving. What you give up is control over the extraction, and a per-call cost you would otherwise pay in proxies and engineering time. If you already run scraping infrastructure across many sites, that trade may not favour us. ### How does the Twitter API handle authentication? One header. You send Authorization: Bearer with a key from your dashboard, and that is the whole handshake: no OAuth dance, no token refresh, no callback URL to register, and no X developer account behind any of it. Keys are per-account and rotate independently, so a leaked key is a key you revoke rather than an outage. Write actions on an account you control need that account connected first; reads need nothing but the key. Full detail on the [quickstart](/quickstart). ### How does a third-party Twitter API compare to the official one? They bill on different axes, which is why a headline comparison misleads. The official X API charges per distinct resource read and does not charge twice for the same post inside a 24 hour window, so a fast polling cadence is free and a broad backfill is expensive. We charge per request, so cost is exactly proportional to calls and a dense pull is cheap. The official API is also the only one that can give you contractual guarantees about provenance and deletion, and if your use case is regulated that decides it regardless of price. Everything else, cost and setup time and endpoint breadth, is laid out on [Twitter API pricing](/twitter-api-pricing). ### Pay-per-use pricing, in plain English You are billed for calls you make, and nothing else. There is no monthly minimum, no seat, no tier to outgrow and nothing to keep alive between projects. A read call is $0.0008 and returns about 20 tweets, so 1,000 tweets costs about $0.04, and a month where you make no calls costs nothing. Two consequences people are usually surprised by, so they are worth saying plainly: a call that comes back empty still counts as a call, because the work was done to answer it; and there is no volume discount to negotiate, because the first call and the ten millionth are the same price. Project your own number with the [Twitter API Cost Calculator](/twitter-api-cost-calculator), or read the full breakdown on [pricing](/pricing). ### What is TwitterAPIs and which Twitter data can I pull? TwitterAPIs gives you programmatic access to public X data: individual tweets, reply chains, full threads, user profiles, follower and following lists, and keyword search. Every supported route and its per-call price is listed on the [TwitterAPIs Pricing](/pricing) page. ### How much does TwitterAPIs cost versus the official X API? Billing is purely per call, with no monthly tier to commit to. Reads run $0.0008 a call and return roughly 20 tweets, which works out to $0.04 per 1,000 tweets; simple write actions run the same $0.0008 a call, and creating a tweet runs $0.0016. To project a real monthly figure for your workload, run the numbers through the [Twitter API Cost Calculator](/twitter-api-cost-calculator) or check the [Twitter API Pricing Comparison](/twitter-api-pricing). ### Can I try the Twitter API for free before paying? Yes. Every new account starts with $0.50 in [free credits](/twitter-free-api), enough to make live calls right away, and we never ask for a card to begin testing. ### Is running a Twitter unofficial API in production a good idea? For one-off scripts and quick experiments an unofficial Twitter API is fine, but anything you put in front of real users needs predictable uptime and a clear stance on platform policy. Weigh those tradeoffs in the [Twitter unofficial API guide](/twitter-unofficial-api) before you settle on a stack. ### Do I have to register an X developer account? No. There are no X developer app credentials to apply for or maintain. Create an account, copy your key, and your first request can go out in minutes. ### How does TwitterAPIs stack up against other Twitter API alternatives? The [Twitter API alternatives and X API alternatives](/twitter-api-alternatives) page lays each option out side by side. Judge them on how they bill, how they treat rate limits, and how fast you can wire them into your code for the job you actually have. ### Are there platform rate limits or endpoint caps? One ceiling, and it is the same on every route: 600 requests per minute and 20 concurrent requests per API key. There are no per-endpoint quotas, no tier gates and no monthly plan, so any route is open to you at that rate for as long as your credits last. Going over returns 429 with a Retry-After header. The [Twitter API Rate Limits Comparison](/twitter-api-rate-limits) shows how that differs from the throttling on the official X API. ### What happens to my data and my credentials? The only personal details we keep are your email and name. Most routes are read-only against public data. For private reads and write actions such as like, retweet, bookmark, and follow, you either register an X session, which is stored encrypted at rest with AES-256-GCM until you replace it, or pass one per request, which is never stored. Everything moves over encrypted HTTPS, and your data is never sold or shared. The full breakdown is on our [Privacy and Data Handling](/privacy-and-data-handling) page. ## Start fetching Twitter data today. $0.50 free credits on signup. No credit card. No developer account. Just an API key and your first call running in under 5 minutes. [Get started free](/signup)[View docs](https://docs.twitterapis.com) No credit card required · $0.0008 per call · Cancel anytime [ TwitterAPIs ](/) The cheapest pay-as-you-go Twitter and X API. $0.0008 per call, which is $0.04 per 1,000 tweets on a full 20-tweet page. No subscriptions, no developer account. [emma@twitterapis.com](mailto:emma@twitterapis.com) ## API - [Pricing](/pricing) - [Endpoints](/pricing) - [Cost Calculator](/twitter-api-cost-calculator) - [Rate Limits](/twitter-api-rate-limits) ## Developers - [Documentation](https://docs.twitterapis.com) - [API Reference](https://docs.twitterapis.com) - [MCP Server](/mcp) ## Resources - [Blog](/blogs) - [Alternatives](/twitter-api-alternatives) - [vs Tweepy](/twitterapis-vs-tweepy) - [vs twitterapi.io](/twitterapis-vs-twitterapi-io) - [vs GetXAPI](/twitterapis-vs-getxapi) - [vs RapidAPI](/twitterapis-vs-rapidapi) ## Legal - [Privacy Policy](/privacy-and-data-handling) - [Terms of Service](/terms-of-service) - [Data Handling](/privacy-and-data-handling) © 2026 TwitterAPIs. All rights reserved. Language English [Deutsch](/de)[简体中文](/zh-hans)[Français](/fr)[Español](/es)[한국어](/ko)[日本語](/ja) All systems operational