Twexapi Documentation - Public Social Media & Twitter Scraper API

Public Twitter scraper and social media API alternative for search, profiles, followers, and AI agents. REST, SDKs, CLI, and MCP — pay per request without monthly minimums.

What TwexAPI is

TwexAPI is a third-party public social media & Twitter scraper API. Built as an affordable, developer-friendly X API alternative, it lets you search real-time tweets, read user profiles, and export followers at scale — from your app, a scraper script, or an AI agent — without paying high monthly subscription fees or managing scraper proxies.

You authenticate with one API key. Agents connect through MCP. Apps use REST or an SDK. Public read endpoints require no cookies or user accounts.

Build search queries in Advance Search TwitterXAPI, then pass them to Advanced Twitter Search.

Connect an AI coding agent

npx skills add twexapi-dev/x-api-scraper-cli

Ask for an outcome, not a path — for example “pull replies on this tweet” or “export followers for this handle”.

Numbers that matter

Latency: about 900ms average
Throughput: up to 100 requests per second per client
Availability: 99.9% uptime target
Pricing: from $0.000050 per request, pay as you go — see Rate Limits and the dashboard

Failed calls are billed fairly. Public docs focus on API-key reads.

What you can build

Twitter Search & Scraping API

Keyword, hashtag, and operator search. Scrape tweets in real time without browser automation. Generate searchTerms at x-advanced-search.cc.

Profiles & Follower Exports

User lookup, followers, and following exports with cursor pagination for audience research and lead generation.

Timelines & Thread Extraction

User timelines, tweet detail, conversation threads, replies, quotes, and full X Articles in Markdown.

MCP & AI Agents

explore then twexapi_request in Cursor, Claude, LangChain, and n8n for live web context.

SDKs & CLI Tooling

TypeScript, Python, Go, Java, and a headless CLI for automated scraping pipelines.

Trends & Engagement Reads

Real-time trending topics, tweet likers (favoriters), and engagement analytics on the same API key.

Compare & Architecture Guides

Choosing the right data pipeline for Twitter/X integration:

TwexAPI vs Official X API

Compare costs, rate limits, OAuth hurdles, and why developers choose per-request pricing over Official X’s per-resource fees.

TwexAPI vs Self-Hosted Scrapers

Avoid proxy bills, CAPTCHAs, and Puppeteer crashes with a managed REST alternative.

TwexAPI vs Apify Actors

900ms real-time REST latency vs 30-second asynchronous Actor queuing and compute unit pricing.

Nitter Alternatives in 2026

Drop-in, no-cookie Twitter extraction alternatives following the Guest Token shutdown.

Get started

Get an API key

Create a key in the dashboard. Review transparent micro-rates in our Pricing & Billing Guide.

Authenticate

Send Authorization: Bearer YOUR_API_KEY. Details: Authentication.

Call an endpoint

Start with API Overview or Advanced Twitter Search. Compare integration trade-offs in our Decision Hub.

Data handling

TwexAPI does not maintain an archive or database of X content. We do not persist copies of public posts, X Articles, direct-message content, or AI chat content obtained through customer requests.

Requests are processed in transit. We retain only limited operational information necessary for security, abuse prevention, billing, and service reliability, such as request timestamps, endpoint usage, status codes, and credit consumption. We do not sell or provide archived X-content datasets.