Use it from the tools you already work in

Guides for n8n, LangChain, the Vercel AI SDK, Claude Code, other MCP clients and plain REST. They use only the REST API and the hosted MCP server, and they say plainly which snippets were not run in the vendor tool.

Read the guidesMCP serverGet a free key
the tools you already use
claude mcp add --transport http onekey https://api.onekey.dev/mcp \
  --header "Authorization: Bearer $ONEKEY_KEY"
Method   GET
URL      https://api.onekey.dev/v1/github/latest_release
Auth     Header Auth: x-api-key
Query    owner = {{ $json.owner }}
         repo  = {{ $json.repo }}
client = MultiServerMCPClient({
  "onekey": {
    "transport": "http",
    "url": "https://api.onekey.dev/mcp",
    "headers": {"Authorization": f"Bearer {os.environ['ONEKEY_KEY']}"},
  }
})
tools = await client.get_tools()
const mcp = await createMCPClient({
  transport: {
    type: "http",
    url: "https://api.onekey.dev/mcp",
    headers: { Authorization: `Bearer ${process.env.ONEKEY_KEY}` },
  },
});
const tools = await mcp.tools();
curl "https://api.onekey.dev/v1/github/latest_release?owner=facebook&repo=react" \
  -H "x-api-key: YOUR_API_KEY"

Snippets follow the integration guides, which say plainly that they were not run inside each vendor's tool.

Six ways in#

Two things exist today and every guide uses only those: the REST API (GET https://api.onekey.dev/v1/{platform}/{endpoint} with an x-api-key header) and the hosted MCP server (https://api.onekey.dev/mcp, key in a header, no OAuth). These are guides for using Onekey from those tools, not partnerships or listings in their marketplaces; we have no logos here on purpose.

ToolPathGuide
n8nHTTP Request node, Webhook node, or the MCP Client Tool noden8n guide
LangChainlangchain-mcp-adapters against the hosted MCP serverLangChain guide
Vercel AI SDKcreateMCPClient from @ai-sdk/mcp against the hosted MCP serverVercel AI SDK guide
Claude Codeclaude mcp add --transport httpClaude Code guide
Other MCP clientsAny client that can set a header: Cursor, Claude Desktop (via mcp-remote)MCP page
Plain RESTAnything that makes an HTTP requestQuickstart

Every guide checked its snippets against the vendor's current documentation but did not run them in the vendor's tool, and each says so in an Untested section. Treat the snippets below as untested in the vendor tool.

n8n untested in the vendor tool#

Use a Header Auth credential named x-api-key and an HTTP Request node for scheduled workflows:

shell
curl "https://api.onekey.dev/v1/github/repo?owner=facebook&repo=react" \
  -H "x-api-key: YOUR_API_KEY"

For "tell me when it changes", create a monitor whose webhook is an n8n Webhook node's production URL, instead of polling on a schedule. To let an n8n AI Agent use Onekey, point the MCP Client Tool node at https://api.onekey.dev/mcp with Streamable HTTP and a Bearer token. Read the guide.

LangChain untested in the vendor tool#

The MCP adapters turn the eleven tools into LangChain tools, so the agent can find endpoints, read their contracts and call them:

python
from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({
    "onekey": {
        "transport": "http",
        "url": "https://api.onekey.dev/mcp",
        "headers": {"Authorization": f"Bearer {os.environ['ONEKEY_KEY']}"},
    }
})
tools = await client.get_tools()  # hand these to your agent

Give an unattended agent its own key with a credit limit. Read the guide.

Vercel AI SDK untested in the vendor tool#

From a TypeScript route handler, connect the same hosted server as an MCP client and pass its tools to generateText or streamText. Call Onekey from your server, never from the browser, because anything you ship to a browser, including a key, is public. Read the guide.

Claude Code and other MCP clients untested in the vendor tool#

shell
claude mcp add --transport http onekey https://api.onekey.dev/mcp --header "Authorization: Bearer $ONEKEY_KEY"

Cursor and Claude Desktop configs are on the MCP page. Read the Claude Code guide.

Plain REST#

Nothing to install. Every endpoint page has curl, Python and JavaScript snippets, and /openapi.json describes all of them for client generators. The live catalog, with every price, is free and needs no key: GET https://api.onekey.dev/v1/platforms. The Python, TypeScript and Go SDKs are built but not published yet.

What these guides do not cover#

They do not use AI enrichment, and they do not use universal search or the reports beyond pointing at them. Webhooks from monitors work with any tool that can receive an HTTPS POST and verify a signature.

Keep reading