Skip to content
Get 100 free requests

Sorsa API vs TwitterAPIs

Sorsa API rehydrates 1,000 tweet IDs from $0.014 where TwitterAPIs charges $0.80, which makes Sorsa API the better choice, and no X session ever sits behind its key.

Sorsa API

$0.014per 1,000 tweet IDs

1,200requests a minute per key

2022first year in production

TwitterAPIs

$0.80per 1,000 tweet IDs

600requests a minute per key

2026first year in production

Short answer: On TwitterAPIs every tweet or profile you fetch by ID is its own $0.0008 call, under a ceiling of 600 calls a minute per key, so 1M tweet IDs cost $800 and about 28 hours of calls. Sorsa API returns 100 per request at 20 requests per second on every plan, which puts the same 1M IDs at 10K requests, from $14, in about 8 minutes, with 99.9% uptime guaranteed in its Terms. For reading X data in production, Sorsa API is the one to pick, and you can run your own IDs through 100 free requests that never expire.

  • Updated
  • 14 min read
  • Published by the Sorsa API team. TwitterAPIs' figures come from its own pages, linked below.

#Seven facts behind the verdict

  1. 57x less per tweet you already have the ID for.

    One Sorsa API request returns 100 tweets, so 1,000 tweet IDs cost from $0.014, while TwitterAPIs bills each one as a $0.0008 Tweet Detail call, $0.80 per 1,000.

  2. Profiles batch the same way.

    GET /info-batch returns 100 full profiles per request, from $0.014 per 1,000, where TwitterAPIs' User Info takes one account per call.

  3. Twice the requests per minute.

    Every Sorsa API key runs at 20 requests per second, 1,200 a minute, on every plan; TwitterAPIs states one ceiling of 600 a minute with 20 in flight.

  4. Hours of calls become minutes.

    At those two ceilings, 1M tweet IDs take Sorsa API about 8 minutes and TwitterAPIs about 28 hours of calls without a pause.

  5. No X session behind the key.

    Sorsa API has 0 write endpoints and never asks for your X login, while a TwitterAPIs key acts as your X account once a session is stored on it.

  6. Uptime written into the Terms.

    Sorsa API guarantees 99.9% uptime every month on paid plans, in Section 7.1 of its Terms; TwitterAPIs' Terms disclaim any losses from downtime.

  7. Four years in production.

    Sorsa API has served developers since 2022, first as TweetScout API, and twitterapis.com was registered in June 2026.

#What a lookup costs, call by call

TwitterAPIs, at twitterapis.com, is a pay-per-call API that started in 2026, and it is a separate service from TwitterAPI.io. Its Tweet Detail endpoint takes one id or one url per call and bills $0.0008. User Info and User Info by ID take one account each, at the same price. Nothing in its API reference returns tweets in a batch, so a list of 1,000 tweet IDs means 1,000 calls and $0.80.

Sorsa API's POST /tweet-info-bulk takes up to 100 tweet IDs or links per request and returns every tweet with its author's full profile inside. GET /info-batch does the same for 100 handles or user IDs. The same 1,000 IDs become 10 requests, from $0.014.

What you fetchSorsa APITwitterAPIs
1,000 tweet IDs10 requests, from $0.0141,000 calls, $0.80
1,000 profiles by ID10 requests, from $0.0141,000 calls, $0.80
1M tweet IDs10K requests, from $141M calls, $800

The "from" prices use the largest plan's rate, $1.40 per 1,000 requests. On Starter, the smallest plan, 1,000 tweet IDs come to $0.049, which is still a sixteenth of the TwitterAPIs bill.

#The same job against the clock

TwitterAPIs' rate-limit page states "One ceiling per API key: 600 requests per minute and 20 concurrent requests in flight", with no tier to upgrade into. Sorsa API runs every key at 20 requests per second, which is 1,200 a minute, from the smallest plan up, and raises the limit from the Platform plan on request.

Start a job of 1M tweet IDs at 9:00 on a Monday and let each API run at its own ceiling. Sorsa API's 10K requests are done at about 9:08. TwitterAPIs' 1M calls run until about 12:47 on Tuesday, nearly 28 hours later, if nothing pauses along the way.

1M tweet IDs, started on Monday at 9:00Sorsa APIdone at about 9:0810K requests of 100 IDs, at 20 per secondTwitterAPIsdone at about 12:47 on Tuesday1M calls of one ID, at 600 a minuteMon 9:0015:0021:00Tue 3:009:0015:00
Each API at its own published ceiling: 100 IDs per request at 1,200 requests a minute, against one ID per call at 600.

The batch and the ceiling compound. Sorsa API reads 100 IDs per request at twice the requests per minute, so it moves 200 times the tweets in the same minute, up to 2,000 tweets a second.

#Four read jobs, two receipts each

Rebuild a 5M-tweet research dataset

A university lab has 5M tweet IDs from a published dataset and needs every tweet back, with its author.

Sorsa API

Total: from $70

  • 50K requests, 100 IDs eachfrom $70
  • Time at 20 requests per secondabout 42 minutes
  • Author profile in every tweetincluded

Needs your X loginno

TwitterAPIs

