Skip to content
Get 100 free requests

Sorsa API vs GetXAPI

Sorsa API is a better choice than GetXAPI: it returns 100 tweets per request, so looking up 1,000 tweets costs from $0.014 instead of $1.00, and its key can never post, like or send a DM as your X account.

Sorsa API

$0.014per 1,000 tweets looked up

99.9%uptime written into the terms

2022first year in production

GetXAPI

$1.00per 1,000 tweets looked up

noneuptime written into the terms

2026first year in production

Short answer: GetXAPI charges $0.001 a call, and its Tweet Detail and User Info calls return one tweet or one profile each, so every 1,000 you look up cost $1.00. Sorsa API has been in production since 2022, reads public data only and guarantees 99.9% uptime in its terms, while GetXAPI launched in February 2026 and its terms rule out liability for losses from downtime. Run your own job on 100 free requests: no card, and they never expire.

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

#Seven reasons Sorsa API comes out ahead

  1. About 70x less for every tweet or profile you look up.

    One Sorsa API request returns 100 tweets or 100 profiles, so 1,000 cost from $0.014; GetXAPI's lookup calls return one each, $1.00 per 1,000.

  2. No X account behind the key.

    Sorsa API has 0 write endpoints and never asks for your X login; GetXAPI's terms say its POST endpoints "require your own Twitter/X authentication tokens".

  3. Four years more in production.

    Sorsa API has run since 2022, first as TweetScout API; GetXAPI's own About page says it launched in February 2026.

  4. Uptime you can hold us to.

    Sorsa API writes 99.9% uptime into Section 7.1 of its Terms on every paid plan; GetXAPI's Terms promise no uptime figure and accept no liability for downtime.

  5. A price that can't rise mid-plan.

    Under Section 8.10 of Sorsa API's Terms, your plan's price never goes up while you stay subscribed; GetXAPI's Terms say its pricing "may change with notice".

  6. An endpoint for every step.

    Sorsa API has 6 check endpoints, a quotes endpoint and one request that reads the tweets of an X List of up to 5,000 accounts; GetXAPI has a follow check and List members only.

  7. 40 MCP tools that can only read.

    Sorsa MCP gives an AI agent 40 read-only tools; GetXAPI's MCP server also carries tools that post, delete tweets and send DMs as a linked X account.

#One tweet per call, or 100 per request

GetXAPI prices the call, and a lookup call carries one item. Its Tweet Detail endpoint takes a single tweet ID and returns a single tweet; its User Info endpoints take one handle or one user ID. A list of 1,000 tweet IDs is therefore 1,000 calls, or $1.00 at its pay-as-you-go rate.

Sorsa API prices the request, and a lookup request carries a batch. POST /tweet-info-bulk takes up to 100 tweet IDs or links, and GET /info-batch takes up to 100 handles or user IDs. The same 1,000 tweets are 10 requests, from $0.014, and each tweet comes with its author's full profile inside.

GetXAPIone tweet per call1,000 calls for 1,000 tweets: $1.00Sorsa API100 tweets per request10010010010010010010010010010010 requests for 1,000 tweets: from $0.014
A lookup is where the two bills part: one tweet per call on GetXAPI, 100 per request on Sorsa API.

Many read pipelines are lookups at heart: refreshing the numbers on posts you track, enriching a list of accounts, rebuilding a dataset from IDs, answering an agent's question about a post it already found. The five jobs below come from that work.

#Five read jobs, priced on both APIs

Rehydrate 1M tweet IDs

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

Sorsa API

Total: from $14

  • 10K requests, 100 tweets eachfrom $14
  • Time at 20 requests per secondabout 8 minutes
  • Author profile in every tweetincluded

Needs your X loginno

GetXAPI

Total: $1,000

  • 1M Tweet Detail calls, one tweet each$1,000
  • Its largest monthly plan$99, about 350K calls

Needs your X loginonly for write actions

Refresh 10K campaign posts every day

A marketing team updates likes, replies, views and bookmarks on 10K campaign posts once a day for a month.

Sorsa API

Total: from $4.20

  • 3K requests a month, 100 posts eachfrom $4.20
  • Time each day at 20 requests per second5 seconds
  • Views and bookmarks in every tweetincluded

Uptime written into the terms99.9%

GetXAPI

