Skip to content
Get 100 free requests

Sorsa API vs TwexAPI

Sorsa API is the better TwexAPI alternative: tweets and profiles cost from $0.014 per 1,000 instead of $0.05, at 20 requests per second, with no X account behind the key.

Sorsa API

$0.014per 1,000 tweets

20requests per second on the smallest paid plan

2022first year in production

TwexAPI

$0.05per 1,000 tweets

5requests per second on the smallest paid plan

2025first year in production

Short answer: TwexAPI (twexapi.io, first online in 2025 as TwitterXAPI) charges 5 credits for each post or profile it returns, which is $0.05 per 1,000. Sorsa API charges one request for 100 tweets or profiles, from $0.014 per 1,000, and runs every plan at 20 requests per second with no write endpoints. Choose Sorsa API, and run your own job first on 100 free requests that never expire, where TwexAPI's free credits last 7 days.

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

#TwexAPI pricing, explained

TwexAPI charges in credits: $1 buys 100K credits on its standard packs, and every post or profile it returns costs 5 of them, so 1,000 cost $0.05. Its largest one-time packs, $499 and $999, bring that to about $0.042 per 1,000. Requests that fail with an error are not billed.

Credits come three ways. Monthly plans give 5M credits for $50 (Basic) or 11M for $99 (Pro). One-time packs run from $20 for 2M credits (Mini) to $999 for 120M. New accounts get 20K free credits, which TwexAPI counts as about 4,000 posts or profiles.

Two catches sit in the plan table, not in the headline price:

  • How long credits last. The free credits are valid for 7 days, and the $20 Mini pack for one day. A job spread over a week needs a monthly plan or a pack from $100.
  • How fast you can spend them. The free credits run at 1 request every 5 seconds. The $20, $50 and $100 options allow 5 requests per second, the $99 and $199 ones 10, and TwexAPI reaches 20 requests per second only from its $499 Scale pack.
Sorsa API100 free requests, no cardTwexAPI20K free credits, no cardWhat they coverup to 10K tweetsWhat they coverabout 4,000 itemsHow long they lastnever expireHow long they last7 daysday 1day 30 and afterday 1day 7day 30at 1 request every 5 seconds
The free start on both sides: what it covers and how long it lasts.

Its batch lookups bill every item, and their size is tied to the plan: the docs for tweets by ID say "The maximum input quantity is limited by your plan’s QPS." Some third-party comparisons still describe TwexAPI as selling access per endpoint; its pricing page says there are no per-endpoint fees, and every endpoint draws from one balance.

The same data on Sorsa API is priced by the request. A batch of 100 tweets or 100 profiles is one request, so 1,000 cost from $0.014, and every plan from 10K to 10M requests a month runs at 20 requests per second. The receipts on this page use TwexAPI's standard rate, $1 per 100K credits, and Sorsa API's best plan rate, $1.40 per 1,000 requests; each plan's own rate is on the Sorsa API pricing page. TwexAPI publishes no maximum batch size, so its receipts show the plan's rate limit instead of a time.

Tweets to look up

Sorsa API

from$14

for 1M tweets

from $0.014 per 1,000 tweets

TwexAPI

$50

for 1M tweets

$0.05 per 1,000 tweets

About 3.5x less on Sorsa API

#Seven reasons Sorsa API wins the whole job

  1. Bulk lookups about 3.5x cheaper.

    One Sorsa API request returns 100 tweets or 100 profiles, so 1,000 cost from $0.014, against $0.05 on TwexAPI, which bills every item in a batch.

  2. 100 IDs per request on every plan.

    Sorsa API's batch size is the same on the smallest plan and the largest, while TwexAPI's docs say the input "is limited by your plan’s QPS".

  3. Four times the rate limit of TwexAPI's smallest plans.

    Every Sorsa API plan runs at 20 requests per second, against 5 on TwexAPI's $20, $50 and $100 options and 10 on its $99 and $199 ones.

  4. Free requests that never expire.

    A new Sorsa API account gets 100 requests, enough for up to 10K tweets, with no card and no deadline; TwexAPI's 20K free credits cover about 4,000 items and last 7 days.

  5. Zero risk to your X account.

    Sorsa API has 0 write endpoints and never asks for your X login, while TwexAPI's account actions run on your own logged-in X account.

  6. 99.9% uptime in the contract.

    Section 7.1 of Sorsa API's Terms of Service guarantees it on every paid plan; TwexAPI's Terms say they do not guarantee "the continuity, accuracy, or reliability of the service".

  7. In production since 2022.

    Sorsa API started as TweetScout API in 2022; TwexAPI's site was first archived in July 2025, under the name TwitterXAPI.

#Four jobs, two receipts each

Rehydrate 1M tweet IDs

