TweetScout Review (2026): It Is Now Sorsa, and We Priced Every Tier

If you searched for TweetScout and landed on a site called Sorsa, nothing is broken. TweetScout was renamed Sorsa, and the vendor says so in its own FAQ: "TweetScout is now Sorsa: same team and data, new name and more features. Old tweetscout.io links open Sorsa." We checked the plumbing rather than taking that on faith — on 29 October 2026, tweetscout.io and app.tweetscout.io both return HTTP 301 to https://sorsa.io, while the old marketing site at about.tweetscout.io returns a 522 and no longer loads at all.

That makes most of the TweetScout write-ups still circulating stale on the one detail that matters: the price. They quote $35/month from a marketing page that is now offline. The current product charges $49 a month, and the API is billed separately on top of that. This review covers what the Sorsa Score actually measures, what the free tier returns, every API tier priced per request, and the three places where the published documentation disagrees with the live service.

The rebrand is cosmetic in architecture and substantial in packaging. The score, the crypto-account database and the team are the same; what changed is that the product split cleanly into three surfaces, each on its own hostname:

• sorsa.io — the marketing site and free score checker. Its sitemap.xml contains exactly one URL, last modified 28 September 2026, so the whole public pitch is a single page with in-page anchors.
• app.sorsa.io — the product itself: profiles, watchlists, the Early Projects and VC Trends feeds.
• api.sorsa.io — a separately sold developer API with its own pricing page, dashboard and documentation site.

One loose end is worth knowing if you have integrations: the two consumer hostnames 301 cleanly, but api.tweetscout.io still answers with HTTP 200 and serves the current application rather than redirecting. Its llms.txt is byte-identical to the one at api.sorsa.io — 13,716 bytes on both. Old API traffic therefore keeps working on the old brand name, which is convenient now and a migration you have not yet done later.

The nav on the new homepage still carries the string "ex. TweetScout", and the hero subtitle reads "Crypto Twitter score checker · formerly TweetScout". The vendor is not hiding the change, it simply has not reached the third-party reviews yet.

The Sorsa Score — the metric people still search for as the TweetScout score — is a social-graph number and nothing else. It counts who follows an account, weighted by how influential those followers are, against the vendor's own database of crypto accounts. The documentation is unusually direct about what is excluded: total follower count, content quality, profile design and blue-check verification do not feed the score, and accounts flagged as follow-for-follow or mass-following are filtered out entirely.

Scores bucket into five tiers, published on the homepage:

Tier	Score	What it means
1. Unknown	0–99	No notable crypto followers yet
2. Noted	100–499	On the radar of real crypto accounts
3. Credible	500–999	Followed by a solid crypto circle
4. Significant	1,000–1,999	Followed by top KOLs, projects and funds
5. Supreme	2,000+	The top of crypto X

For calibration, the live board on the homepage on 29 October 2026 read: vitalik.eth 5,121, OpenSea 4,251, ZachXBT 4,134, Solana 3,424, MoonPay 2,939, Monad 2,617, Lookonchain 2,297. Only seven accounts are shown, and all seven clear the Supreme threshold, so the public examples tell you where the ceiling sits and nothing about the distribution below it.

Two things about the methodology deserve more scepticism than the marketing invites. First, the score is self-referential by construction: the documentation says a follower with a score above 1,000 contributes more than a dozen followers scoring 200, which means an account's score is a function of its followers' scores, which are functions of theirs. That is the shape of an eigenvector-centrality calculation, and like all of them it is only as good as the seed set — here, the 100,000-plus accounts the vendor has hand-tagged as KOLs, projects or funds. Second, you cannot reproduce it from outside. The inputs are described; the weights, the tagging set and the farm-detection rules are not published. You are buying the vendor's judgement about who counts, not a formula you can audit. For anything you need to verify independently, an on-chain source such as a Solana wallet tracker is the one you can actually check.

Credit where it is due on one point: the FAQ explicitly denies a conflation that circulates constantly, stating that the Sorsa Score is not TweepCred and that TweepCred is an internal X signal that is not public. Vendors rarely bother to correct a flattering rumour.

The loudest demand behind the "tweetscout" query is not product research. The top organic results for the term are Reddit threads titled "My tweetscout is always zero. What should I do?" and "Tips on Improving tweet scout score!", both from communities running X bounty campaigns that gate rewards on the score. If you are one of those people, the methodology above already answers it, and the answer is unwelcome.