Total: $300

  • 300K Tweet Detail calls, one post each$300
  • Price in its Termsmay change with notice

Uptime written into the termsnone

Keep 50K lead profiles fresh weekly

A sales team re-reads follower counts, bios and locations for 50K accounts once a week.

Sorsa API

Total: from $2.80

  • 2K requests a month, 100 profiles eachfrom $2.80
  • Time per refresh at 20 requests per second25 seconds
  • Look up by handle or by user IDboth

Price can rise while you stay subscribednever

GetXAPI

Total: $200

  • 200K User Info calls a month, one profile each$200
  • Liability cap in its Termsthe last 30 days of fees

Price can rise while you stay subscribedwith notice

Track 5,000 accounts through one X List

A newsroom follows 5,000 accounts in one public X List and checks for new posts every hour.

Sorsa API

Total: from $12.60

  • 9K requests a month, 20 tweets a pagefrom $12.60
  • One request covers all 5,000 accountsGET /list-tweets
  • Volume assumed5,500 posts a day, 24 checks

In production since2022

GetXAPI

Total: $360

  • 360K search calls, 10 accounts per query, as its own guide groups them$360
  • An endpoint for a List's tweetsnone

In production since2026

Give an AI agent read access to X

A research agent reads 2,000 posts and 500 profiles a day from IDs it has already found.

Sorsa API

Total: from $1.05

  • 750 requests a month, 100 items eachfrom $1.05
  • MCP tools for the agent40, all read-only
  • What a leaked key can doread public data

What the agent's key can doread public data

GetXAPI

Total: $75

  • 75K lookup calls a month, one item each$75
  • Its MCP write toolspost and message as your X account

What the agent's key can dopost and DM as a linked X account

#Ten checks before you pay for X data

The first seven checks come from how to choose an X data API; the last three are about the contract behind the API.

Sorsa API passes all ten checks; GetXAPI passes two.

CheckSorsa API10 of 10GetXAPI2 of 10
Price per 1,000 tweets looked upfrom $0.014$1.00, one tweet per call
Batch lookups100 tweets or profiles per requestone per call
A free test with no deadline100 requests that never expire$0.10 credit that never expires
What it needs from your X accountnothing: 0 write endpointsyour X login, for its writes
Track recordin production since 2022launched in February 2026
An endpoint for every step6 checks, quotes, List tweetsa follow check; no quotes or List tweets
A predictable billfixed plans and a spending limitper call, with spend alerts
A guarantee in the terms99.9% uptime and a price lockneither in its Terms
A named company behind the termsScouts Labs Inc, in the Termsnone named in its Terms
A contract for serious volumean SLA we sign from 1M a monthlargest plan $99 a month

#What a key can do with your X account behind it

A Sorsa API key has no X account behind it, so a leaked key or a confused agent can only read what anyone can already read on X.

Sorsa API key

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

GetXAPI key, with an X account registered to it

  • posts, edits and deletes tweets
  • likes, retweets and bookmarks
  • follows and unfollows accounts
  • reads and sends DMs
  • changes the profile, avatar and banner

Source: GetXAPI, "Twitter/X MCP Server" (opens in a new tab)

#GetXAPI's Terms, next to Sorsa API's

  • Uptime

    GetXAPI

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

    GetXAPI, getxapi.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 getxapi.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_getxapi_com_terms_of_service

    Sorsa API

    Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms; if a month falls below 99.5%, we add bonus requests worth 10% of your monthly requests.

  • Liability

    GetXAPI

    “limited to the amount you paid in the 30 days preceding the claim”

    GetXAPI, getxapi.com/terms-of-service, seen Nov 3, 2026: "limited to the amount you paid in the 30 days preceding the claim"Full capture
    Seen Nov 3, 2026 on getxapi.com/terms-of-service (opens in a new tab)Evidence 2026-11-03/www_getxapi_com_terms_of_service

    Sorsa API

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

  • Writes

    GetXAPI

    “write tools post and message as your X account”

    GetXAPI, getxapi.com/mcp, seen Nov 3, 2026: "write tools post and message as your X account"Full capture
    Seen Nov 3, 2026 on getxapi.com/mcp (opens in a new tab)Evidence 2026-11-03/www_getxapi_com_mcp

    Sorsa API

    Sorsa API has no write endpoints, so a Sorsa API key can't act as your X account at all.

  • Logging in

    GetXAPI

    “required whenever the account has authenticator-app 2FA”

    GetXAPI, docs.getxapi.com/docs/users/user-login, seen Nov 3, 2026: "required whenever the account has authenticator-app 2FA"Full capture
    Seen Nov 3, 2026 on docs.getxapi.com/docs/users/user-login (opens in a new tab)Evidence 2026-11-03/docs_getxapi_com_docs_users_user_login

    Sorsa API

    Sorsa API never asks for an X password, a two-factor secret or a session.