A research team holds 1M tweet IDs from a published dataset and needs every tweet back with its author.

Sorsa API

Total: from $14

  • 10K requests to POST /tweet-info-bulk, 100 IDs eachfrom $14
  • Time at 20 requests per secondabout 8 minutes
  • Fits inthe 10K-request Starter plan

IDs per request100 on every plan

TwexAPI

Total: $50

  • 1M tweets at 5 credits each5M credits, $50
  • IDs per requestlimited by the plan's QPS
  • Rate limit on its $50 plan5 requests per second

IDs per requestset by the plan's QPS

Refresh 100K lead profiles every week

A sales team re-reads 100K X profiles every Monday to keep follower counts and bios current in its CRM.

Sorsa API

Total: from $5.60

  • 4K requests a month, 1K per refresh at 100 profiles eachfrom $5.60
  • Time per refresh at 20 requests per secondabout 50 seconds

Price fixed while you stay subscribedyes

TwexAPI

Total: $20

  • 400K profiles a month at 5 credits each2M credits, $20
  • Rate limit on its $20 to $100 options5 requests per second

Price fixed while you stay subscribedno promise in its terms

Give an AI agent read access to X

An agent in Claude, Cursor or your own code searches posts, reads profiles and runs checks with nobody watching each call.

Sorsa API

Total: 40 read-only tools

  • Installnpx -y sorsa-mcp
  • What the key can doread public data
  • Write toolsnone

Can post as your X accountno

TwexAPI

Total: 3 tools

  • Its posting toollabelled "Destructive, not idempotent"
  • What the agent can do with your login addedpost, reply, like and send DMs

Can post as your X accountyes, once your login is added

Test before you pay

You want to run your own job on your own data before you buy anything.

Sorsa API

Total: 100 free requests

  • Cardnot needed
  • Tweets they coverup to 10K
  • Expirynever

Needs your X loginno

TwexAPI

Total: 20K free credits

  • Cardnot needed
  • Posts or profiles they coverabout 4,000
  • Expiry7 days
  • Rate limit1 request every 5 seconds

Needs your X loginonly for account actions

#Ten checks, with values on both sides

The first eight checks come from how to choose an X data API; the last two read the contract. The one tie: both sides sign a custom SLA for large volumes, and on Sorsa API it starts at 1M requests a month.

Sorsa API passes all ten checks; TwexAPI passes one.

CheckSorsa API10 of 10TwexAPI1 of 10
Price per 1,000 resultsfrom $0.014 per 1,000 tweets$0.05 per 1,000 tweets
Batch lookups100 tweets for one requestsize capped by plan QPS
Rate limit on the smallest paid plan20 requests per second5 requests per second
A free test with no deadline100 requests, never expire20K credits for 7 days
What it needs from your X accountnothing: read-onlyyour X login for actions
Track record and a stable schemasince 2022, one user schemasince 2025, two user schemas
Checks for every campaign stepfive verification checksno verification checks
A predictable billone request for any callcredit cost varies by endpoint
A guarantee in the terms99.9% uptime, a price lockno continuity guarantee
A contract for serious volumean SLA from 1M a montha custom SLA on request

#What a TwexAPI key can do with your X login added

Give a Sorsa API key to an agent or a contractor, and the most it can do is read public data.

Sorsa API key

  • reads public posts, profiles, followers, Lists, Communities, Spaces and X Articles
  • has no write endpoints, so it can't post, like, follow or send DMs
  • never asks for your X login

TwexAPI key, with your X login added to a request

  • posts tweets, replies, threads and quote posts, and deletes tweets
  • likes, retweets and bookmarks posts
  • follows, unfollows and blocks accounts
  • sends DMs and reads your DM history
  • changes your profile's bio, image and banner

Source: TwexAPI, "API Overview" (opens in a new tab)

#For AI agents: 40 read-only tools against 3

TwexAPI reads public data with its API key alone, and its account actions are a second product on the same key: each write request carries the session of the X account it acts as, and TwexAPI's Terms say that for every write "users must authenticate using their own Twitter session credentials". Sorsa API has no such product, so its key has nothing to act on.

TwexAPI's MCP server brings those writes to agents. It has three tools: explore searches its catalog, twexapi_request calls a read endpoint and twexapi_write posts a tweet or a reply from your X account. TwexAPI labels the write tool "Destructive, not idempotent", and its docs warn that the account credential it takes "gives full control of that X account, and it passes through the AI client and its conversation history."

Sorsa API's MCP server gives an agent 40 tools, each named for one job, and none of them can write:

What the agent getsSorsa API MCP serverTwexAPI MCP server
Tools40, one per job3: explore, read, write
Write toolsnoneposting from your X account
Batches100 tweets or profiles per calllimited by the plan's QPS
Verification checksfollow, retweet, quote, comment, Communitynone
Spacesyesno endpoint

