A fast, reliable X (Twitter) API and scraper for real-time data: 50× cheaper than the official API. 20 req/sec, 40 endpoints, AI-ready JSON, live in 3 minutes.
Sorsa is a read-only REST API and scraper for public X (Twitter) data: 40 endpoints covering tweets, advanced search, user profiles, followers, lists, communities, and action verification, all returned as clean JSON. One API key, flat per-request pricing, no OAuth and no approval, running since 2022.
How Sorsa API stacks up against the official X API and other ways to scrape X (Twitter) data.
| Feature | Sorsa API | Official X API | Other APIs & scrapers |
|---|---|---|---|
| Cost per 1K tweets | $0.09 | $5.00 | $0.15 to $1.50 |
| Setup time | 3 minutes | Days (approval needed) | Hours to days |
| Rate limit | 20 req/s | ~0.3 req/s | ~5 req/s |
| Latency (p50) | 300ms | ~1s | 500ms to 2s |
| Upkeep when X changes | Handled by Sorsa | N/A | Breaks, DIY fixes |
| AI-ready docs | ✓ | ✕ | Partial |
| Pricing model | Flat: 1 req = 1 call | Pay-per-resource | Usage-based or credits |
| Payment methods | Cards & crypto | Card only | Varies |
Paste a single URL into Claude Code, Codex, Cursor, Grok build, or Antigravity, and let it write your integration end to end. Not a cheaper substitute: this is the fastest way to put live X data into an AI stack today, official API included.
Paste the URL into Claude, ChatGPT, Cursor, Grok, or Gemini. The model learns every endpoint, parameter, and response shape on the spot.
OpenAPI 3.0 spec, structured for machine reading. Native compatibility with Claude tool use, OpenAI function calling, and Cursor MCP.
From LLM pipelines to trading bots, teams pick Sorsa for the same reasons: fair pricing, fast endpoints, and no enterprise gatekeeping.
Connect Claude, GPT, or any custom agent to a live X feed. Our AI-optimized OpenAPI spec drops straight into Claude tool use, OpenAI function calling, and Cursor MCP, giving one-shot integration without you writing a single wrapper.
Every endpoint returns clean, predictable JSON, so agents reason over the data instead of fighting it. The same 20 req/sec ceiling on every plan means agents don't get throttled the moment they go autonomous.
Track follower dynamics, engagement patterns, and the full social graph behind any account. Run brand-monitoring at agency scale, surface overlap between audiences, and benchmark growth velocity against direct competitors, all from a single API key.
Pull millions of fresh, public X conversations for model training and RAG without paying enterprise tiers.
Real-time market sentiment with sub-300 ms latency. Detect ticker mentions before mainstream coverage.
Confirm whether users actually followed, retweeted, commented, quoted, or joined a community before you reward them. Dedicated verification endpoints return a clean true or false, so you can run giveaways and engagement campaigns without manual checking.
40 endpoints across eight categories. Same data, higher limits, cleaner JSON.
Pull complete profile data, follower and following graphs, and account history for any public X account. Identify users by handle, ID, or profile URL.
/infofull profile (bio, counts, verification, creation date, pinned tweets)/info-batchup to 100 profiles in one request/aboutcountry, username change history/followerspaginated followers list, up to 200/page/followspaginated following list, up to 200/page/verified-followersverified accounts onlyFetch any tweet's full text, media, and engagement counts, pull entire user timelines back to a user's first tweet, and read X Articles in full.
/tweet-infosingle tweet with full metrics and nested quoted/retweeted content/tweet-info-bulkup to 100 tweets per request/user-tweetspaginated user timeline, no 3,200-tweet cap/commentsreplies under any tweet/quotesquote tweets under any tweet/retweeterslist of users who retweeted/articlefull X Article body, cover, metricsSearch across public X content using the full Twitter Advanced Search operator set. Filter mentions by engagement and date, discover users by keyword.
/search-tweetskeyword and operator search, popular or latest/mentionsmentions of a handle with filters (min likes, retweets, date range)/search-usersuser search by name, bio, keywordfrom:to:since:until:lang:min_faves:"exact phrase"#hashtag-excludeRead tweets and member rosters from any public List or Community on X. Useful for tight niche monitoring without scraping individual accounts.
/list-membersprofiles in a List/list-followerssubscribers to a List/list-tweetscombined timeline of List members/community-membersmembers of a Community/community-tweetsCommunity feed (popular or latest)/community-search-tweetskeyword search inside a CommunityOne-call checks that confirm whether a user performed a specific social action. Built for giveaway validation, airdrop eligibility, campaign analytics.
/check-followdid user A follow user B/check-commentdid the user reply under a tweet (returns the reply if yes)/check-quoteddid the user quote a tweet (returns date and text)/check-retweetdid the user retweet (cursor-based, scans 100 retweets/call)/check-community-membercommunity membership checkUtility endpoints for stable referencing and quota visibility. User IDs never change, even when handles do, so ID conversion is essential for any production pipeline.
/username-to-id/{handle}handle to numeric ID/id-to-username/{id}numeric ID to current handle/link-to-idprofile URL to numeric ID/key-usage-inforemaining requests, expiry, total usedSend a request, get clean JSON back. That's the whole learning curve.
curl -X POST "https://api.sorsa.io/v3/search-tweets" \ -H "ApiKey: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "AI agents min_faves:10", "order": "latest"}'
import requests response = requests.post( "https://api.sorsa.io/v3/search-tweets", headers={"ApiKey": "YOUR_API_KEY"}, json={"query": "AI agents min_faves:10", "order": "latest"} ) tweets = response.json()["tweets"]
const res = await fetch("https://api.sorsa.io/v3/search-tweets", { method: "POST", headers: { "ApiKey": "YOUR_API_KEY", "Content-Type": "application/json" }, body: JSON.stringify({ query: "AI agents min_faves:10", order: "latest" }) }); const { tweets } = await res.json();
package main import ( "bytes" "net/http" ) func main() { body := []byte(`{"query":"AI agents min_faves:10","order":"latest"}`) req, _ := http.NewRequest("POST", "https://api.sorsa.io/v3/search-tweets", bytes.NewBuffer(body)) req.Header.Set("ApiKey", "YOUR_API_KEY") http.DefaultClient.Do(req) }
$ch = curl_init("https://api.sorsa.io/v3/search-tweets"); curl_setopt_array($ch, [ CURLOPT_POST => true, CURLOPT_HTTPHEADER => ["ApiKey: YOUR_API_KEY", "Content-Type: application/json"], CURLOPT_POSTFIELDS => json_encode(["query" => "AI agents min_faves:10"]), CURLOPT_RETURNTRANSFER => true ]); $tweets = json_decode(curl_exec($ch), true);
Drop our docs URL into Claude or ChatGPT and let it write your integration. AI-optimized documentation, native function calling support.
We started as TweetScout API and scaled into the data backbone for thousands of independent builders and 100+ companies.
When X changes something on their side, we fix it on ours, so your integration keeps running. Built like a data provider, not a fragile scraper: every endpoint returns the same clean, structured JSON with a stable schema that does not drift when X ships changes, and cursor-based pagination returns complete result sets without the silent gaps that break DIY scrapers.
Three teams. Three different problems with the official API. One backend that finally got them shipping.
A signal pipeline polls X for ticker mentions around the clock. During volatility spikes the official API returned 429 errors at exactly the moments the data mattered most. Two scraper vendors were tested next; both degraded above a few requests per second.
The pipeline moved to Sorsa. The 20 req/sec limit is flat on every plan and holds under load, so response behavior during a spike is the same as on a quiet day.
We don't need the fastest API on earth. We need the same response time at 9:30 on a red day as on a quiet Sunday, and that's what we get. The 429 retry code is still in the repo. It just never fires anymore.
A solo-built giveaway platform verified follows, retweets, and comments through the official X API. After the usage was reclassified as commercial, the projected API bill came out higher than the product's monthly revenue.
The same verification checks run on Sorsa's dedicated endpoints with flat per-request pricing and no enterprise gate. The product stayed live and the unit economics flipped back to positive.
The math was simple: the API bill was about to be bigger than the revenue. I migrated the verification calls over a weekend, mostly find-and-replace plus a new auth header. The product didn't notice the switch. My bank account did.
An AI team waited months for official developer-account approval. Shortly after getting access, the account was suspended without explanation and support went silent, stalling the project.
Sorsa needed only a signup and a key. Because endpoint paths and JSON shapes stay close to the official API, the existing client ported over with minimal changes.
I pasted the Sorsa docs URL into Claude and asked it to port our client. It got 90 percent of the way there on the first pass, and the rest was renaming two fields. Hard to stay mad about a two-hour migration after waiting months for an approval email.
1 request equals 1 action, on every endpoint, on every plan. Same rate limit on Starter as on Enterprise. Pay by card or crypto.
Sorsa API is a fast, reliable, read-only REST API and scraper for public X (Twitter) data. It covers 40 endpoints across user profiles, tweets, advanced search, followers, lists, communities, and action verification, and returns clean JSON. Launched in 2022 as TweetScout API and later rebranded to Sorsa, it offers up to 50x lower prices than the official X API on flat per-request pricing, with a single API key and no developer-account approval.
Both refer to the same thing. Twitter rebranded to X in 2023, so the official product is now the X API, though many developers still search for the Twitter API. Sorsa works with public X (Twitter) data regardless of which name you use.
Sorsa API is a high-performance alternative that gives you full data access at up to 50x lower cost. You start instantly with a single API key, while the official X API uses pay-per-use pricing that bills separately for every post and profile, requires OAuth and a developer-account application, and caps reads at 2 million posts per month.
Sorsa API stands out on flat per-request pricing with no credit math, AI-optimized documentation that drops straight into Claude, GPT, and AI agents, and a strictly read-only design that keeps the service stable for serious data and AI workloads. It also covers areas many alternatives skip, including follow, retweet, comment, and community-membership verification, plus X Lists and communities. Sorsa has run in production since 2022.
Nothing on your side. When X ships changes to its frontend or internal APIs, the Sorsa team patches the data layer, the response schema stays stable, and your integration keeps running without code changes. This is the core difference between a managed API and a DIY scraper that breaks with every X update.
No. Sorsa API is read-only by design, focused on data retrieval and verification. Write actions are intentionally disabled to keep the service stable and abuse-resistant.
Yes. All plans, from Starter to Enterprise, share the same flat rate limit of 20 requests per second. We don't throttle speed on lower tiers.
Yes. Sorsa API was built AI-first. Clean JSON and AI-optimized documentation work natively with Claude, GPT, OpenClaw, and other agents. Drop the docs URL into your assistant for one-shot integration.
1 request always equals exactly 1 action. No credit multipliers, no hidden fees. Fetching a tweet, running advanced search, or pulling a follower list all cost the same: one request from your monthly quota. Batch endpoints return up to 200 profiles or 100 tweets in that single request, and the full author profile is included free inside every tweet, so one request often replaces dozens.
We accept all major credit and debit cards, and you can also pay with crypto. Crypto payments work on every plan, so you can fund your account and get your API key without a card if you prefer.
Yes. Sorsa API accesses publicly available X data, the same way a browser or search engine does. The service is built for ethical use cases like market research, AI training, and analytics, and follows relevant privacy laws.
Real-time with sub-second latency. Migration from the official X API typically takes under 2 hours because endpoints and JSON structure are deliberately similar. See the Migration Guide for details and example code.
Sign up, grab your API key, paste a curl command. That's it.