#Who you sign a contract with

A team that runs X data in production buys a contract along with the API. Here are the two contracts side by side, from each provider's own terms.

Sorsa APIGetXAPI
Party to the termsScouts Labs Incno company named
Governing lawstated in Section 18.2, with arbitrationnot stated
Uptime99.9% on every paid plan, Section 7.1no figure, no liability for downtime
Pricelocked while you stay subscribed, Section 8.10may change with notice
Liability capthe greater of three months of fees or $100the fees of the last 30 days
Serious volumean SLA we sign from 1M requests a monthlargest plan $99 a month

GetXAPI's About page calls it "a small, founder-run product", and its own migration guide says "No third-party Twitter API has a contractual SLA". Sorsa API signs one from 1M requests a month, with an account manager from the Business plan and dedicated infrastructure on Hyperscale. See how it handles uptime and security, or talk to sales about an SLA for your volume.

#Four years in production, against nine months

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed Sorsa API in 2025

  2. 2026

    GetXAPI

    domain registered February 5, 2026; public launch February 9, 2026

#Give an agent X data, not your X account

Sorsa MCP installs with npx -y sorsa-mcp and gives Claude, Cursor or any MCP client 40 tools: search, profiles, followers, Lists, Spaces and the follow, retweet, quote and reply checks. All 40 only read. The server is on npm and in the official MCP Registry, and the Twitter MCP server page has the setup for each client.

GetXAPI's server mixes reads and writes. Its MCP page says read tools run on the API key alone and write tools "post and message as your X account", so an agent holding that key, with an account registered behind it, can post, delete a tweet or send a DM. A Sorsa API key gives an agent nothing of that kind to misuse: the worst a confused agent can do is read a public post.

The Twitter MCP server guide walks through the servers agents use today and how to connect each one.

#What GetXAPI says about Sorsa API, and the facts

GetXAPI's own ranking of alternatives puts Sorsa API seventh. Here are its lines about Sorsa API as we saw them on November 3, 2026, each with the fact.

#Even competitors say it

#GetXAPI pricing, explained

GetXAPI sells calls. A standard call costs $0.001 whatever it brings back, and heavier calls cost $0.002 to $0.010.

That is the catch for lookups. GetXAPI's per-1,000-tweet headline assumes a full page of about 20 results per call, but its Tweet Detail and User Info calls carry one item each, so every 1,000 tweets or profiles you already have IDs for cost 1,000 calls: $1.00 at pay as you go.

Plans change the rate, not the number of calls. Pro at $15 a month buys $30 of credit, which is $0.50 per 1,000 calls; Growth at $49 buys $120, or $0.41; Scale at $99 buys $300, or $0.33. Paying in crypto adds $10, $20 or $50 of credit, which brings Scale to about $0.28 per 1,000 calls. A one-time $5 Starter pack buys $4.50 of credit for 30 days, which is $1.11 per 1,000 calls. Past the $99 plan, GetXAPI asks you to contact it.

Even at its best rate, 1,000 lookups cost about $0.28 on GetXAPI, 20 times Sorsa API's from $0.014, because Sorsa API charges one request for a batch of 100.

Tweets to look up

Sorsa API

from$14

for 1M tweets

from $0.014 per 1,000 tweets

GetXAPI

$1,000

for 1M tweets

$1.00 per 1,000 tweets looked up

About 70x less on Sorsa API

#Moving your reads off GetXAPI

Every GetXAPI read below has a Sorsa API endpoint. Send your key in the ApiKey header to https://api.sorsa.io/v3 instead of a Bearer token; the rest is field names.