The server installs with npx -y sorsa-mcp from npm and is listed in the official MCP Registry. The Twitter MCP server page has the setup for Claude, Cursor and other clients, and the Twitter MCP server guide explains how an agent uses it.

#TwexAPI's terms in its own words

We read TwexAPI's Terms of Service (last updated September 3, 2026), its Privacy Policy and its pricing page in full. The Terms and the Privacy Policy name no company, no address and no governing law; their only contact is an email address. Sorsa API's Terms open with the company behind them, Scouts Labs Inc, and its registered office. TwexAPI's pricing page lists an uptime SLA claim on its paid plans, and its Terms say otherwise:

#In production since 2022

The Wayback Machine first archived TwexAPI's site on July 14, 2025, at twitterxapi.com, and twexapi.io was registered on August 3, 2025. Sorsa API had been in production for about three years by then, as TweetScout API. Its response schema stays the same as the API grows: one user object, with the same field names, in tweets, profile lookups and follower lists. TwexAPI's API reference documents two: its follower lists return userId and followersCount, while its tweets and profile lookups return id, screen_name and followers_count.

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed in 2025

  2. 2025

    TwexAPI

    first archived in July 2025 as TwitterXAPI

#Switch from TwexAPI: endpoints and fields

Send your key in the ApiKey header to https://api.sorsa.io/v3 instead of a Bearer token to https://api.twexapi.io. Every read below has a Sorsa API endpoint; Sorsa API is read-only by design, so to post, pair it with the official X API.

TwexAPISorsa APINote
POST /twitter​/tweets​/lookupPOST /tweet-info-bulk100 tweet IDs or links per request
POST /twitter​/users​/by_ids, POST /twitter​/usersGET /info-batch100 user IDs or usernames per request
POST /twitter​/followers​/pageGET /followers200 per page, by handle, ID or link
POST /twitter​/following​/pageGET /follows200 per page
POST /v3​/twitter​/users​/verified-followersGET /verified-followers
POST /twitter​/advanced_search​/pagePOST /search-tweetsthe same X search operators, back to 2006
POST /twitter​/{screen_name}​/timeline​/pagePOST /user-tweetsposts, replies or retweets
POST /twitter​/tweets​/{tweet_id}​/replies​/pagePOST /commentsby relevance, recency or likes
POST /twitter​/tweets​/quotes​/pagePOST /quotes
POST /twitter​/tweets​/retweeters​/pagePOST /retweeters
POST /twitter​/list​/tweets​/page, /twitter/list/members/pageGET /list-tweets, GET /list-membersa List of up to 5,000 accounts in one feed
GET /twitter​/community​/{community_id}, POST /twitter​/community​/searchPOST /community-info, POST /search-communities
POST /twitter​/community​/members​/page, /twitter/community/tweets/pagePOST /community-members, POST /community-tweets
GET /twitter​/{screen_name}​/aboutGET /aboutcountry, username changes, verification
POST /x​/articlePOST /articleX Articles with their stats
GET /twitter​/{country}​/trendingGET /trendsby location (WOEID)
POST /twitter​/shadowban​/checkGET /check-shadowban
GET /balanceGET /key-usage-infofree: it never counts against your requests
no endpointPOST /check-follow, POST /check-retweet, POST /check-quotedone request answers each check
no endpointGET /check-comment, POST /check-community-memberone request answers each check
no endpointGET /spacesa Space's details and stats
TwexAPI fieldSorsa API field
tweet_idid, always a string
full_textfull_text
created_at, as "Mon Jun 17 03:51:48 +0000 2024"created_at, ISO 8601
favorite_countlikes_count
view_countview_count
user.screen_name in tweets, username in follower listsuser.username everywhere
user.id in tweets, userId in follower listsuser.id everywhere
followers_count in tweets, followersCount in follower listsfollowers_count everywhere
following_count, followingCountfollowings_count
statuses_count, statusesCounttweets_count
namedisplay_name
adapter.py
import os

import requests

SORSA = "https://api.sorsa.io/v3"
HEADERS = {"ApiKey": os.environ["SORSA_API_KEY"]}


def tweets_by_ids(tweet_ids):
    """Replaces TwexAPI's POST /twitter/tweets/lookup, 100 IDs a request."""
    tweets = []
    for i in range(0, len(tweet_ids), 100):
        body = {"tweet_links": tweet_ids[i:i + 100]}
        r = requests.post(f"{SORSA}/tweet-info-bulk", headers=HEADERS,
                          json=body, timeout=30)
        r.raise_for_status()
        tweets.extend(r.json()["tweets"])
    return tweets