A zero means no account in the vendor's tagged crypto database follows you. Posting more does not change that, because posts are not an input. Neither do likes, giveaways, a blue check, or buying followers — the last of those is actively filtered. The vendor's own guidance is that the only lever is being followed by accounts that already score highly, and that follow-for-follow and mass-following patterns get excluded rather than counted. For a bounty hunter, the practical implication is blunt: a score-gated campaign is measuring whether established crypto accounts already recognise you, and there is no shortcut that the system does not explicitly detect.

A second cause worth ruling out: the score only moves on daily refreshes, and the FAQ notes a drop can mean a top follower unfollowed you or was excluded for follow-for-follow behaviour. If you were scored once and have stayed flat, the data is current and the number is real.

Free is genuinely useful here, which is the main thing the stale $35/month reviews get wrong in the other direction. Without paying anything you get the score itself, the tier, top-follower counts, the day-by-day score history, and the follower-quality-by-tier breakdown. That is enough for a quick sniff test on a project account.

Sorsa Plus is $49 a month or $499 a year, and adds the full top-follower list, the bot-follower check, tweet stats, mentions by top accounts, the complete Trending, Early Projects and VC Trends feeds, a 100-account watchlist, and manual refresh on any account.

Two pieces of arithmetic are worth doing before you click. The homepage advertises Plus "From $41.58/mo, billed yearly", which is simply $499 ÷ 12 = $41.58. Against twelve months at $49 ($588) that is a saving of $89, or 15.1% — about 1.8 months free, not the two months the API plans advertise. And the refund policy is explicit: you can cancel any time and Plus runs to the end of the paid period, but there are no refunds. The vendor's own suggestion is the right one — check accounts on the free tier before committing to a year.

The cost that catches people is the split. API access is sold separately from Sorsa Plus, in the vendor's own words. If you want the dashboard and programmatic access to the same numbers, that is $49 for Plus plus $49 for the cheapest API plan, or $98 a month.

The developer side is the more interesting half of this product, and it is the one nobody reviews. The base URL is https://api.sorsa.io/v3, authentication is a single ApiKey request header with no OAuth flow and no app-approval process, and every plan carries the same 20 requests per second limit.

The crypto-specific endpoints are the reason a Solana trader would care:

• GET /score — current Sorsa Score. Returns a bare {"score": …}.
• GET /score-changes — week and month deltas.
• GET /followers-stats — followers split into influencers, projects and venture-capital employees.
• GET /top-followers and GET /top-following — top 20 each by score.
• GET /new-followers-7d and GET /new-following-7d — recent crypto follow activity, tracked accounts only.

Those seven are the whole crypto layer; the other 33 endpoints are general X data — profiles, tweets, search, followers, lists, communities and campaign-verification checks. We counted them against the vendor's own index and found a discrepancy. The pricing page says every plan "includes all 40 endpoints", and the machine-readable API reference at /v3/static/sorsa_api_v3_documentation_en.txt does document 40. The llms.txt index that AI agents and developers read first lists only 38, omitting POST /community-info and POST /search-communities, and naming the retweeters endpoint POST /retweets where the full reference calls it POST /retweeters. If you are building against the summary file, you are working from a stale map — fetch the full reference instead.

Two documentation drifts show up the moment you make a real request. Calling any endpoint without a key returns:

• HTTP 403, with the body {"message":"missing key in request header"}, in about 230 ms.

The docs say otherwise twice over. The error-codes page maps 401 to "Unauthorized: authentication failed" and reserves 403 for "valid key but no access or credits"; an endpoint-level table is more specific still, giving 401 for "missing or invalid API key" and 403 for "quota exhausted or subscription expired". A missing key produces neither. The documented example body is {"message": "ApiKey required"}, which is also not the string the service returns. Neither is harmful, but if your retry logic branches on 401 versus 403 to decide between "fix the key" and "top up the balance", it will take the wrong branch on day one.

One genuine limitation we could not work around, and which cuts both ways: the authentication check runs before routing. Every path we tried without a key returned the same 403, including a deliberately invented endpoint name. That is reasonable security — it leaks no information about the surface — but it also means you cannot verify which endpoint names are live without paying, and we could not settle the /retweets versus /retweeters question from outside.

Sorsa's headline developer pitch is "$0.02 per 1K tweets" and "up to 50x cheaper than the official X API". Both are true. They are also computed on different assumptions, and reconciling them is the single most useful thing a developer can do before buying.

Pricing is flat: one API call is one request regardless of endpoint, with no credit multipliers. Here is every tier, with the per-request rate worked out:

Plan	Requests/mo	Monthly	Yearly	Per 1,000 requests
Free	100 one-time	$0	—	$0
Starter	10,000	$49	$490	$4.90
Pro	100,000	$199	$1,990	$1.99
Growth	250,000	$475	$4,750	$1.90
Enterprise	500,000	$899	$8,990	$1.80
Platform	1,000,000	$1,699	$16,788	$1.70
Business	3,000,000	$4,799	$47,988	$1.60
Scale	5,000,000	$7,499	$74,388	$1.50
Hyperscale	10,000,000	$13,990	$139,188	$1.40

Three findings from running the numbers:

The "2 months free" yearly claim is accurate, and conservative at the top. On Starter through Business, the yearly price is exactly ten times the monthly one. On Platform, Scale and Hyperscale it is slightly less — 9.88, 9.92 and 9.95 months respectively — so the largest plans give marginally more than two months. The four "save $X/mo vs. Pro rate" figures on the pricing page also check out to the dollar: Platform at 1M requests costs $1,699 against $1,990 at the Pro per-request rate, a saving of exactly $291, and the same holds for $1,171, $2,451 and $5,910 on the tiers above.

There is no overage penalty. Pay-as-you-go extra requests bill at $4.90 per 1,000 on Starter, $2.00 on Pro, $1.90 on Growth, down to $1.40 on Hyperscale. Compare those to the in-plan marginal rates in the table and they are the same numbers — the largest deviation across all eight tiers is half a percent, on Pro. Most API vendors charge a premium for bursting past the quota; this one does not.

The per-tweet headline assumes maximum batching, and archive work does not get it. The "$0.02 per 1,000 tweets" figure at Pro resolves to 10 million tweets from 100,000 requests — exactly 100 tweets per call, which is what POST /tweet-info-bulk delivers. But the Historical Data documentation states that POST /search-tweets and POST /user-tweets paginate at roughly 20 tweets per page. Pull an archive through those and 100,000 requests yields 2 million tweets, not 10 million: $0.0995 per 1,000 tweets, five times the advertised rate. That is also exactly where the "up to 50x cheaper" claim comes from — against the $5-per-1,000 official-API reference rate implied across Sorsa's own tiers, the paginated figure is 50.3x and the batched figure is 251x. Both of the vendor's numbers are internally consistent; the conservative one is the one that applies to archive search, and it is the one they chose to put in the headline.

Two more practical notes. The free tier is 100 requests, one time, no card, no expiry, covering all endpoints — and the docs put a useful unit on it: a full due-diligence pass on one account is about four calls (score, change, follower breakdown, top followers), so 100 requests is roughly 25 accounts. And the 20 req/s rate limit is never the binding constraint; sustained, it would deliver about 51.8 million requests a month, five times the largest plan's quota. The quota is what you run out of, not the rate.

This is where the tool's boundary matters most to anyone copying traders, and where the marketing is quiet. We searched Sorsa's entire published documentation corpus — 373 KB across 515 headings, the full llms-full.txt — for the words that would indicate on-chain capability. The counts:

• "on-chain" / "onchain": 0 matches.
• "wallet address": 0. "blockchain": 0. "Solana": 0. "PnL": 0.
• "copy trading" / "mirror trading": 0.
• "token" appears 27 times, every one of them about API pagination cursors, not crypto tokens.

Sorsa is an X analytics product with a crypto-flavoured social graph on top. It has no wallet data, no transaction history and no profit-and-loss figures, and it has never claimed to. That is a clean division of labour rather than a flaw, but it means a high score answers exactly one question — is this account recognised by people who matter in crypto — and tells you nothing about whether its trades make money. The two are not correlated in any way you should bet on. To check that, you need on-chain smart money data, not follower graphs.

Three further constraints are documented honestly and worth repeating:

• Read-only. The migration guide says plainly that if your integration also posts, likes or follows, keep your official X API key for the write path and migrate only reads.
• No rate-limit headers. There is no x-ratelimit-remaining or x-ratelimit-reset; the docs justify this on the grounds that the limit resets every second. You pace requests yourself and handle 429s.
• Daily refresh. Scores update about once a day, with manual refresh reserved for Plus. For anything that moves in minutes, this is not a real-time feed.

One small calibration trap: the documentation's worked example for GET /score shows Vitalik Buterin returning 1843.7, which would place him in Tier 4. The vendor's own live board shows 5,121, Tier 5. The sample is illustrative, but do not set your thresholds from it.

The honest comparison is not Sorsa against another analytics suite, it is Sorsa against the on-chain tools that answer the next question. Here is where each one actually sits:

Tool	Primary data	Answers
Sorsa (ex-TweetScout)	X follower graph	Is this account recognised?
Kolscan	Solana wallets of known KOLs	Does this KOL actually win?
Cielo	Multichain wallet activity	What did this wallet just do?
Arkham	Entity-labelled addresses	Who owns this wallet?
Nansen	Labelled flows at scale	Where is capital rotating?
uwuu	Verified on-chain leaderboard	Can I mirror this trader now?

In practice the sequence runs one way. A new ticker appears, you check the project's score to see whether anyone credible is behind it — the free tier handles this — and then you go on-chain, because recognition is not performance. A Solana KOL tracker gives you the wallet; a rug check gives you the contract risk; the verified leaderboard gives you 30-day PnL and win rate on addresses you can audit yourself. If you want the research chain laid out end to end, see how to copy KOL trades on Solana.

The step Sorsa never reaches is execution. Knowing a wallet is good does not get you into the trade — by the time a KOL's buy shows up in a feed you are reading, the move is minutes old. That gap is what a non-custodial Solana trading bot closes, by mirroring a verified trader's fills at sub-400ms rather than reporting them to you afterwards. uwuu charges a performance-based fee, so you pay only on the trades that make you money.

Worth $49/month if you are a project or a KOL whose job depends on the crypto social graph: tracking which VCs and influencers just followed a competitor, vetting partnership inbound, or auditing an influencer's follower quality before paying for a campaign. The bot-follower check and the mentions feed are hard to replicate manually, and the 100-account watchlist with manual refresh is the feature that justifies the subscription.

Worth the API tier if you are building something that needs X data at volume and the official API's cost or approval process is a blocker. Flat per-request pricing with no endpoint multipliers, a single header for auth, a full archive back to March 2006 with no separate tier, and an overage rate that matches the in-plan rate make it easy to model. Validate on the 100 free requests, and build against the full reference file rather than the llms.txt summary.

Not worth paying for if you are a trader looking for an edge. The free score check already answers the only question it can answer, and the paid tiers deepen social-graph detail rather than adding anything you can trade on. There is no on-chain data here at all. Spend the $49 on tooling that sees wallets.

Is TweetScout the same as Sorsa?

Yes. TweetScout was renamed Sorsa, and the vendor's FAQ states it directly: same team and data, new name, more features. We confirmed the plumbing on 29 October 2026 — tweetscout.io and app.tweetscout.io both return HTTP 301 to sorsa.io, and the old marketing site at about.tweetscout.io returns a 522 and no longer loads. The API still answers on api.tweetscout.io without redirecting.

How much does TweetScout cost in 2026?

Sorsa Plus is $49 a month or $499 a year, which works out to $41.58 a month and a 15.1% saving — about 1.8 months free, not two. The free tier gives you the score, the tier, score history and follower-quality breakdown. Reviews still quoting $35/month are reading a marketing page that is offline. API access is billed separately from $49/month.

Why is my TweetScout score zero?

Because no account in Sorsa's tagged crypto database follows you. The score counts who follows an account, weighted by their own score — posts, likes, giveaways and verification are not inputs, and bought or follow-for-follow followers are filtered out. The only documented way to raise it is being followed by accounts that already score highly.

What is a good Sorsa Score?

The published tiers are 0–99 Unknown, 100–499 Noted, 500–999 Credible, 1,000–1,999 Significant, and 2,000+ Supreme. For scale, the vendor's live board on 29 October 2026 showed vitalik.eth at 5,121 and the Solana account at 3,424. Note that the documentation's own code sample returns 1843.7 for Vitalik, which is stale — do not calibrate from it.

Does TweetScout have an API, and is it free?

Yes, at https://api.sorsa.io/v3, authenticated with a single ApiKey header. Every new account gets 100 one-time requests with no card and no expiry, covering all endpoints — roughly 25 accounts of due diligence at four calls each. Paid plans run $49/month for 10,000 requests up to $13,990/month for 10 million, all at 20 requests per second.

Can TweetScout or Sorsa show wallet data or PnL?

No. We searched the full 373 KB documentation corpus and found zero matches for "on-chain", "wallet address", "blockchain", "Solana", "PnL" and "copy trading". It is an X social-graph product with no blockchain data of any kind. For trader performance you need an on-chain source such as a wallet tracker or a verified leaderboard.

Is the Sorsa Score the same as TweepCred?

No, and the vendor says so explicitly. TweepCred is an internal X ranking signal that is not public. The Sorsa Score is a proprietary crypto-influence metric based on who follows an account, weighted by those followers' own scores — which also means it cannot be reproduced from outside, since the weights and the account-tagging set are not published.