GetXAPISorsa APINote
GET /twitter​/tweet​/detailPOST /tweet-info-bulk100 tweet IDs or links per request
GET /twitter​/user​/info, /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 /mentionslikes, replies and date filters
GET /twitter​/tweet​/repliesPOST /commentsby relevance, recency or likes
GET /twitter​/tweet​/retweetersPOST /retweeters
GET /twitter​/user​/followersGET /followersup to 200 per page
GET /twitter​/user​/user_aboutGET /about
GET /twitter​/list​/membersGET /list-membersadd GET /list-tweets for the List's tweets
GET /twitter​/user​/check_follow_relationshipPOST /check-follow
GET /twitter​/spaces​/infoGET /spaces
GET /twitter​/trendsGET /trendsby WOEID
GET /twitter​/article​/getPOST /article
GET /account​/meGET /key-usage-infofree: it never counts against your requests
GetXAPI fieldSorsa API field
textfull_text
authoruser, the full profile
likeCount, retweetCount, viewCountlikes_count, retweet_count, view_count
createdAtcreated_at, in ISO 8601
next_cursor with has_morenext_cursor, missing or null on the last page
Terminal
curl -X POST "https://api.sorsa.io/v3/tweet-info-bulk" \
  -H "ApiKey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tweet_links": ["1234567890123456789", "1234567890123456790"]}'

#Start with the job you priced

Pick one of the five jobs and run it on the free requests: the docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes. Sorsa API is read-only by design, so your X account is never at risk; to publish posts, pair it with the official X API. The wider field is in Twitter API alternatives, and every other head-to-head sits on the Twitter API comparison hub.

#FAQ

Is Sorsa API better than GetXAPI?

Yes. Sorsa API returns 100 tweets or profiles per request, so 1,000 lookups cost from $0.014 against $1.00 on GetXAPI, which returns one per call. Sorsa API is read-only, so no X account sits behind its key. It has been in production since 2022 and guarantees 99.9% uptime on every paid plan in its Terms. GetXAPI launched in February 2026, and its Terms accept no liability for downtime.

What is the best GetXAPI alternative?

Sorsa API. It covers GetXAPI's public reads and adds what GetXAPI has no endpoint for: 100-item batch lookups, quote tweets, the tweets of an X List of up to 5,000 accounts, and checks for retweets, quotes, replies and Community membership. Its MCP server gives agents 40 read-only tools. Moving takes an endpoint map, a new header and new field names, and 100 free requests cover the test.

Does GetXAPI guarantee uptime?

No. GetXAPI's Terms name no uptime figure, say it is "not liable for any losses caused by downtime", and cap its liability at the fees you paid in the last 30 days. Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms, adds bonus requests if a month falls below 99.5%, and caps its liability at the greater of three months of fees or $100.

When did GetXAPI launch?

In February 2026. GetXAPI's About page says "Launched February 2026", its changelog dates the public launch to February 9, 2026, and the domain was registered on February 5, 2026. Sorsa API has been in production since 2022, when it launched as TweetScout API, and it was renamed Sorsa API in 2025.

Does Sorsa API need my X account or login?

No. Sorsa API has no write endpoints, so it never asks for your X login, password, two-factor secret or session, and its key can only read public data. GetXAPI's Terms say its POST endpoints "require your own Twitter/X authentication tokens", and its MCP page says its write tools post and message as your X account.

Can an AI agent use Sorsa API safely?

Yes. Sorsa MCP gives an agent 40 tools, and every one of them only reads: search, profiles, followers, Lists, Spaces and the engagement checks. Install it with npx -y sorsa-mcp in Claude, Cursor or any MCP client. Because the key has no X account behind it, an agent that misreads a prompt still can't post, follow or send a DM.

How do I move from GetXAPI to Sorsa API?

Map each call to its Sorsa API endpoint and send your key in the ApiKey header instead of a Bearer token. Tweet Detail lookups move to POST /tweet-info-bulk with 100 IDs per request, User Info to GET /info-batch, and advanced search to POST /search-tweets with the same operators. Responses carry next_cursor until the last page, and every tweet includes its author's full profile.

#Sources

Disclaimers

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

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. GetXAPI'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 GetXAPI

Sorsa API is a better choice than GetXAPI: it returns 100 tweets per request, so looking up 1,000 tweets costs from $0.014 instead of $1.00, and its key can never post, like or send a DM as your X account.