def profiles_by_usernames(usernames):
    """Replaces TwexAPI's POST /twitter/users, 100 usernames a request."""
    users = []
    for i in range(0, len(usernames), 100):
        query = {"usernames": usernames[i:i + 100]}
        r = requests.get(f"{SORSA}/info-batch", headers=HEADERS,
                         params=query, timeout=30)
        r.raise_for_status()
        users.extend(r.json()["users"])
    return users

Both functions return Sorsa API's standard objects: tweets with the full author profile inside each one, and users with the same fields a follower list returns.

#Run your own job before you decide

The free requests cover any job above at a small scale, and the docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes. Uptime and security shows how Sorsa API runs and what it keeps. Twitter API alternatives prices TwexAPI next to the rest of the market, and every other head-to-head sits on our Twitter API comparison hub.

Priced as whole jobs, Sorsa API is the stronger pick over TwexAPI: tweets and profiles from $0.014 per 1,000 instead of $0.05, 20 requests per second on every plan, a key that can never act as your X account, and 99.9% uptime written into its terms.

#FAQ

Is Sorsa API better than TwexAPI?

Yes. Sorsa API returns 100 tweets or profiles for one request, so 1,000 cost from $0.014 against TwexAPI's $0.05, and every plan runs at 20 requests per second, against 5 on TwexAPI's $20 to $100 options. Its key has no write endpoints, its 100 free requests never expire, and its Terms guarantee 99.9% uptime, where TwexAPI's Terms disclaim the continuity of the service.

How much does TwexAPI cost?

TwexAPI sells credits, $1 per 100K on its standard packs, and charges 5 for each post or profile it returns, so 1,000 cost $0.05, or about $0.042 on its $499 and $999 packs. Credits come as monthly plans at $50 and $99 or one-time packs from $20 to $999, and the $20 pack lasts one day. Sorsa API returns 100 tweets or profiles per request, from $0.014 per 1,000.

Does TwexAPI have a free tier?

Yes: 20K free credits, about 4,000 posts or profiles, with no card. Its pricing page gives them 7 days of validity and a rate of 1 request every 5 seconds. Sorsa API gives every new account 100 free requests with no card and no deadline, enough for up to 10K tweets or 10K profiles through its batch endpoints.

Is TwexAPI the same as TwitterAPI.io?

No. TwexAPI runs at twexapi.io and first went online in 2025 under the name TwitterXAPI; TwitterAPI.io is a separate service at twitterapi.io. Both bill each item they return and sell account actions through an X account you log in with. Sorsa API is read-only and bills the request, and Sorsa API vs TwitterAPI.io puts those two side by side.

Does TwexAPI need my X account?

Not to read public data. Its account actions do: posts, replies, likes, follows and DMs run on your own logged-in X account, so each write request carries that account's session, and its MCP server has a tool that posts. Sorsa API has no write endpoints and never asks for your X login, so the most a leaked key or a runaway agent can do is read public data.

Does TwexAPI guarantee uptime?

Not in its contract. Its pricing page lists an uptime SLA claim on paid plans, but its Terms say "We do not guarantee the continuity, accuracy, or reliability of the service" and exclude liability for any damages. Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms of Service, with bonus requests if a month falls below 99.5%, and signs an SLA from 1M requests a month.

Does TwexAPI have an MCP server for AI agents?

Yes, with three tools: explore, twexapi_request for reads, and twexapi_write, which posts a tweet or reply from your X account and is labelled "Destructive, not idempotent". Sorsa API's MCP server runs with npx -y sorsa-mcp and gives an agent 40 read-only tools, from batches of 100 tweets to five verification checks, at one request per call.

How do I switch from TwexAPI to Sorsa API?

Send your key in the ApiKey header to https://api.sorsa.io/v3, map each read to its Sorsa API endpoint and rename a few fields. Tweets by ID move to POST /tweet-info-bulk and profiles to GET /info-batch, 100 per request, and followers move to GET /followers with 200 per page. Sorsa API has no write endpoints: to post, pair it with the official X API.

#Sources

Disclaimers

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

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. TwexAPI's figures come from its own pages, linked above, as seen on the dates shown.

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 TwexAPI

Sorsa API is the better TwexAPI alternative: tweets and profiles cost from $0.014 per 1,000 instead of $0.05, at 20 requests per second, with no X account behind the key.

Sorsa API

$0.014per 1,000 tweets

20requests per second on the smallest paid plan

2022first year in production

TwexAPI

$0.05per 1,000 tweets

5requests per second on the smallest paid plan

2025first year in production

