Social account intelligence,as an API
Verify that an account is real, read how it grew, measure what its audience actually does, and enrich a list of handles at volume. One contract across X, Instagram, TikTok, YouTube, Telegram, Bluesky and LinkedIn.
The data comes from crawlers we run and a catalog we own, not from reselling somebody else's feed. That is why a directory read is cheap enough to page through and a live check is fast enough to sit in a signup flow.
1,000 requests a month on the free plan. No card, no sales call.
curl "https://api.playersells.com/v2/directory/x/elonmusk" \
-H "Authorization: Bearer $PLAYERSELLS_API_KEY"{
"data": {
"platform": "x",
"handle": "elonmusk",
"display_name": "Elon Musk",
"followers": 221084193,
"verified": true,
"created_at": "2009-06-02T20:12:29Z",
"last_seen_at": "2026-08-30T04:11:07Z"
},
"meta": {
"request_id": "req_9f1c2d7a4b6e0813",
"generated_at": "2026-08-30T04:12:55Z",
"took_ms": 31,
"source": "catalog",
"cache_age_s": 108
}
}One API, seven platforms
Each platform has its own crawler, its own catalog and its own quirks, and we have already paid the cost of learning them. What reaches you is one contract: same key, same envelope, same error codes, whichever network you are reading.
What you can ask it
Every endpoint answers in the same envelope, authenticates with the same key and paginates with the same cursor. Learn one, and you have learned all of them.
Accounts
Check one account, on any of the seven platforms, in one shape: does it exist, how big is it, is it verified, when was it created, is it in our catalog and how stale is that reading. The catalog checks are index probes and cost nothing; add /live to read the platform itself.
- GET/accounts/platforms
- GET/accounts/{platform}/{handle}
- GET/accounts/{platform}/{handle}/live
Directory
The account and channel catalog the crawlers maintain across X, Instagram, TikTok, YouTube, Telegram and Bluesky. Reads are served from our own Postgres, so they are fast, cheap and bounded only by your tier.
- GET/directory
- GET/directory/{platform}
- GET/directory/{platform}/{id}
People
Read the account and channel catalog across all seven platforms.
- GET/people/lookup
- GET/people/search
Live scrape
On-demand reads that skip the catalog and fetch from the source right now. Slower and separately metered, because every call costs upstream work. Reach for these when you need one handle fresh, not for bulk enrichment.
- GET/scrape/x/user
- POST/scrape/x/users
- GET/scrape/x/verify
Insights
Derived engagement intelligence: engagement rates, top and viral posts, posting patterns and cohort benchmarks computed over the post layer.
- GET/insights/x/{handle}
- GET/insights/x/{handle}/engagement
- GET/insights/x/{handle}/top-tweets
Research
Findings, runs and events from the autonomous research engine, which decides on its own which pools to expand and reports what it learned.
- GET/research/findings
- GET/research/findings/{id}
- GET/research/runs
Engines
Operational health of every crawler: throughput, freshness, catalog size and crawl backlog. This is the surface to alert on.
- GET/engines
- GET/engines/{key}
Marketplace
Public marketplace data: active listings, platform statistics, the seller leaderboard and current pricing. The same numbers the site shows, with nothing key-holder-specific in them.
- GET/marketplace/listings
- GET/marketplace/listings/{id}
- GET/marketplace/stats
Tools
The analysis tools behind the public free-tool pages, callable directly: valuation, follower audit, scoring and the rest. Metered like a live call, because each run costs compute or an upstream fetch.
- GET/tools
- POST/tools/valuation
- POST/tools/shadowban-check
Leads
B2B lead data: LinkedIn companies and decision makers, plus X follower-graph exports. Sensitive by nature, separately scoped, and never granted by default.
- GET/leads/linkedin/companies
- GET/leads/linkedin/companies/{id}
- GET/leads/linkedin/people
Built to be integrated once
The contract is the product. It is written down, it is versioned, and it does not change under you.
One envelope, always
Success is { data, meta }, failure is { error } with a documented code. Clients branch on codes, never on prose, so an error message can be rewritten without breaking anybody.
Cursors, not offsets
Every list paginates with a signed opaque cursor. Deep pages cost the same as shallow ones, and a position cannot be hand-written into a query.
Limits you can read
Rate, quota and plan standing come back as headers on every response. A client can see how close it is without a second call.
Scoped keys
A key carries only the scopes you grant it, and can be pinned to an IP allowlist. Rotate one without touching the others.
curl "https://api.playersells.com/v2" \
-H "Authorization: Bearer $PLAYERSELLS_API_KEY"The root endpoint returns the full capability list for your key: which endpoints exist, which scopes you hold and which of them you may call.
An OpenAPI 3.1 document is generated from the same catalog this site renders, so a client you generate from it can never describe an endpoint that does not exist.
/openapi.jsonPricing
A plan buys a monthly request budget. Live calls, which fetch from the source instead of the catalog, cost more of that budget than a catalog read. Past the budget you can either stop or pay for overage, and that switch is yours.
Free
Prove it works against real data, then pay for volume.
- 500 requests per month
- Account and channel directory across all 7 platforms
- Marketplace listings, stats and leaderboard
- One key, no card required
Starter
For a product that has shipped and needs live data.
- 20,000 requests per month
- Live account checks straight from the source
- Ownership verification on 6 platforms
- Engagement insights and the full tool suite
- Three keys
Growth
For teams enriching at volume.
- 150,000 requests per month
- Cheaper live calls and a higher burst ceiling
- Autonomous research findings
- Ten keys, IP allowlisting
Scale
Every scope, including the sensitive ones.
- 750,000 requests per month
- Every scope, including B2B lead exports
- The cheapest live calls on a self-serve plan
- Twenty-five keys
Enterprise
Volume, every scope, and a number to call.
- 5,000,000 requests per month
- Highest burst and live-call ceilings
- Every scope, no exceptions
- One hundred keys
- Priority support and a response commitment
Try it before you decide
A free key takes one click, needs no card, and calls the same endpoints and the same data as every paid plan. The only difference is how many times.