Total: $4,000

  • 5M Tweet Detail calls at $0.0008$4,000
  • Time at 600 calls a minuteabout 5 days 19 hours

Needs your X loginonly for write actions

Track 100K posts every day

A media analytics product refreshes views, likes and replies on the 100K posts it follows, once a day.

Sorsa API

Total: from $42 a month

  • 30K requests a month, 1K a dayfrom $42
  • Time per daily refreshunder a minute
  • Fits inside one planPro's 100K requests a month

Needs your X loginno

TwitterAPIs

Total: $2,400 a month

  • 3M Tweet Detail calls a month$2,400
  • Time per daily refresh at 600 a minuteabout 2 hours 47 minutes

Needs your X loginonly for write actions

Enrich 300K handles in a CRM

A sales team holds 300K X handles from sign-ups and events and wants each account's bio, location, followers and verification.

Sorsa API

Total: from $4.20

  • 3K requests, 100 handles eachfrom $4.20
  • Time at 20 requests per secondabout 2.5 minutes
  • Fits the smallest planStarter's 10K requests

Needs your X loginno

TwitterAPIs

Total: $240

  • 300K User Info calls at $0.0008$240
  • User About Batch instead, billed per account$240
  • Time at 600 calls a minuteabout 8 hours 20 minutes

Needs your X loginonly for write actions

Hand an AI agent a key with no account behind it

A team connects an agent to X research, and the key will live in a config file shared with tools and colleagues.

Sorsa API

Total: read-only by design

  • What the key can doread public data
  • Write endpointsnone
  • X session stored on the keynever

Account risknone

TwitterAPIs

Total: a key that can act as you

  • What the key can do with a session on itpost, delete, follow, read and send DMs
  • Its MCP server, in the official MCP Registry"Read and write Twitter/X"

Account riskthe X account behind the session

#The buyer's scorecard

Sorsa API passes all ten checks; TwitterAPIs passes one.

CheckSorsa API10 of 10TwitterAPIs1 of 10
Price per 1,000 resultsfrom $0.014 per 1,000 tweet IDs$0.80, one tweet per call
Batch lookups100 tweets or profiles per requestone per call, or billed per item
Rate limit on the smallest plan20 requests per second600 a minute, 20 in flight
A free test with no deadline100 requests, never expire$0.50 credit, never expires
What it needs from your X accountnothing: no write endpointsan X session, for writes
Track recordin production since 2022domain registered June 2026
An endpoint for every step6 checks, follow to shadowbanfollow and account status
A predictable billplan price locked while subscribedpricing may change with notice
A guarantee written into the terms99.9% uptime, Section 7.1not liable for downtime losses
A contract for serious volumean SLA we sign from 1M a monthliability capped at 30 days' fees

#Two keys, two levels of access

A Sorsa API key that leaks, or sits in an agent's config, can read public data and spend your requests; it can never speak as your X account.

Sorsa API key

  • reads public posts, profiles, followers, Lists, Communities, Spaces and X Articles
  • runs follow, retweet, quote, comment, Community and shadowban checks
  • has no write endpoints: it can't post, like, follow, delete or send a DM

TwitterAPIs key, with an X session stored on it

  • posts, schedules and deletes tweets as your account
  • likes, retweets, follows and unfollows
  • reads and sends your DMs
  • reads your bookmarks, likes and block list
  • changes your name, bio, avatar and banner
  • logs in with your X password and two-factor secret, then keeps the session on the key

Source: TwitterAPIs docs, "Write Sessions" (opens in a new tab)

#One stored session changes what a key can do

TwitterAPIs' reads work on the API key alone. The risk arrives with the first session someone stores: its docs say TwitterAPIs "runs every write as your account", and they warn that the session values "grant full control of your X account". Its login endpoint takes a username and password, "plus a TOTP secret when two-factor authentication is enabled", and stores the session on the key. A Sorsa API key has no such path, because Sorsa API has no endpoint that writes.

For AI agents, a key that can only read

Agents need X data far more often than they need an X account. Sorsa MCP, npx -y sorsa-mcp on npm and in the official MCP Registry, gives Claude, Cursor and other MCP clients tools that read: search, profiles, followers, Lists, Communities and the checks. None of them can post, like, follow or send a message, since the API behind them has no write endpoints at all.

TwitterAPIs' server describes itself in the same registry as "Read and write Twitter/X: search, users, tweets, DMs." Its read tools run on the key, and its own MCP page says its "write actions act as a linked X account". For an agent that only reads, the second half adds risk and no capability. Setup prompts for Claude Code, Cursor and Codex are on Build with AI.