Short answer: TwexAPI (twexapi.io, first online in 2025 as TwitterXAPI) charges 5 credits for each post or profile it returns, which is $0.05 per 1,000. Sorsa API charges one request for 100 tweets or profiles, from $0.014 per 1,000, and runs every plan at 20 requests per second with no write endpoints. Choose Sorsa API, and run your own job first on 100 free requests that never expire, where TwexAPI's free credits last 7 days.

Updated , 12 min read

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

TwexAPI pricing, explained

TwexAPI charges in credits: $1 buys 100K credits on its standard packs, and every post or profile it returns costs 5 of them, so 1,000 cost $0.05. Its largest one-time packs, $499 and $999, bring that to about $0.042 per 1,000. Requests that fail with an error are not billed.

Credits come three ways. Monthly plans give 5M credits for $50 (Basic) or 11M for $99 (Pro). One-time packs run from $20 for 2M credits (Mini) to $999 for 120M. New accounts get 20K free credits, which TwexAPI counts as about 4,000 posts or profiles.

Two catches sit in the plan table, not in the headline price:

  • How long credits last. The free credits are valid for 7 days, and the $20 Mini pack for one day. A job spread over a week needs a monthly plan or a pack from $100.
  • How fast you can spend them. The free credits run at 1 request every 5 seconds. The $20, $50 and $100 options allow 5 requests per second, the $99 and $199 ones 10, and TwexAPI reaches 20 requests per second only from its $499 Scale pack.
Sorsa API 100 free requests, no card What they cover up to 10K tweets How long they last never expire day 1 day 30 and after TwexAPI 20K free credits, no card What they cover about 4,000 items How long they last 7 days day 1 day 7 day 30 at 1 request every 5 seconds
The free start on both sides: what it covers and how long it lasts.

Its batch lookups bill every item, and their size is tied to the plan: the docs for tweets by ID say "The maximum input quantity is limited by your plan’s QPS." Some third-party comparisons still describe TwexAPI as selling access per endpoint; its pricing page says there are no per-endpoint fees, and every endpoint draws from one balance.

The same data on Sorsa API is priced by the request. A batch of 100 tweets or 100 profiles is one request, so 1,000 cost from $0.014, and every plan from 10K to 10M requests a month runs at 20 requests per second. The receipts on this page use TwexAPI's standard rate, $1 per 100K credits, and Sorsa API's best plan rate, $1.40 per 1,000 requests; each plan's own rate is on the Sorsa API pricing page. TwexAPI publishes no maximum batch size, so its receipts show the plan's rate limit instead of a time.

Tweets to look up

Sorsa API

from$14

for 1M tweets

from $0.014 per 1,000 tweets

TwexAPI

$50

for 1M tweets

$0.05 per 1,000 tweets

About 3.5x less on Sorsa API

Seven reasons Sorsa API wins the whole job

  1. Bulk lookups about 3.5x cheaper.

    One Sorsa API request returns 100 tweets or 100 profiles, so 1,000 cost from $0.014, against $0.05 on TwexAPI, which bills every item in a batch.

  2. 100 IDs per request on every plan.

    Sorsa API's batch size is the same on the smallest plan and the largest, while TwexAPI's docs say the input "is limited by your plan’s QPS".

  3. Four times the rate limit of TwexAPI's smallest plans.

    Every Sorsa API plan runs at 20 requests per second, against 5 on TwexAPI's $20, $50 and $100 options and 10 on its $99 and $199 ones.

  4. Free requests that never expire.

    A new Sorsa API account gets 100 requests, enough for up to 10K tweets, with no card and no deadline; TwexAPI's 20K free credits cover about 4,000 items and last 7 days.

  5. Zero risk to your X account.

    Sorsa API has 0 write endpoints and never asks for your X login, while TwexAPI's account actions run on your own logged-in X account.

  6. 99.9% uptime in the contract.

    Section 7.1 of Sorsa API's Terms of Service guarantees it on every paid plan; TwexAPI's Terms say they do not guarantee "the continuity, accuracy, or reliability of the service".

  7. In production since 2022.

    Sorsa API started as TweetScout API in 2022; TwexAPI's site was first archived in July 2025, under the name TwitterXAPI.

Four jobs, two receipts each

Rehydrate 1M tweet IDs

A research team holds 1M tweet IDs from a published dataset and needs every tweet back with its author.

Sorsa API

Total: from $14

  • 10K requests to POST /tweet-info-bulk, 100 IDs eachfrom $14
  • Time at 20 requests per secondabout 8 minutes
  • Fits inthe 10K-request Starter plan

IDs per request100 on every plan

TwexAPI

Total: $50

  • 1M tweets at 5 credits each5M credits, $50
  • IDs per requestlimited by the plan's QPS
  • Rate limit on its $50 plan5 requests per second

IDs per requestset by the plan's QPS

Refresh 100K lead profiles every week

