Docs
View as Markdown

Integrations

Use Onekey from the tools you already work in. Two things exist today, and the guides use only those:

  • The REST API: GET https://api.onekey.dev/v1/{platform}/{endpoint} with an x-api-key header. It works from anything that can make an HTTP request.
  • The hosted MCP server: https://api.onekey.dev/mcp, with eleven tools an AI agent can use to find endpoints and fetch data. It authenticates with your API key in a header; there is no OAuth sign-in.
GuideUse it whenPath
n8nYou want a scheduled or webhook-driven workflow with no code.HTTP Request node and Webhook node (REST), or the MCP Client Tool node for an AI agent.
LangChainYou are building a Python or JavaScript agent.langchain-mcp-adapters / @langchain/mcp-adapters against the hosted MCP server.
Vercel AI SDKYou are building a TypeScript app or route handler.createMCPClient from @ai-sdk/mcp against the hosted MCP server.
Claude CodeYou want your coding assistant to fetch public data.claude mcp add --transport http.

Before any guide#

  1. Get a key. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
  2. Put it in an environment variable named ONEKEY_KEY. Never paste it into a prompt, a shared workflow or a public repo.
  3. For an agent that will run unattended, create a separate key with a credit limit, so the most it can spend is a number you chose.

What the guides do not cover#

The pages describe only what the API does today. They do not use AI enrichment beyond pointing at Labels, and they do not use universal search or the reports; see those pages. Every guide has an Untested section saying which snippets were checked against the vendor's documentation but not run.

  • Monitors: have Onekey call your webhook when data changes instead of polling.
  • MCP server: connection details, the eleven tools and what results and errors look like.
  • Credits & pricing: every price is flat and printed on the endpoint's page.