One key, every platform, and what you can do with it
Onekey is one API for public data. These pages cover the parts around the endpoints: how an assistant connects, how a question spans platforms, how change reaches you, and what to expect when things fail. Anything that is not enabled yet says so.
What one call replaces
Many integrations become one request, and a report shows what happens inside it, including a source that fails.
Before: 12 integrations
12 keys to rotate, 12 response shapes to map, 12 sets of limits and retries to handle yourself.
After: 1 call
GET /v1/search/multi with platforms=: one key, one response shape, and a platform that fails shows in coverage and is refunded.
The after side is the multi-platform search route (api.onekey.dev/v1/search/multi), up to 20 platforms per call. Read how it bills and what a partial answer looks like.
1 request
?handle=torvalds
&platforms=github,bluesky,reddit
4 legs, in parallel
- github.profile...2001 credit
- bluesky.profile...2001 credit
- bluesky.posts...2001 credit
- reddit.user_about...502 UPSTREAM_BLOCKED1 credit
1 receipt
github.profile1
bluesky.profile1
bluesky.posts1
reddit.user_about0 refunded
total charged3
Timing is illustrative. The report, its legs, their prices and the 502 are from the creator vet report: only legs that answered are charged, a failed leg is refunded and named in coverage, and dry_run=true shows these prices for 0 credits.
Connect
Reach the data from an assistant, a workflow tool or your own code.
MCP server
A hosted MCP server: eleven tools, one line to connect Claude Code, Claude Desktop or Cursor with your key.
Open MCP server →For AI agents
llms.txt, per-platform files, Markdown twins of every docs page, machine-readable errors and a copyable prompt.
Open For AI agents →Integrations
n8n, LangChain, the Vercel AI SDK, Claude Code, other MCP clients and plain REST, each with a guide.
Open Integrations →SDKs
Python, TypeScript and Go clients. Built and tested, not published yet.
Open SDKs →Ask and watch
Questions and jobs that span platforms, on demand or on a schedule.
Universal search
One query in words, planned across platforms, run in parallel and merged. Priced before it runs.
Open Universal search →Reports
Brand mentions, creator vetting and demand signals as one structured answer, with coverage and warnings.
Open Reports →Monitors
Saved calls on a schedule that tell your webhook, signed, only when something you care about changes.
Open Monitors →Understand and trust
What comes back, what happens when things fail, and how to evaluate us.
Unified schema
One fixed set of field names for every platform. Honest nulls, and ext.* for what is platform-specific.
Open Unified schema →API explorer
Pick a platform and an endpoint, fill the parameters, see the request and the recorded response.
Open API explorer →Reliability
How failures are treated: refunds, stale-serve, idempotency, rate limits and the public status endpoint.
Open Reliability →Enterprise
Volume, security review and procurement: what to send us and what is documented today.
Open Enterprise →Browse the rest
The catalog, worked examples, free tools and the reference.
Platforms
Every source, its endpoints, prices and status.
Open Platforms →Solutions
Worked examples with real endpoints and honest monthly costs.
Open Solutions →Tools
Free tools that run the API on real public data: creator card, profile viewer, engagement rate, brand mentions, package lookup, trend snapshot, URL to data.
Open Tools →Docs
The reference: quickstart, credits, errors, caching and every endpoint.
Open Docs →Pricing
Credit packs, free credits and what a call costs.
Open Pricing →