A sales team re-reads 100K X profiles every Monday to keep follower counts and bios current in its CRM.

Sorsa API

Total: from $5.60

  • 4K requests a month, 1K per refresh at 100 profiles eachfrom $5.60
  • Time per refresh at 20 requests per secondabout 50 seconds

Price fixed while you stay subscribedyes

TwexAPI

Total: $20

  • 400K profiles a month at 5 credits each2M credits, $20
  • Rate limit on its $20 to $100 options5 requests per second

Price fixed while you stay subscribedno promise in its terms

Give an AI agent read access to X

An agent in Claude, Cursor or your own code searches posts, reads profiles and runs checks with nobody watching each call.

Sorsa API

Total: 40 read-only tools

  • Installnpx -y sorsa-mcp
  • What the key can doread public data
  • Write toolsnone

Can post as your X accountno

TwexAPI

Total: 3 tools

  • Its posting toollabelled "Destructive, not idempotent"
  • What the agent can do with your login addedpost, reply, like and send DMs

Can post as your X accountyes, once your login is added

Test before you pay

You want to run your own job on your own data before you buy anything.

Sorsa API

Total: 100 free requests

  • Cardnot needed
  • Tweets they coverup to 10K
  • Expirynever

Needs your X loginno

TwexAPI

Total: 20K free credits

  • Cardnot needed
  • Posts or profiles they coverabout 4,000
  • Expiry7 days
  • Rate limit1 request every 5 seconds

Needs your X loginonly for account actions

Ten checks, with values on both sides

The first eight checks come from how to choose an X data API; the last two read the contract. The one tie: both sides sign a custom SLA for large volumes, and on Sorsa API it starts at 1M requests a month.

10 of 10 Sorsa API1 of 10 TwexAPI

Sorsa API passes all ten checks; TwexAPI passes one.

  • Price per 1,000 results

    Sorsa API
    from $0.014 per 1,000 tweets
    TwexAPI
    $0.05 per 1,000 tweets

  • Batch lookups

    Sorsa API
    100 tweets for one request
    TwexAPI
    size capped by plan QPS

  • Rate limit on the smallest paid plan

    Sorsa API
    20 requests per second
    TwexAPI
    5 requests per second

  • A free test with no deadline

    Sorsa API
    100 requests, never expire
    TwexAPI
    20K credits for 7 days

  • What it needs from your X account

    Sorsa API
    nothing: read-only
    TwexAPI
    your X login for actions
The other 5 checks

  • Track record and a stable schema

    Sorsa API
    since 2022, one user schema
    TwexAPI
    since 2025, two user schemas

  • Checks for every campaign step

    Sorsa API
    five verification checks
    TwexAPI
    no verification checks

  • A predictable bill

    Sorsa API
    one request for any call
    TwexAPI
    credit cost varies by endpoint

  • A guarantee in the terms

    Sorsa API
    99.9% uptime, a price lock
    TwexAPI
    no continuity guarantee

  • A contract for serious volume

    Sorsa API
    an SLA from 1M a month
    TwexAPI
    a custom SLA on request

What a TwexAPI key can do with your X login added

Give a Sorsa API key to an agent or a contractor, and the most it can do is read public data.

Sorsa API key

  • reads public posts, profiles, followers, Lists, Communities, Spaces and X Articles
  • has no write endpoints, so it can't post, like, follow or send DMs
  • never asks for your X login

TwexAPI key, with your X login added to a request

  • posts tweets, replies, threads and quote posts, and deletes tweets
  • likes, retweets and bookmarks posts
  • follows, unfollows and blocks accounts
  • sends DMs and reads your DM history
  • changes your profile's bio, image and banner

Source: TwexAPI, "API Overview" (opens in a new tab)

For AI agents: 40 read-only tools against 3

TwexAPI reads public data with its API key alone, and its account actions are a second product on the same key: each write request carries the session of the X account it acts as, and TwexAPI's Terms say that for every write "users must authenticate using their own Twitter session credentials". Sorsa API has no such product, so its key has nothing to act on.

TwexAPI's MCP server brings those writes to agents. It has three tools: explore searches its catalog, twexapi_request calls a read endpoint and twexapi_write posts a tweet or a reply from your X account. TwexAPI labels the write tool "Destructive, not idempotent", and its docs warn that the account credential it takes "gives full control of that X account, and it passes through the AI client and its conversation history."

Sorsa API's MCP server gives an agent 40 tools, each named for one job, and none of them can write:

  • Tools

    Sorsa API MCP server
    40, one per job
    TwexAPI MCP server
    3: explore, read, write

  • Write tools

    Sorsa API MCP server
    none
    TwexAPI MCP server
    posting from your X account

  • Batches

    Sorsa API MCP server
    100 tweets or profiles per call
    TwexAPI MCP server
    limited by the plan's QPS

  • Verification checks

    Sorsa API MCP server
    follow, retweet, quote, comment, Community
    TwexAPI MCP server
    none

  • Spaces

    Sorsa API MCP server
    yes
    TwexAPI MCP server
    no endpoint