Sorsa API

$0.014per 1,000 tweets looked up

99.9%uptime written into the terms

2022first year in production

GetXAPI

$1.00per 1,000 tweets looked up

noneuptime written into the terms

2026first year in production

Short answer: GetXAPI charges $0.001 a call, and its Tweet Detail and User Info calls return one tweet or one profile each, so every 1,000 you look up cost $1.00. Sorsa API has been in production since 2022, reads public data only and guarantees 99.9% uptime in its terms, while GetXAPI launched in February 2026 and its terms rule out liability for losses from downtime. Run your own job on 100 free requests: no card, and they never expire.

Updated , 11 min read

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

Seven reasons Sorsa API comes out ahead

  1. About 70x less for every tweet or profile you look up.

    One Sorsa API request returns 100 tweets or 100 profiles, so 1,000 cost from $0.014; GetXAPI's lookup calls return one each, $1.00 per 1,000.

  2. No X account behind the key.

    Sorsa API has 0 write endpoints and never asks for your X login; GetXAPI's terms say its POST endpoints "require your own Twitter/X authentication tokens".

  3. Four years more in production.

    Sorsa API has run since 2022, first as TweetScout API; GetXAPI's own About page says it launched in February 2026.

  4. Uptime you can hold us to.

    Sorsa API writes 99.9% uptime into Section 7.1 of its Terms on every paid plan; GetXAPI's Terms promise no uptime figure and accept no liability for downtime.

  5. A price that can't rise mid-plan.

    Under Section 8.10 of Sorsa API's Terms, your plan's price never goes up while you stay subscribed; GetXAPI's Terms say its pricing "may change with notice".

  6. An endpoint for every step.

    Sorsa API has 6 check endpoints, a quotes endpoint and one request that reads the tweets of an X List of up to 5,000 accounts; GetXAPI has a follow check and List members only.

  7. 40 MCP tools that can only read.

    Sorsa MCP gives an AI agent 40 read-only tools; GetXAPI's MCP server also carries tools that post, delete tweets and send DMs as a linked X account.

One tweet per call, or 100 per request

GetXAPI prices the call, and a lookup call carries one item. Its Tweet Detail endpoint takes a single tweet ID and returns a single tweet; its User Info endpoints take one handle or one user ID. A list of 1,000 tweet IDs is therefore 1,000 calls, or $1.00 at its pay-as-you-go rate.

Sorsa API prices the request, and a lookup request carries a batch. POST /tweet-info-bulk takes up to 100 tweet IDs or links, and GET /info-batch takes up to 100 handles or user IDs. The same 1,000 tweets are 10 requests, from $0.014, and each tweet comes with its author's full profile inside.

GetXAPI one tweet per call 1,000 calls for 1,000 tweets: $1.00 Sorsa API 100 tweets per request 100 100 100 100 100 100 100 100 100 100 10 requests for 1,000 tweets: from $0.014
A lookup is where the two bills part: one tweet per call on GetXAPI, 100 per request on Sorsa API.

Many read pipelines are lookups at heart: refreshing the numbers on posts you track, enriching a list of accounts, rebuilding a dataset from IDs, answering an agent's question about a post it already found. The five jobs below come from that work.

Five read jobs, priced on both APIs

Rehydrate 1M tweet IDs

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

Sorsa API

Total: from $14

  • 10K requests, 100 tweets eachfrom $14
  • Time at 20 requests per secondabout 8 minutes
  • Author profile in every tweetincluded

Needs your X loginno

GetXAPI

Total: $1,000

  • 1M Tweet Detail calls, one tweet each$1,000
  • Its largest monthly plan$99, about 350K calls

Needs your X loginonly for write actions

Refresh 10K campaign posts every day

A marketing team updates likes, replies, views and bookmarks on 10K campaign posts once a day for a month.

Sorsa API

Total: from $4.20

  • 3K requests a month, 100 posts eachfrom $4.20
  • Time each day at 20 requests per second5 seconds
  • Views and bookmarks in every tweetincluded

Uptime written into the terms99.9%

GetXAPI

Total: $300

  • 300K Tweet Detail calls, one post each$300
  • Price in its Termsmay change with notice

Uptime written into the termsnone

Keep 50K lead profiles fresh weekly