#TwitterAPIs' terms and pages, line by line

  • Downtime

    TwitterAPIs

    “We are not liable for any losses caused by downtime”

    Terms of Service, section 8

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: "We are not liable for any losses caused by downtime"Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    Sorsa API guarantees 99.9% uptime in each calendar month on every paid plan, in Section 7.1 of its Terms.

  • Uptime record

    TwitterAPIs

    “Why there is no uptime percentage”

    status page, a section heading

    TwitterAPIs, twitterapis.com/status, seen Nov 3, 2026: "Why there is no uptime percentage"Full capture
    Seen Nov 3, 2026 on twitterapis.com/status (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_status

    Sorsa API

    Sorsa API's 99.9% is a written commitment, measured month by month.

  • Your X credentials

    TwitterAPIs

    “discarded the moment the call finishes ... stored against that key and encrypted at rest”

    security page, both on the same page

    TwitterAPIs, twitterapis.com/security, seen Nov 3, 2026: "discarded the moment the call finishes ... stored against that key and encrypted at rest"Full capture
    Seen Nov 3, 2026 on twitterapis.com/security (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_security

    Sorsa API

    Sorsa API never receives X credentials of any kind, so there is nothing to discard or store.

  • Liability

    TwitterAPIs

    “Our total liability is limited to the amount you paid in the 30 days preceding the claim”

    Terms of Service, section 9

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: "Our total liability is limited to the amount you paid in the 30 days preceding the claim"Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    Sorsa API's cap is the greater of three months of fees and $100 (Section 15.2).

  • Price changes

    TwitterAPIs

    “Pricing is listed on our pricing page and may change with notice”

    Terms of Service, section 5

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: "Pricing is listed on our pricing page and may change with notice"Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    While your Sorsa API subscription stays active, its price never goes up (Section 8.10).

  • Who you contract with

    TwitterAPIs

    “TwitterAPIs operates this service”

    Privacy and Data Handling, under Data Controller; the Terms name no company, address or governing law either

    TwitterAPIs, twitterapis.com/privacy-and-data-handling, seen Nov 3, 2026: "TwitterAPIs operates this service"Full capture
    Seen Nov 3, 2026 on twitterapis.com/privacy-and-data-handling (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_privacy_and_data_handling

    Sorsa API

    Sorsa API's Terms name Scouts Labs Inc and its registered office.

#TwitterAPIs on Sorsa API: five lines, checked

#Even TwitterAPIs says it

#Since 2022, against a 2026 domain

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed Sorsa API in 2025

  2. 2026

    TwitterAPIs

    twitterapis.com registered on June 22, 2026

#TwitterAPIs pricing, explained

TwitterAPIs sells prepaid credits, in packs from $10, and bills them by the call. A standard call costs $0.0008, whatever it returns. Posting, DMs and article writes cost $0.0016 a call, a full account history $0.0024, a full thread $0.004 and a login $0.01.

Its one profile-style batch, User About Batch, bills $0.0008 for every account it returns, so 100 accounts cost the same as 100 calls. For lookups by ID that settles the unit: one tweet or one profile per call, $0.80 per 1,000, on every volume.

Sorsa API prices the request instead. A request to POST /tweet-info-bulk or GET /info-batch carries up to 100 IDs, so 1,000 cost from $0.014, and the rate per request falls as plans grow, down to $1.40 per 1,000 requests.

Tweet IDs to rehydrate

Sorsa API

from$14

for 1M tweet IDs

from $0.014 per 1,000 tweet IDs

TwitterAPIs

$800

for 1M tweet IDs

$0.0008 per ID, one per call

About 57x less on Sorsa API

#Port your TwitterAPIs reads

Each TwitterAPIs read below has a Sorsa API endpoint for the same job. Send your key in the ApiKey header to https://api.sorsa.io/v3, turn lookups by ID into batches of 100, and keep paging with next_cursor.

TwitterAPIsSorsa APINote
GET /twitter​/tweet​/detailPOST /tweet-info-bulk100 tweet IDs or links per request
GET /twitter​/user​/info_by_idGET /info-batch100 handles or user IDs per request
GET /twitter​/tweet​/advanced_searchPOST /search-tweetsthe same X search operators
GET /twitter​/user​/tweetsPOST /user-tweetsposts, replies or retweets
GET /twitter​/user​/mentionsPOST /mentionswith likes and date filters
GET /twitter​/tweet​/repliesPOST /commentsby relevance, recency or likes
GET /twitter​/tweet​/quotesPOST /quotes
GET /twitter​/tweet​/retweetersPOST /retweeters
GET /twitter​/user​/followersGET /followersup to 200 per page
GET /twitter​/user​/verified_followersGET /verified-followers
GET /twitter​/user​/check_follow_relationshipPOST /check-followplus retweet, quote, comment and Community checks
GET /twitter​/user​/user_aboutGET /aboutcountry and username history
GET /twitter​/list​/membersGET /list-members
GET /twitter​/list​/tweetsGET /list-tweetsa List of up to 5,000 accounts in one request
GET /twitter​/community​/membersPOST /community-members
GET /twitter​/spaces​/infoGET /spaces
GET /twitter​/article​/getPOST /articleX Articles
GET /account​/meGET /key-usage-infofree: it never counts against your requests
TwitterAPIs fieldSorsa API field
Authorization: Bearer headerApiKey header
tweet.textfull_text
tweet.authoruser, the full profile
favorite_countlikes_count
retweet_count, reply_count, quote_count, view_countthe same names
cursor parameternext_cursor, in the query for GET and the body for POST
rehydrate.py
import os
import requests

def rehydrate(tweet_ids):
    """Fetch tweets by ID from Sorsa API, 100 per request."""
    tweets = []
    for i in range(0, len(tweet_ids), 100):
        r = requests.post(
            "https://api.sorsa.io/v3/tweet-info-bulk",
            headers={"ApiKey": os.environ["SORSA_API_KEY"]},
            json={"tweet_links": tweet_ids[i:i + 100]},
            timeout=30,
        )
        r.raise_for_status()
        tweets.extend(r.json()["tweets"])
    return tweets

Posting stays with the official X API. Sorsa API is read-only by design, so your X account is never at risk: read with Sorsa API, and pair it with the official X API for the posts you publish.

#Run your own IDs first

For reading X data at production volume, choose Sorsa API: 100 IDs per request from $0.014 per 1,000, 20 requests per second on every plan, no X session on the key, and an uptime guarantee and a price that never goes up in its Terms, from a team trusted by 2,500+ developers and 100+ companies since 2022. The docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes, and Trust shows how Sorsa API handles your data. The eight checks behind the scorecard are explained in how to choose a Twitter/X data API, the wider field is in Twitter API alternatives, and every other comparison sits on the compare hub.

#FAQ

Is Sorsa API better than TwitterAPIs?

Yes. Sorsa API returns 100 tweets or profiles per request, so 1,000 IDs cost from $0.014 against $0.80 in one-per-call lookups on TwitterAPIs, and every key runs 1,200 requests a minute against TwitterAPIs' ceiling of 600. It is read-only, so no X session ever sits on its keys. It has been in production since 2022, and its Terms guarantee 99.9% uptime.

Is TwitterAPIs the same as TwitterAPI.io?

No. TwitterAPIs runs at twitterapis.com and bills $0.0008 per call; TwitterAPI.io runs at twitterapi.io and bills per item it returns. They are separate services with their own prices, terms and limits, and assistants sometimes merge the two. This page covers TwitterAPIs, and the other comparison is Sorsa vs TwitterAPI.io.

How much does TwitterAPIs charge for 1,000 tweets by ID?

$0.80. Its Tweet Detail endpoint takes one tweet ID or URL per call and bills $0.0008 a call, so 1,000 IDs are 1,000 calls, and 1M IDs cost $800. On Sorsa API, POST /tweet-info-bulk takes 100 IDs per request: 1,000 tweet IDs cost from $0.014, and 1M from $14, with each author's full profile included.

Can a TwitterAPIs key act as my X account?

Yes, once an X session is stored on it. Its docs say TwitterAPIs runs every write as your account, and its login endpoint takes your username, password and two-factor secret, then keeps the session on the key. Posts, deletions, follows, DMs and profile edits then run as you. A Sorsa API key cannot: Sorsa API has no write endpoints and never asks for your X login.

Does TwitterAPIs guarantee uptime?

No. Its Terms of Service say "We are not liable for any losses caused by downtime", and its status page says no historical uptime figure is published yet. Its marketing pages carry an uptime claim with no remedy behind it. Sorsa API guarantees 99.9% uptime each calendar month on paid plans in Section 7.1 of its Terms, with bonus requests if a month falls below 99.5%.

What is TwitterAPIs' rate limit?

600 requests per minute and 20 concurrent requests per API key, according to its rate-limit page, past which it answers with a 429. That is 10 requests a second. Sorsa API runs every key at 20 requests per second, 1,200 a minute, from the smallest plan up, so 1M tweet IDs take about 8 minutes on Sorsa API against about 28 hours of calls on TwitterAPIs.

When did TwitterAPIs launch?

In 2026. Its domain, twitterapis.com, was registered on June 22, 2026, and its MCP package first appeared on npm the next day. Sorsa API has been in production since 2022, when it launched as TweetScout API, and took its current name in 2025, so it brings four years of production to the same job.

How do I move from TwitterAPIs to Sorsa API?

Point your reads at https://api.sorsa.io/v3 with the ApiKey header, then map each call: Tweet Detail to POST /tweet-info-bulk with 100 IDs per request, User Info to GET /info-batch, Advanced Search to POST /search-tweets with the same operators, and followers to GET /followers. Pages continue with next_cursor. Keep the official X API for anything you post.

#Sources

Disclaimers

TwitterAPIs is a trademark of its owner. Sorsa API is not affiliated with TwitterAPIs.

X and the X logo are trademarks of X Corp. Sorsa API is not affiliated with, endorsed by, or sponsored by X Corp.

Published by the Sorsa API team. TwitterAPIs' figures come from its own pages, linked above, as seen on November 3, 2026.

By the Sorsa API team. We build and run Sorsa API, the read-only Twitter/X API and scraper, in production since 2022 (formerly TweetScout API) with 6B+ requests served. About Sorsa API

More comparisons

All comparisons

Evidence

Open the image

Sorsa API vs TwitterAPIs

Sorsa API rehydrates 1,000 tweet IDs from $0.014 where TwitterAPIs charges $0.80, which makes Sorsa API the better choice, and no X session ever sits behind its key.

Sorsa API

$0.014per 1,000 tweet IDs

1,200requests a minute per key

2022first year in production

TwitterAPIs

$0.80per 1,000 tweet IDs

600requests a minute per key

2026first year in production

Short answer: On TwitterAPIs every tweet or profile you fetch by ID is its own $0.0008 call, under a ceiling of 600 calls a minute per key, so 1M tweet IDs cost $800 and about 28 hours of calls. Sorsa API returns 100 per request at 20 requests per second on every plan, which puts the same 1M IDs at 10K requests, from $14, in about 8 minutes, with 99.9% uptime guaranteed in its Terms. For reading X data in production, Sorsa API is the one to pick, and you can run your own IDs through 100 free requests that never expire.

Updated , 14 min read

Published by the Sorsa API team. TwitterAPIs' figures come from its own pages, linked below.

Seven facts behind the verdict

  1. 57x less per tweet you already have the ID for.

    One Sorsa API request returns 100 tweets, so 1,000 tweet IDs cost from $0.014, while TwitterAPIs bills each one as a $0.0008 Tweet Detail call, $0.80 per 1,000.

  2. Profiles batch the same way.

    GET /info-batch returns 100 full profiles per request, from $0.014 per 1,000, where TwitterAPIs' User Info takes one account per call.

  3. Twice the requests per minute.

    Every Sorsa API key runs at 20 requests per second, 1,200 a minute, on every plan; TwitterAPIs states one ceiling of 600 a minute with 20 in flight.

  4. Hours of calls become minutes.

    At those two ceilings, 1M tweet IDs take Sorsa API about 8 minutes and TwitterAPIs about 28 hours of calls without a pause.

  5. No X session behind the key.

    Sorsa API has 0 write endpoints and never asks for your X login, while a TwitterAPIs key acts as your X account once a session is stored on it.

  6. Uptime written into the Terms.

    Sorsa API guarantees 99.9% uptime every month on paid plans, in Section 7.1 of its Terms; TwitterAPIs' Terms disclaim any losses from downtime.

  7. Four years in production.

    Sorsa API has served developers since 2022, first as TweetScout API, and twitterapis.com was registered in June 2026.

What a lookup costs, call by call

TwitterAPIs, at twitterapis.com, is a pay-per-call API that started in 2026, and it is a separate service from TwitterAPI.io. Its Tweet Detail endpoint takes one id or one url per call and bills $0.0008. User Info and User Info by ID take one account each, at the same price. Nothing in its API reference returns tweets in a batch, so a list of 1,000 tweet IDs means 1,000 calls and $0.80.

Sorsa API's POST /tweet-info-bulk takes up to 100 tweet IDs or links per request and returns every tweet with its author's full profile inside. GET /info-batch does the same for 100 handles or user IDs. The same 1,000 IDs become 10 requests, from $0.014.

  • 1,000 tweet IDs

    Sorsa API
    10 requests, from $0.014
    TwitterAPIs
    1,000 calls, $0.80

  • 1,000 profiles by ID

    Sorsa API
    10 requests, from $0.014
    TwitterAPIs
    1,000 calls, $0.80

  • 1M tweet IDs

    Sorsa API
    10K requests, from $14
    TwitterAPIs
    1M calls, $800

The "from" prices use the largest plan's rate, $1.40 per 1,000 requests. On Starter, the smallest plan, 1,000 tweet IDs come to $0.049, which is still a sixteenth of the TwitterAPIs bill.

The same job against the clock

TwitterAPIs' rate-limit page states "One ceiling per API key: 600 requests per minute and 20 concurrent requests in flight", with no tier to upgrade into. Sorsa API runs every key at 20 requests per second, which is 1,200 a minute, from the smallest plan up, and raises the limit from the Platform plan on request.

Start a job of 1M tweet IDs at 9:00 on a Monday and let each API run at its own ceiling. Sorsa API's 10K requests are done at about 9:08. TwitterAPIs' 1M calls run until about 12:47 on Tuesday, nearly 28 hours later, if nothing pauses along the way.

1M tweet IDs, started Monday 9:00 Sorsa API done at about 9:08 10K requests of 100 IDs, 20 per second TwitterAPIs done at about 12:47 on Tuesday 1M calls of one ID, 600 a minute Mon 9:00 Mon 21:00 Tue 9:00
Each API at its own published ceiling: 100 IDs per request at 1,200 requests a minute, against one ID per call at 600.

The batch and the ceiling compound. Sorsa API reads 100 IDs per request at twice the requests per minute, so it moves 200 times the tweets in the same minute, up to 2,000 tweets a second.

Four read jobs, two receipts each

Rebuild a 5M-tweet research dataset

A university lab has 5M tweet IDs from a published dataset and needs every tweet back, with its author.

Sorsa API

Total: from $70

  • 50K requests, 100 IDs eachfrom $70
  • Time at 20 requests per secondabout 42 minutes
  • Author profile in every tweetincluded

Needs your X loginno

TwitterAPIs

Total: $4,000

  • 5M Tweet Detail calls at $0.0008$4,000
  • Time at 600 calls a minuteabout 5 days 19 hours

Needs your X loginonly for write actions

Track 100K posts every day

A media analytics product refreshes views, likes and replies on the 100K posts it follows, once a day.

Sorsa API

Total: from $42 a month

  • 30K requests a month, 1K a dayfrom $42
  • Time per daily refreshunder a minute
  • Fits inside one planPro's 100K requests a month

Needs your X loginno

TwitterAPIs

Total: $2,400 a month

  • 3M Tweet Detail calls a month$2,400
  • Time per daily refresh at 600 a minuteabout 2 hours 47 minutes

Needs your X loginonly for write actions

Enrich 300K handles in a CRM

A sales team holds 300K X handles from sign-ups and events and wants each account's bio, location, followers and verification.

Sorsa API

Total: from $4.20

  • 3K requests, 100 handles eachfrom $4.20
  • Time at 20 requests per secondabout 2.5 minutes
  • Fits the smallest planStarter's 10K requests

Needs your X loginno

TwitterAPIs

Total: $240

  • 300K User Info calls at $0.0008$240
  • User About Batch instead, billed per account$240
  • Time at 600 calls a minuteabout 8 hours 20 minutes

Needs your X loginonly for write actions

Hand an AI agent a key with no account behind it

A team connects an agent to X research, and the key will live in a config file shared with tools and colleagues.

Sorsa API

Total: read-only by design

  • What the key can doread public data
  • Write endpointsnone
  • X session stored on the keynever

Account risknone

TwitterAPIs

Total: a key that can act as you

  • What the key can do with a session on itpost, delete, follow, read and send DMs
  • Its MCP server, in the official MCP Registry"Read and write Twitter/X"

Account riskthe X account behind the session

The buyer's scorecard

10 of 10 Sorsa API1 of 10 TwitterAPIs

Sorsa API passes all ten checks; TwitterAPIs passes one.

  • Price per 1,000 results

    Sorsa API
    from $0.014 per 1,000 tweet IDs
    TwitterAPIs
    $0.80, one tweet per call

  • Batch lookups

    Sorsa API
    100 tweets or profiles per request
    TwitterAPIs
    one per call, or billed per item

  • Rate limit on the smallest plan

    Sorsa API
    20 requests per second
    TwitterAPIs
    600 a minute, 20 in flight

  • A free test with no deadline

    Sorsa API
    100 requests, never expire
    TwitterAPIs
    $0.50 credit, never expires

  • What it needs from your X account

    Sorsa API
    nothing: no write endpoints
    TwitterAPIs
    an X session, for writes
The other 5 checks

  • Track record

    Sorsa API
    in production since 2022
    TwitterAPIs
    domain registered June 2026

  • An endpoint for every step

    Sorsa API
    6 checks, follow to shadowban
    TwitterAPIs
    follow and account status

  • A predictable bill

    Sorsa API
    plan price locked while subscribed
    TwitterAPIs
    pricing may change with notice

  • A guarantee written into the terms

    Sorsa API
    99.9% uptime, Section 7.1
    TwitterAPIs
    not liable for downtime losses

  • A contract for serious volume

    Sorsa API
    an SLA we sign from 1M a month
    TwitterAPIs
    liability capped at 30 days' fees

Two keys, two levels of access

A Sorsa API key that leaks, or sits in an agent's config, can read public data and spend your requests; it can never speak as your X account.

Sorsa API key

  • reads public posts, profiles, followers, Lists, Communities, Spaces and X Articles
  • runs follow, retweet, quote, comment, Community and shadowban checks
  • has no write endpoints: it can't post, like, follow, delete or send a DM

TwitterAPIs key, with an X session stored on it

  • posts, schedules and deletes tweets as your account
  • likes, retweets, follows and unfollows
  • reads and sends your DMs
  • reads your bookmarks, likes and block list
  • changes your name, bio, avatar and banner
  • logs in with your X password and two-factor secret, then keeps the session on the key

Source: TwitterAPIs docs, "Write Sessions" (opens in a new tab)

One stored session changes what a key can do

TwitterAPIs' reads work on the API key alone. The risk arrives with the first session someone stores: its docs say TwitterAPIs "runs every write as your account", and they warn that the session values "grant full control of your X account". Its login endpoint takes a username and password, "plus a TOTP secret when two-factor authentication is enabled", and stores the session on the key. A Sorsa API key has no such path, because Sorsa API has no endpoint that writes.

For AI agents, a key that can only read

Agents need X data far more often than they need an X account. Sorsa MCP, npx -y sorsa-mcp on npm and in the official MCP Registry, gives Claude, Cursor and other MCP clients tools that read: search, profiles, followers, Lists, Communities and the checks. None of them can post, like, follow or send a message, since the API behind them has no write endpoints at all.

TwitterAPIs' server describes itself in the same registry as "Read and write Twitter/X: search, users, tweets, DMs." Its read tools run on the key, and its own MCP page says its "write actions act as a linked X account". For an agent that only reads, the second half adds risk and no capability. Setup prompts for Claude Code, Cursor and Codex are on Build with AI.

TwitterAPIs' terms and pages, line by line

  • Downtime

    TwitterAPIs

    “We are not liable for any losses caused by downtime”

    Terms of Service, section 8

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    Sorsa API guarantees 99.9% uptime in each calendar month on every paid plan, in Section 7.1 of its Terms.

  • Uptime record

    TwitterAPIs

    “Why there is no uptime percentage”

    status page, a section heading

    TwitterAPIs, twitterapis.com/status, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/status (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_status

    Sorsa API

    Sorsa API's 99.9% is a written commitment, measured month by month.

  • Your X credentials

    TwitterAPIs

    “discarded the moment the call finishes ... stored against that key and encrypted at rest”

    security page, both on the same page

    TwitterAPIs, twitterapis.com/security, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/security (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_security

    Sorsa API

    Sorsa API never receives X credentials of any kind, so there is nothing to discard or store.

  • Liability

    TwitterAPIs

    “Our total liability is limited to the amount you paid in the 30 days preceding the claim”

    Terms of Service, section 9

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    Sorsa API's cap is the greater of three months of fees and $100 (Section 15.2).

  • Price changes

    TwitterAPIs

    “Pricing is listed on our pricing page and may change with notice”

    Terms of Service, section 5

    TwitterAPIs, twitterapis.com/terms-of-service, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_terms_of_service

    Sorsa API

    While your Sorsa API subscription stays active, its price never goes up (Section 8.10).

  • Who you contract with

    TwitterAPIs

    “TwitterAPIs operates this service”

    Privacy and Data Handling, under Data Controller; the Terms name no company, address or governing law either

    TwitterAPIs, twitterapis.com/privacy-and-data-handling, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on twitterapis.com/privacy-and-data-handling (opens in a new tab)Evidence 2026-11-03/www_twitterapis_com_privacy_and_data_handling

    Sorsa API

    Sorsa API's Terms name Scouts Labs Inc and its registered office.

TwitterAPIs on Sorsa API: five lines, checked

Even TwitterAPIs says it

Since 2022, against a 2026 domain

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed Sorsa API in 2025

  2. 2026

    TwitterAPIs

    twitterapis.com registered on June 22, 2026

TwitterAPIs pricing, explained

TwitterAPIs sells prepaid credits, in packs from $10, and bills them by the call. A standard call costs $0.0008, whatever it returns. Posting, DMs and article writes cost $0.0016 a call, a full account history $0.0024, a full thread $0.004 and a login $0.01.

Its one profile-style batch, User About Batch, bills $0.0008 for every account it returns, so 100 accounts cost the same as 100 calls. For lookups by ID that settles the unit: one tweet or one profile per call, $0.80 per 1,000, on every volume.

Sorsa API prices the request instead. A request to POST /tweet-info-bulk or GET /info-batch carries up to 100 IDs, so 1,000 cost from $0.014, and the rate per request falls as plans grow, down to $1.40 per 1,000 requests.

Tweet IDs to rehydrate

Sorsa API

from$14

for 1M tweet IDs

from $0.014 per 1,000 tweet IDs

TwitterAPIs

$800

for 1M tweet IDs

$0.0008 per ID, one per call

About 57x less on Sorsa API

Port your TwitterAPIs reads

Each TwitterAPIs read below has a Sorsa API endpoint for the same job. Send your key in the ApiKey header to https://api.sorsa.io/v3, turn lookups by ID into batches of 100, and keep paging with next_cursor.

  • GET /twitter/tweet/detail

    Sorsa API
    POST /tweet-info-bulk
    Note
    100 tweet IDs or links per request

  • GET /twitter/user/info_by_id

    Sorsa API
    GET /info-batch
    Note
    100 handles or user IDs per request

  • GET /twitter/tweet/advanced_search

    Sorsa API
    POST /search-tweets
    Note
    the same X search operators

  • GET /twitter/user/tweets

    Sorsa API
    POST /user-tweets
    Note
    posts, replies or retweets

  • GET /twitter/user/mentions

    Sorsa API
    POST /mentions
    Note
    with likes and date filters

  • GET /twitter/tweet/replies

    Sorsa API
    POST /comments
    Note
    by relevance, recency or likes

  • GET /twitter/tweet/quotes

    Sorsa API
    POST /quotes

  • GET /twitter/tweet/retweeters

    Sorsa API
    POST /retweeters

  • GET /twitter/user/followers

    Sorsa API
    GET /followers
    Note
    up to 200 per page

  • GET /twitter/user/verified_followers

    Sorsa API
    GET /verified-followers

  • GET /twitter/user/check_follow_relationship

    Sorsa API
    POST /check-follow
    Note
    plus retweet, quote, comment and Community checks

  • GET /twitter/user/user_about

    Sorsa API
    GET /about
    Note
    country and username history

  • GET /twitter/list/members

    Sorsa API
    GET /list-members

  • GET /twitter/list/tweets

    Sorsa API
    GET /list-tweets
    Note
    a List of up to 5,000 accounts in one request

  • GET /twitter/community/members

    Sorsa API
    POST /community-members

  • GET /twitter/spaces/info

    Sorsa API
    GET /spaces

  • GET /twitter/article/get

    Sorsa API
    POST /article
    Note
    X Articles

  • GET /account/me

    Sorsa API
    GET /key-usage-info
    Note
    free: it never counts against your requests

  • Authorization: Bearer header

    Sorsa API field
    ApiKey header

  • tweet.text

    Sorsa API field
    full_text

  • tweet.author

    Sorsa API field
    user, the full profile

  • favorite_count

    Sorsa API field
    likes_count

  • retweet_count, reply_count, quote_count, view_count

    Sorsa API field
    the same names

  • cursor parameter

    Sorsa API field
    next_cursor, in the query for GET and the body for POST
rehydrate.py
import os
import requests

def rehydrate(tweet_ids):
    """Fetch tweets by ID from Sorsa API, 100 per request."""
    tweets = []
    for i in range(0, len(tweet_ids), 100):
        r = requests.post(
            "https://api.sorsa.io/v3/tweet-info-bulk",
            headers={"ApiKey": os.environ["SORSA_API_KEY"]},
            json={"tweet_links": tweet_ids[i:i + 100]},
            timeout=30,
        )
        r.raise_for_status()
        tweets.extend(r.json()["tweets"])
    return tweets

Posting stays with the official X API. Sorsa API is read-only by design, so your X account is never at risk: read with Sorsa API, and pair it with the official X API for the posts you publish.

Run your own IDs first

For reading X data at production volume, choose Sorsa API: 100 IDs per request from $0.014 per 1,000, 20 requests per second on every plan, no X session on the key, and an uptime guarantee and a price that never goes up in its Terms, from a team trusted by 2,500+ developers and 100+ companies since 2022. The docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes, and Trust shows how Sorsa API handles your data. The eight checks behind the scorecard are explained in how to choose a Twitter/X data API, the wider field is in Twitter API alternatives, and every other comparison sits on the compare hub.

FAQ

Is Sorsa API better than TwitterAPIs?

Yes. Sorsa API returns 100 tweets or profiles per request, so 1,000 IDs cost from $0.014 against $0.80 in one-per-call lookups on TwitterAPIs, and every key runs 1,200 requests a minute against TwitterAPIs' ceiling of 600. It is read-only, so no X session ever sits on its keys. It has been in production since 2022, and its Terms guarantee 99.9% uptime.

Is TwitterAPIs the same as TwitterAPI.io?

No. TwitterAPIs runs at twitterapis.com and bills $0.0008 per call; TwitterAPI.io runs at twitterapi.io and bills per item it returns. They are separate services with their own prices, terms and limits, and assistants sometimes merge the two. This page covers TwitterAPIs, and the other comparison is Sorsa vs TwitterAPI.io.

How much does TwitterAPIs charge for 1,000 tweets by ID?

$0.80. Its Tweet Detail endpoint takes one tweet ID or URL per call and bills $0.0008 a call, so 1,000 IDs are 1,000 calls, and 1M IDs cost $800. On Sorsa API, POST /tweet-info-bulk takes 100 IDs per request: 1,000 tweet IDs cost from $0.014, and 1M from $14, with each author's full profile included.

Can a TwitterAPIs key act as my X account?

Yes, once an X session is stored on it. Its docs say TwitterAPIs runs every write as your account, and its login endpoint takes your username, password and two-factor secret, then keeps the session on the key. Posts, deletions, follows, DMs and profile edits then run as you. A Sorsa API key cannot: Sorsa API has no write endpoints and never asks for your X login.

Does TwitterAPIs guarantee uptime?

No. Its Terms of Service say "We are not liable for any losses caused by downtime", and its status page says no historical uptime figure is published yet. Its marketing pages carry an uptime claim with no remedy behind it. Sorsa API guarantees 99.9% uptime each calendar month on paid plans in Section 7.1 of its Terms, with bonus requests if a month falls below 99.5%.

What is TwitterAPIs' rate limit?

600 requests per minute and 20 concurrent requests per API key, according to its rate-limit page, past which it answers with a 429. That is 10 requests a second. Sorsa API runs every key at 20 requests per second, 1,200 a minute, from the smallest plan up, so 1M tweet IDs take about 8 minutes on Sorsa API against about 28 hours of calls on TwitterAPIs.

When did TwitterAPIs launch?

In 2026. Its domain, twitterapis.com, was registered on June 22, 2026, and its MCP package first appeared on npm the next day. Sorsa API has been in production since 2022, when it launched as TweetScout API, and took its current name in 2025, so it brings four years of production to the same job.

How do I move from TwitterAPIs to Sorsa API?

Point your reads at https://api.sorsa.io/v3 with the ApiKey header, then map each call: Tweet Detail to POST /tweet-info-bulk with 100 IDs per request, User Info to GET /info-batch, Advanced Search to POST /search-tweets with the same operators, and followers to GET /followers. Pages continue with next_cursor. Keep the official X API for anything you post.

Sources

Disclaimers

TwitterAPIs is a trademark of its owner. Sorsa API is not affiliated with TwitterAPIs.

X and the X logo are trademarks of X Corp. Sorsa API is not affiliated with, endorsed by, or sponsored by X Corp.

Published by the Sorsa API team. TwitterAPIs' figures come from its own pages, linked above, as seen on November 3, 2026.

By the Sorsa API team. We build and run Sorsa API, the read-only Twitter/X API and scraper, in production since 2022 (formerly TweetScout API) with 6B+ requests served. About Sorsa API

Rehydrate 10K tweet IDs free

Every new Sorsa API account gets 100 free requests: no credit card, and they never expire.

Get 100 free requestsSee pricing

More comparisons

All comparisons

Evidence

Open the image