The server installs with npx -y sorsa-mcp from npm and is listed in the official MCP Registry. The Twitter MCP server page has the setup for Claude, Cursor and other clients, and the Twitter MCP server guide explains how an agent uses it.

TwexAPI's terms in its own words

We read TwexAPI's Terms of Service (last updated September 3, 2026), its Privacy Policy and its pricing page in full. The Terms and the Privacy Policy name no company, no address and no governing law; their only contact is an email address. Sorsa API's Terms open with the company behind them, Scouts Labs Inc, and its registered office. TwexAPI's pricing page lists an uptime SLA claim on its paid plans, and its Terms say otherwise:

In production since 2022

The Wayback Machine first archived TwexAPI's site on July 14, 2025, at twitterxapi.com, and twexapi.io was registered on August 3, 2025. Sorsa API had been in production for about three years by then, as TweetScout API. Its response schema stays the same as the API grows: one user object, with the same field names, in tweets, profile lookups and follower lists. TwexAPI's API reference documents two: its follower lists return userId and followersCount, while its tweets and profile lookups return id, screen_name and followers_count.

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed in 2025

  2. 2025

    TwexAPI

    first archived in July 2025 as TwitterXAPI

Switch from TwexAPI: endpoints and fields

Send your key in the ApiKey header to https://api.sorsa.io/v3 instead of a Bearer token to https://api.twexapi.io. Every read below has a Sorsa API endpoint; Sorsa API is read-only by design, so to post, pair it with the official X API.

  • POST /twitter/tweets/lookup

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

  • POST /twitter/users/by_ids, POST /twitter/users

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

  • POST /twitter/followers/page

    Sorsa API
    GET /followers
    Note
    200 per page, by handle, ID or link

  • POST /twitter/following/page

    Sorsa API
    GET /follows
    Note
    200 per page

  • POST /v3/twitter/users/verified-followers

    Sorsa API
    GET /verified-followers

  • POST /twitter/advanced_search/page

    Sorsa API
    POST /search-tweets
    Note
    the same X search operators, back to 2006

  • POST /twitter/{screen_name}/timeline/page

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

  • POST /twitter/tweets/{tweet_id}/replies/page

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

  • POST /twitter/tweets/quotes/page

    Sorsa API
    POST /quotes

  • POST /twitter/tweets/retweeters/page

    Sorsa API
    POST /retweeters

  • POST /twitter/list/tweets/page, /twitter/list/members/page

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

  • GET /twitter/community/{community_id}, POST /twitter/community/search

    Sorsa API
    POST /community-info, POST /search-communities

  • POST /twitter/community/members/page, /twitter/community/tweets/page

    Sorsa API
    POST /community-members, POST /community-tweets

  • GET /twitter/{screen_name}/about

    Sorsa API
    GET /about
    Note
    country, username changes, verification

  • POST /x/article

    Sorsa API
    POST /article
    Note
    X Articles with their stats

  • GET /twitter/{country}/trending

    Sorsa API
    GET /trends
    Note
    by location (WOEID)

  • POST /twitter/shadowban/check

    Sorsa API
    GET /check-shadowban

  • GET /balance

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

  • no endpoint

    Sorsa API
    POST /check-follow, POST /check-retweet, POST /check-quoted
    Note
    one request answers each check

  • no endpoint

    Sorsa API
    GET /check-comment, POST /check-community-member
    Note
    one request answers each check

  • no endpoint

    Sorsa API
    GET /spaces
    Note
    a Space's details and stats

  • tweet_id

    Sorsa API field
    id, always a string

  • full_text

    Sorsa API field
    full_text

  • created_at, as "Mon Jun 17 03:51:48 +0000 2024"

    Sorsa API field
    created_at, ISO 8601

  • favorite_count

    Sorsa API field
    likes_count

  • view_count

    Sorsa API field
    view_count

  • user.screen_name in tweets, username in follower lists

    Sorsa API field
    user.username everywhere

  • user.id in tweets, userId in follower lists

    Sorsa API field
    user.id everywhere

  • followers_count in tweets, followersCount in follower lists

    Sorsa API field
    followers_count everywhere

  • following_count, followingCount

    Sorsa API field
    followings_count

  • statuses_count, statusesCount

    Sorsa API field
    tweets_count

  • name

    Sorsa API field
    display_name
adapter.py
import os

import requests

SORSA = "https://api.sorsa.io/v3"
HEADERS = {"ApiKey": os.environ["SORSA_API_KEY"]}