A sales team re-reads follower counts, bios and locations for 50K accounts once a week.

Sorsa API

Total: from $2.80

  • 2K requests a month, 100 profiles eachfrom $2.80
  • Time per refresh at 20 requests per second25 seconds
  • Look up by handle or by user IDboth

Price can rise while you stay subscribednever

GetXAPI

Total: $200

  • 200K User Info calls a month, one profile each$200
  • Liability cap in its Termsthe last 30 days of fees

Price can rise while you stay subscribedwith notice

Track 5,000 accounts through one X List

A newsroom follows 5,000 accounts in one public X List and checks for new posts every hour.

Sorsa API

Total: from $12.60

  • 9K requests a month, 20 tweets a pagefrom $12.60
  • One request covers all 5,000 accountsGET /list-tweets
  • Volume assumed5,500 posts a day, 24 checks

In production since2022

GetXAPI

Total: $360

  • 360K search calls, 10 accounts per query, as its own guide groups them$360
  • An endpoint for a List's tweetsnone

In production since2026

Give an AI agent read access to X

A research agent reads 2,000 posts and 500 profiles a day from IDs it has already found.

Sorsa API

Total: from $1.05

  • 750 requests a month, 100 items eachfrom $1.05
  • MCP tools for the agent40, all read-only
  • What a leaked key can doread public data

What the agent's key can doread public data

GetXAPI

Total: $75

  • 75K lookup calls a month, one item each$75
  • Its MCP write toolspost and message as your X account

What the agent's key can dopost and DM as a linked X account

Ten checks before you pay for X data

The first seven checks come from how to choose an X data API; the last three are about the contract behind the API.

10 of 10 Sorsa API2 of 10 GetXAPI

Sorsa API passes all ten checks; GetXAPI passes two.

  • Price per 1,000 tweets looked up

    Sorsa API
    from $0.014
    GetXAPI
    $1.00, one tweet per call

  • Batch lookups

    Sorsa API
    100 tweets or profiles per request
    GetXAPI
    one per call

  • A free test with no deadline

    Sorsa API
    100 requests that never expire
    GetXAPI
    $0.10 credit that never expires

  • What it needs from your X account

    Sorsa API
    nothing: 0 write endpoints
    GetXAPI
    your X login, for its writes

  • Track record

    Sorsa API
    in production since 2022
    GetXAPI
    launched in February 2026
The other 5 checks

  • An endpoint for every step

    Sorsa API
    6 checks, quotes, List tweets
    GetXAPI
    a follow check; no quotes or List tweets

  • A predictable bill

    Sorsa API
    fixed plans and a spending limit
    GetXAPI
    per call, with spend alerts

  • A guarantee in the terms

    Sorsa API
    99.9% uptime and a price lock
    GetXAPI
    neither in its Terms

  • A named company behind the terms

    Sorsa API
    Scouts Labs Inc, in the Terms
    GetXAPI
    none named in its Terms

  • A contract for serious volume

    Sorsa API
    an SLA we sign from 1M a month
    GetXAPI
    largest plan $99 a month

What a key can do with your X account behind it

A Sorsa API key has no X account behind it, so a leaked key or a confused agent can only read what anyone can already read on X.

Sorsa API key

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

GetXAPI key, with an X account registered to it

  • posts, edits and deletes tweets
  • likes, retweets and bookmarks
  • follows and unfollows accounts
  • reads and sends DMs
  • changes the profile, avatar and banner

Source: GetXAPI, "Twitter/X MCP Server" (opens in a new tab)

GetXAPI's Terms, next to Sorsa API's

  • Uptime

    GetXAPI

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

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

    Sorsa API

    Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms; if a month falls below 99.5%, we add bonus requests worth 10% of your monthly requests.

  • Liability

    GetXAPI

    “limited to the amount you paid in the 30 days preceding the claim”

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

    Sorsa API

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

  • Writes

    GetXAPI

    “write tools post and message as your X account”

    GetXAPI, getxapi.com/mcp, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on getxapi.com/mcp (opens in a new tab)Evidence 2026-11-03/www_getxapi_com_mcp

    Sorsa API

    Sorsa API has no write endpoints, so a Sorsa API key can't act as your X account at all.

  • Logging in

    GetXAPI

    “required whenever the account has authenticator-app 2FA”

    GetXAPI, docs.getxapi.com/docs/users/user-login, seen Nov 3, 2026: Full capture
    Seen Nov 3, 2026 on docs.getxapi.com/docs/users/user-login (opens in a new tab)Evidence 2026-11-03/docs_getxapi_com_docs_users_user_login

    Sorsa API

    Sorsa API never asks for an X password, a two-factor secret or a session.

