Sorsa
Sorsa Labs operates a real-time X (Twitter) data API providing developers access to tweets, profiles, search, mentions, lists, communities, engagement verification, and Sorsa Score crypto-influence analytics through 40 REST endpoints. It markets itself as an affordable alternative to the official X API and was formerly known as Tweetscout.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Sorsa the way a machine reads it — 80 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sorsa scores 61.4/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Sorsa
Each block below is one kind of artifact we hold for Sorsa. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sorsa Community API
Twitter/X Community tweets, members, and community search
Sorsa Lists API
Twitter/X List tweets, members, and followers
Sorsa Search API
Search tweets, users, mentions, and Twitter Spaces (Places)
Sorsa Sorsa Info Crypto Related API
The Sorsa Info Crypto Related API from Sorsa — 7 operation(s) for sorsa info crypto related.
Sorsa Technical Endpoints API
The Technical Endpoints API from Sorsa — 4 operation(s) for technical endpoints.
Sorsa Tweets API
Tweet data (single and batch), articles, user timelines, quotes, retweets, comments, trends
Sorsa Users Data API
User profile, followers, following, verified followers, About metadata
Sorsa Verification API
Verify follow, comment, retweet, quote and community-membership relationships
Scroll within the panel for all 8 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Sorsa API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Sorsa Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sorsa Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sorsa Finops
FINOPSFeatures 12
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Real-Time X (Twitter) Data
Live tweet, profile, follower, and engagement data pulled directly from X.
Simple API Key Authentication
One `ApiKey` header — no OAuth flow, bearer rotation, or callback URLs.
Batch Endpoints
Bulk profile and tweet endpoints accept up to 100 items per request for cost efficiency.
Advanced Search Operators
Mirrors X advanced-search syntax (`from:`, `to:`, `since:`, `until:`, phrase and hashtag operators).
Mentions Tracking
Filterable mentions feed with minimum likes/replies/retweets and date-range filters.
Lists and Communities Coverage
Read List feeds, List members and followers, plus Community feeds, members, and in-community search.
Engagement Verification
Check follow, comment, retweet, quote, and community-membership relationships with boolean responses.
Sorsa Score Crypto Analytics
Influence score among crypto influencers, projects, and VCs, with 7-day/30-day deltas and top-follower lists.
Follower Category Breakdown
Categorize an account's followers into influencers, projects, and venture capital employees.
ID and Handle Utilities
Convert between usernames and stable numeric user IDs; parse profile URLs to user IDs.
Key Usage Visibility
The /key-usage-info endpoint reports total allocated requests, remaining balance, and quota expiration.
Flat-Rate Pricing
1 API call = 1 request from the quota, regardless of which endpoint is hit.
Scroll within the panel for all 12 ·
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Sorsa Context
JSON-LDSorsa Security Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Sorsa API Rules
SPECTRALSorsa API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CommunityUser
JSON SCHEMAFollower
JSON SCHEMAPlace
JSON SCHEMATopFollower
JSON SCHEMATrend
JSON SCHEMATweetEntity
JSON SCHEMATweet
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Sorsa Community User Structure
JSON STRUCTURESorsa Follower Structure
JSON STRUCTURESorsa Place Structure
JSON STRUCTURESorsa Top Follower Structure
JSON STRUCTURESorsa Trend Structure
JSON STRUCTURESorsa Tweet Entity Structure
JSON STRUCTURESorsa Tweet Structure
JSON STRUCTURESorsa User Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 18
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Sorsa Check Follow Example
EXAMPLESorsa Community User Example
EXAMPLESorsa Follower Example
EXAMPLESorsa Followers Example
EXAMPLESorsa Follows Example
EXAMPLESorsa Info Example
EXAMPLESorsa Key Usage Info Example
EXAMPLESorsa Mentions Example
EXAMPLESorsa Place Example
EXAMPLESorsa Score Example
EXAMPLESorsa Search Tweets Example
EXAMPLESorsa Top Follower Example
EXAMPLESorsa Trend Example
EXAMPLESorsa Tweet Entity Example
EXAMPLESorsa Tweet Example
EXAMPLESorsa Tweet Info Example
EXAMPLESorsa User Example
EXAMPLEScroll within the panel for all 18 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Crypto Twitter Intelligence
Track crypto influencers, projects, and VC activity in real time.
Marketing Campaign Verification
Verify follows, likes, retweets, quotes, and community membership for airdrop or campaign rules.
Audience Geography Analysis
Combine About metadata and follower categories to map audience composition.
Competitor Analysis
Compare follower growth, Sorsa Score, and top-follower overlap between accounts.
Mention Monitoring
Real-time alerting on @-mentions filtered by engagement thresholds and date ranges.
Target Audience Discovery
Find high-Sorsa-Score followers and following relationships to seed outreach lists.
Migration from Official X API
Drop-in replacement for read-only X API workflows at a fraction of the cost.
Trend Surveillance
Pull trending topics by WOEID for region-specific monitoring.
Scroll within the panel for all 8 ·
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
X (Twitter)
Primary upstream data source — Sorsa surfaces public X data via REST.
Discord
Community and support channel for developers using Sorsa.
Webhooks (planned)
Documentation references real-time monitoring patterns built on polling today.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Starter
10,000 monthly requests at $49/mo — entry tier for individual developers.
Pro
100,000 monthly requests at $199/mo — for production integrations and agencies.
Enterprise
500,000 monthly requests at $899/mo — for high-volume crypto-intel platforms.
Custom
Volume arrangements beyond 500K monthly requests via [email protected] with dedicated rate-limit profiles.
Resources
Every other property we hold for Sorsa — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sorsa · machine-readable index on apis.io