def tweets_by_ids(tweet_ids):
    """Replaces TwexAPI's POST /twitter/tweets/lookup, 100 IDs a request."""
    tweets = []
    for i in range(0, len(tweet_ids), 100):
        body = {"tweet_links": tweet_ids[i:i + 100]}
        r = requests.post(f"{SORSA}/tweet-info-bulk", headers=HEADERS,
                          json=body, timeout=30)
        r.raise_for_status()
        tweets.extend(r.json()["tweets"])
    return tweets


def profiles_by_usernames(usernames):
    """Replaces TwexAPI's POST /twitter/users, 100 usernames a request."""
    users = []
    for i in range(0, len(usernames), 100):
        query = {"usernames": usernames[i:i + 100]}
        r = requests.get(f"{SORSA}/info-batch", headers=HEADERS,
                         params=query, timeout=30)
        r.raise_for_status()
        users.extend(r.json()["users"])
    return users

Both functions return Sorsa API's standard objects: tweets with the full author profile inside each one, and users with the same fields a follower list returns.

Run your own job before you decide

The free requests cover any job above at a small scale, and the docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes. Uptime and security shows how Sorsa API runs and what it keeps. Twitter API alternatives prices TwexAPI next to the rest of the market, and every other head-to-head sits on our Twitter API comparison hub.

Priced as whole jobs, Sorsa API is the stronger pick over TwexAPI: tweets and profiles from $0.014 per 1,000 instead of $0.05, 20 requests per second on every plan, a key that can never act as your X account, and 99.9% uptime written into its terms.

FAQ

Is Sorsa API better than TwexAPI?

Yes. Sorsa API returns 100 tweets or profiles for one request, so 1,000 cost from $0.014 against TwexAPI's $0.05, and every plan runs at 20 requests per second, against 5 on TwexAPI's $20 to $100 options. Its key has no write endpoints, its 100 free requests never expire, and its Terms guarantee 99.9% uptime, where TwexAPI's Terms disclaim the continuity of the service.

How much does TwexAPI cost?

TwexAPI sells credits, $1 per 100K on its standard packs, and charges 5 for each post or profile it returns, so 1,000 cost $0.05, or about $0.042 on its $499 and $999 packs. Credits come as monthly plans at $50 and $99 or one-time packs from $20 to $999, and the $20 pack lasts one day. Sorsa API returns 100 tweets or profiles per request, from $0.014 per 1,000.

Does TwexAPI have a free tier?

Yes: 20K free credits, about 4,000 posts or profiles, with no card. Its pricing page gives them 7 days of validity and a rate of 1 request every 5 seconds. Sorsa API gives every new account 100 free requests with no card and no deadline, enough for up to 10K tweets or 10K profiles through its batch endpoints.

Is TwexAPI the same as TwitterAPI.io?

No. TwexAPI runs at twexapi.io and first went online in 2025 under the name TwitterXAPI; TwitterAPI.io is a separate service at twitterapi.io. Both bill each item they return and sell account actions through an X account you log in with. Sorsa API is read-only and bills the request, and Sorsa API vs TwitterAPI.io puts those two side by side.

Does TwexAPI need my X account?

Not to read public data. Its account actions do: posts, replies, likes, follows and DMs run on your own logged-in X account, so each write request carries that account's session, and its MCP server has a tool that posts. Sorsa API has no write endpoints and never asks for your X login, so the most a leaked key or a runaway agent can do is read public data.

Does TwexAPI guarantee uptime?

Not in its contract. Its pricing page lists an uptime SLA claim on paid plans, but its Terms say "We do not guarantee the continuity, accuracy, or reliability of the service" and exclude liability for any damages. Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms of Service, with bonus requests if a month falls below 99.5%, and signs an SLA from 1M requests a month.

Does TwexAPI have an MCP server for AI agents?

Yes, with three tools: explore, twexapi_request for reads, and twexapi_write, which posts a tweet or reply from your X account and is labelled "Destructive, not idempotent". Sorsa API's MCP server runs with npx -y sorsa-mcp and gives an agent 40 read-only tools, from batches of 100 tweets to five verification checks, at one request per call.

How do I switch from TwexAPI to Sorsa API?

Send your key in the ApiKey header to https://api.sorsa.io/v3, map each read to its Sorsa API endpoint and rename a few fields. Tweets by ID move to POST /tweet-info-bulk and profiles to GET /info-batch, 100 per request, and followers move to GET /followers with 200 per page. Sorsa API has no write endpoints: to post, pair it with the official X API.

Sources

Disclaimers

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

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. TwexAPI's figures come from its own pages, linked above, as seen on the dates shown.

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

Look up 10K tweets 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