Who you sign a contract with

A team that runs X data in production buys a contract along with the API. Here are the two contracts side by side, from each provider's own terms.

  • Party to the terms

    Sorsa API
    Scouts Labs Inc
    GetXAPI
    no company named

  • Governing law

    Sorsa API
    stated in Section 18.2, with arbitration
    GetXAPI
    not stated

  • Uptime

    Sorsa API
    99.9% on every paid plan, Section 7.1
    GetXAPI
    no figure, no liability for downtime

  • Price

    Sorsa API
    locked while you stay subscribed, Section 8.10
    GetXAPI
    may change with notice

  • Liability cap

    Sorsa API
    the greater of three months of fees or $100
    GetXAPI
    the fees of the last 30 days

  • Serious volume

    Sorsa API
    an SLA we sign from 1M requests a month
    GetXAPI
    largest plan $99 a month

GetXAPI's About page calls it "a small, founder-run product", and its own migration guide says "No third-party Twitter API has a contractual SLA". Sorsa API signs one from 1M requests a month, with an account manager from the Business plan and dedicated infrastructure on Hyperscale. See how it handles uptime and security, or talk to sales about an SLA for your volume.

Four years in production, against nine months

  1. 2022

    Sorsa API

    launched as TweetScout API, renamed Sorsa API in 2025

  2. 2026

    GetXAPI

    domain registered February 5, 2026; public launch February 9, 2026

Give an agent X data, not your X account

Sorsa MCP installs with npx -y sorsa-mcp and gives Claude, Cursor or any MCP client 40 tools: search, profiles, followers, Lists, Spaces and the follow, retweet, quote and reply checks. All 40 only read. The server is on npm and in the official MCP Registry, and the Twitter MCP server page has the setup for each client.

GetXAPI's server mixes reads and writes. Its MCP page says read tools run on the API key alone and write tools "post and message as your X account", so an agent holding that key, with an account registered behind it, can post, delete a tweet or send a DM. A Sorsa API key gives an agent nothing of that kind to misuse: the worst a confused agent can do is read a public post.

The Twitter MCP server guide walks through the servers agents use today and how to connect each one.

What GetXAPI says about Sorsa API, and the facts

GetXAPI's own ranking of alternatives puts Sorsa API seventh. Here are its lines about Sorsa API as we saw them on November 3, 2026, each with the fact.

Even competitors say it

GetXAPI pricing, explained

GetXAPI sells calls. A standard call costs $0.001 whatever it brings back, and heavier calls cost $0.002 to $0.010.

That is the catch for lookups. GetXAPI's per-1,000-tweet headline assumes a full page of about 20 results per call, but its Tweet Detail and User Info calls carry one item each, so every 1,000 tweets or profiles you already have IDs for cost 1,000 calls: $1.00 at pay as you go.

Plans change the rate, not the number of calls. Pro at $15 a month buys $30 of credit, which is $0.50 per 1,000 calls; Growth at $49 buys $120, or $0.41; Scale at $99 buys $300, or $0.33. Paying in crypto adds $10, $20 or $50 of credit, which brings Scale to about $0.28 per 1,000 calls. A one-time $5 Starter pack buys $4.50 of credit for 30 days, which is $1.11 per 1,000 calls. Past the $99 plan, GetXAPI asks you to contact it.

Even at its best rate, 1,000 lookups cost about $0.28 on GetXAPI, 20 times Sorsa API's from $0.014, because Sorsa API charges one request for a batch of 100.

Tweets to look up

Sorsa API

from$14

for 1M tweets

from $0.014 per 1,000 tweets

GetXAPI

$1,000

for 1M tweets

$1.00 per 1,000 tweets looked up

About 70x less on Sorsa API

Moving your reads off GetXAPI

Every GetXAPI read below has a Sorsa API endpoint. Send your key in the ApiKey header to https://api.sorsa.io/v3 instead of a Bearer token; the rest is field names.

  • GET /twitter/tweet/detail

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

  • GET /twitter/user/info, /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
    likes, replies and date filters

  • GET /twitter/tweet/replies

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

  • 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/user_about

    Sorsa API
    GET /about

  • GET /twitter/list/members

    Sorsa API
    GET /list-members
    Note
    add GET /list-tweets for the List's tweets

  • GET /twitter/user/check_follow_relationship

    Sorsa API
    POST /check-follow

  • GET /twitter/spaces/info

    Sorsa API
    GET /spaces

  • GET /twitter/trends

    Sorsa API
    GET /trends
    Note
    by WOEID

  • GET /twitter/article/get

    Sorsa API
    POST /article

  • GET /account/me

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

  • text

    Sorsa API field
    full_text

  • author

    Sorsa API field
    user, the full profile

  • likeCount, retweetCount, viewCount

    Sorsa API field
    likes_count, retweet_count, view_count

  • createdAt

    Sorsa API field
    created_at, in ISO 8601

  • next_cursor with has_more

    Sorsa API field
    next_cursor, missing or null on the last page
Terminal
curl -X POST "https://api.sorsa.io/v3/tweet-info-bulk" \
  -H "ApiKey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tweet_links": ["1234567890123456789", "1234567890123456790"]}'

Start with the job you priced

Pick one of the five jobs and run it on the free requests: the docs quickstart (opens in a new tab) takes a new key to its first response in about three minutes. Sorsa API is read-only by design, so your X account is never at risk; to publish posts, pair it with the official X API. The wider field is in Twitter API alternatives, and every other head-to-head sits on the Twitter API comparison hub.

FAQ

Is Sorsa API better than GetXAPI?

Yes. Sorsa API returns 100 tweets or profiles per request, so 1,000 lookups cost from $0.014 against $1.00 on GetXAPI, which returns one per call. Sorsa API is read-only, so no X account sits behind its key. It has been in production since 2022 and guarantees 99.9% uptime on every paid plan in its Terms. GetXAPI launched in February 2026, and its Terms accept no liability for downtime.

What is the best GetXAPI alternative?

Sorsa API. It covers GetXAPI's public reads and adds what GetXAPI has no endpoint for: 100-item batch lookups, quote tweets, the tweets of an X List of up to 5,000 accounts, and checks for retweets, quotes, replies and Community membership. Its MCP server gives agents 40 read-only tools. Moving takes an endpoint map, a new header and new field names, and 100 free requests cover the test.

Does GetXAPI guarantee uptime?

No. GetXAPI's Terms name no uptime figure, say it is "not liable for any losses caused by downtime", and cap its liability at the fees you paid in the last 30 days. Sorsa API guarantees 99.9% uptime on every paid plan in Section 7.1 of its Terms, adds bonus requests if a month falls below 99.5%, and caps its liability at the greater of three months of fees or $100.

When did GetXAPI launch?

In February 2026. GetXAPI's About page says "Launched February 2026", its changelog dates the public launch to February 9, 2026, and the domain was registered on February 5, 2026. Sorsa API has been in production since 2022, when it launched as TweetScout API, and it was renamed Sorsa API in 2025.

Does Sorsa API need my X account or login?

No. Sorsa API has no write endpoints, so it never asks for your X login, password, two-factor secret or session, and its key can only read public data. GetXAPI's Terms say its POST endpoints "require your own Twitter/X authentication tokens", and its MCP page says its write tools post and message as your X account.

Can an AI agent use Sorsa API safely?

Yes. Sorsa MCP gives an agent 40 tools, and every one of them only reads: search, profiles, followers, Lists, Spaces and the engagement checks. Install it with npx -y sorsa-mcp in Claude, Cursor or any MCP client. Because the key has no X account behind it, an agent that misreads a prompt still can't post, follow or send a DM.

How do I move from GetXAPI to Sorsa API?

Map each call to its Sorsa API endpoint and send your key in the ApiKey header instead of a Bearer token. Tweet Detail lookups move to POST /tweet-info-bulk with 100 IDs per request, User Info to GET /info-batch, and advanced search to POST /search-tweets with the same operators. Responses carry next_cursor until the last page, and every tweet includes its author's full profile.

Sources

Disclaimers

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

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. GetXAPI'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 or profiles 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