AgentKey Integration: Web, Social, and On-Chain Data Access for AI Agents

Connects AI agents to web, social, and on-chain data via a single MCP subscription.

Data & On-Chainbeginner13 min read
Author
chainbase-labs
Stars
560
Language
Shell
License
Apache-2.0
Upstream updated
2026-07-24
AgentKey Integration: Web, Social, and On-Chain Data Access for AI Agents

AgentKey connects your AI agent (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, Manus, and 40+ others) to external data sources including web search, social media, on-chain crypto data, finance, e-commerce, and business information through a single subscription. Once installed, your agent can browse Twitter, search LinkedIn, scrape any webpage, read YouTube transcripts, pull token prices, and summarize on-chain wallet activity without needing individual API keys for each provider.

What It Does

AgentKey provides your AI agent with the following capabilities, all routed through a single cloud-side integration:

  • Web search: Search engines, news, and real-time discovery across the open web
  • Web scraping: Clean article extraction, structured data, and metadata from any URL
  • On-chain / Crypto: Token prices, market data, on-chain activity, and project metadata
  • Social & content: Public posts, videos, and discussions across major social and content platforms
  • Finance: Stock and FX quotes, technical indicators, company financials, and earnings
  • E-commerce: Product listings, prices, reviews, and best-sellers across major marketplaces
  • Business: Company, funding, investor, and people data for market and competitive research

Underlying providers are routed automatically and grow over time. Your agent can call find_tools to see what is currently available. The sources also list Maps and Weather as planned capabilities.

According to the official documentation, before AgentKey, 10 tasks required 10 API keys and 10 separate bills. With AgentKey installed, your agent gains all these data capabilities automatically with no per-provider registrations and no juggling separate API bills. One subscription covers everything.

Concrete use cases from the sources include:

  • Asking your agent what someone has been saying on Twitter lately: without AgentKey, tweets are blocked; with AgentKey, the agent pulls all relevant tweets and summarizes them.
  • Asking about product sentiment on Instagram: without AgentKey, it is blocked and requires login; with AgentKey, the agent scrapes real posts and organizes them by sentiment.
  • Asking what a YouTube or Bilibili video covers: without AgentKey, the agent cannot read it because there are no subtitles; with AgentKey, the agent reads the video transcript and extracts key points.
  • Finding Reddit threads about a specific pain point: without AgentKey, the request returns a 403 error; with AgentKey, the agent finds relevant threads and extracts solutions.
  • Checking a competitor or candidate on LinkedIn: without AgentKey, there are 403 access issues; with AgentKey, the agent opens the page and summarizes key info.
  • Asking what is trending on Douyin or TikTok: without AgentKey, the agent cannot scrape the hot list; with AgentKey, the agent pulls trending topics and tags.
  • Asking what a webpage says: without AgentKey, the agent returns raw HTML; with AgentKey, the agent extracts the content and explains it clearly.
  • Asking what a GitHub repo does: without AgentKey, you have to click through yourself; with AgentKey, the agent reads the README and Issues and gives a one-line summary.
  • Asking what a wallet or fund has been buying lately: without AgentKey, you have to click through a block explorer; with AgentKey, the agent summarizes recent transactions and positions.

Setup

Diagram: Setup

One-Command Install (Recommended)

The installer auto-detects every agent on your machine (40+ supported agents from the vercel-labs/skills supported-agents list, including Claude Code, Codex, Gemini CLI, and Cursor CLI) and configures each one. A browser tab opens for login, then you are done.

macOS / Linux

curl -fsSL https://agentkey.app/install.sh | bash

Windows (PowerShell)

irm https://agentkey.app/install.ps1 | iex

After installation, restart your agent. Then ask it something that needs the internet, for example: "What has Musk been tweeting about lately?" No API key to copy, no JSON to edit.

Advanced Install Options (CI / Specific Agents / Manual Two-Step)

The installer auto-detects which AI agents you have on this machine by probing well-known config directories and binaries from the vercel-labs/skills supported-agents list and pre-selects them with no multi-select prompt. You can override this with the following flags:

# Non-interactive (CI / unattended): install to every detected agent, no prompts
curl -fsSL https://agentkey.app/install.sh | bash -s -- --yes

# See which agents the installer would auto-select on this host (and exit)
curl -fsSL https://agentkey.app/install.sh | bash -s -- --list-agents

# Only install the skill for specific agents (overrides auto-detection)
curl -fsSL https://agentkey.app/install.sh | bash -s -- --only claude-code,cursor

# Skip our agent detection; let `skills` CLI install for every agent it finds
curl -fsSL https://agentkey.app/install.sh | bash -s -- --all-agents

# Only the skill, or only the MCP auth
curl -fsSL https://agentkey.app/install.sh | bash -s -- --skip-mcp
curl -fsSL https://agentkey.app/install.sh | bash -s -- --skip-skill

PowerShell equivalents: -Yes, -ListAgents, -Only, -AllAgents, -SkipMcp, -SkipSkill.

Manual Two-Step Install

If you prefer to run the two underlying commands yourself, or the one-line installer cannot reach your machine, use this approach:

# 1. Install the skill into every detected agent
npx skills add chainbase-labs/agentkey

# 2. Authenticate and register the MCP server
npx -y @agentkey/cli --auth-login

Headless / SSH / Docker

The auth step always tries to open a browser and prints the URL. On a machine without a usable display, copy the printed URL to any device with a browser to finish authentication. If you prefer typing the key manually, run npx -y @agentkey/cli --setup which opens an interactive wizard instead.

Manual Config for Unsupported Agents

MCP auto-configuration covers Claude Code, Claude Desktop, and Cursor. For Codex, OpenCode, Gemini CLI, Hermes, Manus, or Linux Claude Desktop, the skill still installs automatically but you need to paste this MCP snippet into the agent's own config (the path varies per agent):

{
  "mcpServers": {
    "agentkey": {
      "type": "http",
      "url": "https://api.agentkey.app/v1/mcp",
      "headers": { "Authorization": "Bearer ak_..." }
    }
  }
}

Then restart the agent. The skill's first-run activation will also walk you through this.

Claude Code Plugin Mode

Install straight from the marketplace. The plugin prompts you for your AgentKey API key on enable and wires the MCP server for you, so there is no second @agentkey/cli step:

# Public install
claude plugin marketplace add chainbase-labs/agentkey
claude plugin install agentkey@agentkey

# Or from a local checkout, for development
claude plugin marketplace add /absolute/path/to/agentkey
claude plugin install agentkey@agentkey

On enable, Claude Code prompts for AGENTKEY_API_KEY (stored in your OS keychain) and injects it into the plugin's .mcp.json via ${user_config.AGENTKEY_API_KEY}. Reload a local checkout with claude plugin update agentkey after edits. The sources note that day-to-day skill iteration is still fastest via the skills-CLI path; the plugin path is the one-step option for Claude Code users.

Codex Plugin Mode

Install from the marketplace bundled in this repo. Auth is OAuth (browser sign-in on install), so there is no API key to paste and no second @agentkey/cli step:

# Public install
codex plugin marketplace add chainbase-labs/agentkey
# then run /plugins inside Codex and install AgentKey,
# or: codex plugin install agentkey@agentkey

The plugin manifest lives in .codex-plugin/plugin.json; it bundles the same skill plus a remote-HTTP MCP entry (.codex-plugin/mcp.json) that authenticates against https://api.agentkey.app/v1/mcp via MCP OAuth (RFC 9728 discovery). Sign in with your AgentKey account when Codex prompts you.

Self-Host or Develop Against AgentKey

Install from a local checkout:

git clone https://github.com/chainbase-labs/agentkey.git
cd agentkey

# 1. Install your working tree into every detected agent
npx skills add .

# 2. Register the MCP server (if you haven't already)
npx -y @agentkey/cli --auth-login

npx skills add . accepts a local path or a file:// URL. Run it again after each edit to skills/agentkey/SKILL.md. The MCP step only needs to run once per machine.

If you are iterating on the MCP server itself, the server lives at AgentKey-Server/ (Go) and exposes the MCP endpoint at /v1/mcp. Run a local server with make run and point your MCP config at http://localhost:8081/v1/mcp to test changes end-to-end.

Uninstall

One command cleans every agent and config file.

macOS / Linux

curl -fsSL https://agentkey.app/uninstall.sh | bash

Windows (PowerShell)

irm https://agentkey.app/uninstall.ps1 | iex

This removes the skill from every agent, strips the agentkey MCP entry and API key from all MCP client configs, and clears caches and logs. Pass --keep-marketplace (bash) or -KeepMarketplace (PowerShell) to retain the Claude Code plugin marketplace entry.

If you prefer a manual two-step uninstall:

# 1. Remove the skill from every agent
npx skills remove chainbase-labs/agentkey

# 2. Delete the "agentkey" entry under mcpServers in each MCP client config:
#    - Claude Code:     ~/.claude.json
#    - Claude Desktop:  ~/Library/Application Support/Claude/claude_desktop_config.json  (macOS)
#                       %APPDATA%\Claude\claude_desktop_config.json                      (Windows)
#    - Cursor:          ~/.cursor/mcp.json

The one-command uninstaller additionally cleans npm/npx caches, legacy shell rc entries, CLAUDE.md sections, and MCP stdio logs. The sources recommend using the one-command uninstaller if you want a fully clean slate.

Configuration Reference

Environment Variables

VariablePurposeDefaultNotes
AGENTKEY_API_KEYAPI key for authenticationNoneStored in OS keychain when using Claude Code plugin mode. Used in the Authorization header as Bearer ak_....
AGENTKEY_TELEMETRYDisable telemetry for a single sessionNot setSet to 0 to opt out of anonymous usage telemetry for one session.

File-Based Telemetry Opt-Out

Create the file ~/.config/agentkey/telemetry-disabled for a persistent opt-out. To re-enable, delete that file.

Installer Flags

Flag (bash)PowerShell EquivalentPurpose
--yes-YesNon-interactive (CI / unattended): install to every detected agent, no prompts
--list-agents-ListAgentsSee which agents the installer would auto-select on this host (and exit)
--only claude-code,cursor-Only claude-code,cursorOnly install the skill for specific agents (overrides auto-detection)
--all-agents-AllAgentsSkip our agent detection; let skills CLI install for every agent it finds
--skip-mcp-SkipMcpOnly install the skill, skip MCP auth
--skip-skill-SkipSkillOnly run MCP auth, skip skill install
--no-telemetryNot listedOpt out of telemetry at install time

Slash Commands (Inside Your Agent)

CommandWhat It Does
/agentkeyAuto-triggered during data queries. You usually do not call it manually.
/agentkey setupFirst-time setup: configure API key and verify MCP connectivity.
/agentkey statusDiagnose current config (MCP, version, connectivity test).

MCP Server Configuration

The MCP server is hosted remotely at https://api.agentkey.app/v1/mcp. It uses HTTP transport with an Authorization header containing a Bearer token. The server is always up to date because it is cloud-hosted. The @agentkey/cli package (run as npx -y @agentkey/cli --auth-login) only writes the remote-HTTP MCP config into each AI client and never has to be re-run unless you want to rotate your key.

Skill Files

The skill files (SKILL.md + helpers) are stored locally. Their update mechanism depends on the client:

  • Claude Code: Updates are automatic. On the first call of a session the skill runs a silent version check. If a new release is available, it prompts you to upgrade and (with your consent) runs npx skills update -g agentkey.
  • Claude Desktop, Cursor, and other clients without an inline Bash tool: Starting in v1.4.0, the MCP server publishes the latest skill version via a dedicated metadata tool (agentkey_skill_meta). Your agent calls it once per session, compares against this skill's own version, and prompts you to upgrade with the exact command for your client. See protocol/skill-meta-v1.md for the protocol details.
  • Force manual update (any client): Run npx skills update agentkey to refresh the skill content. To pin a specific version, run npx skills add chainbase-labs/agentkey@v1.0.0.

Note: npx skills update writes to ~/.agents/skills/agentkey and ~/.claude/skills/agentkey, which is where Claude Code reads from. Claude Desktop reads from its own sandbox path and is not touched by npx skills update. Use the Desktop bootstrap command (detailed in the Update section of the sources) for Desktop.

How It Works

AgentKey uses the Model Context Protocol (MCP) to connect AI agents to external data. The architecture has two main components:

  1. Cloud-side MCP server: Hosted at https://api.agentkey.app/v1/mcp. This server maintains integrations across the open web and routes requests to the appropriate underlying provider automatically. The server is always up to date because it is cloud-hosted.

  2. Local skill files: A decision tree and routing rules stored in skills/agentkey/SKILL.md plus helper scripts. These files tell your agent how to discover and invoke the MCP server's tools.

When your agent needs external data, it follows the skill's decision tree to call the MCP server. The server handles authentication, provider routing, and data retrieval. The underlying providers are routed automatically and grow over time. Your agent can call find_tools to see what is currently available.

For Claude Code, the skill runs a silent version check on the first call of a session. For clients without an inline Bash tool (Claude Desktop, Cursor), starting in v1.4.0 the MCP server publishes the latest skill version via the agentkey_skill_meta metadata tool. The agent calls it once per session, compares against the local skill's version, and prompts an upgrade if needed.

AgentKey collects anonymous usage telemetry: which agent you installed into, your skill version, and upgrade outcomes. According to the sources, AgentKey never collects your queries or responses. The only data collected is anonymous usage telemetry.

Requirements and Limitations

Supported Platforms

  • macOS and Linux (bash installer)
  • Windows (PowerShell installer)

Supported Agents

The installer auto-detects 40+ agents from the vercel-labs/skills supported-agents list. Common examples explicitly named in the sources include Claude Code, Codex, Gemini CLI, and Cursor CLI. MCP auto-configuration covers Claude Code, Claude Desktop, and Cursor. For Codex, OpenCode, Gemini CLI, Hermes, and Manus (or Linux Claude Desktop), the skill installs automatically but you need to manually paste the MCP snippet into the agent's config.

Product Stage

The product is in early access. The sources state there are rough edges and ask for patience. Feature requests and bug reports are welcome via GitHub Issues or Telegram.

Limitations

  • The MCP server is cloud-hosted. There is no mention of an offline or fully self-hosted mode for production use (though you can run a local MCP server for development by pointing at http://localhost:8081/v1/mcp).
  • The skill update mechanism for Claude Desktop requires a one-time bootstrap if you are on a pre-1.4.0 skill. The metadata tool exists but the skill rule does not know how to read it until you bootstrap.
  • Claude Desktop reads skill files from its own sandbox path, which is not touched by npx skills update. You must use the Desktop bootstrap command for updates on that platform.
  • The sources do not specify any rate limits, maximum request sizes, or concurrency limits. These are presumably governed by your subscription plan.
  • The sources do not list specific supported social media platforms, blockchains, or e-commerce sites. They describe coverage in general terms ("major social and content platforms," "major marketplaces").

Troubleshooting

Diagnosing Issues

Inside your agent, run /agentkey status. This command diagnoses your MCP config, version, and connectivity.

Stuck on Pre-1.4.0 Skill in Claude Desktop

If you are stuck on a pre-1.4.0 skill in Claude Desktop, the metadata tool exists but your skill rule does not know how to read it. Bring yourself current once with this bootstrap command:

# Replace <UUID1>/<UUID2> with the actual session folder under skills-plugin
# (usually there is just one; pick the one that contains skills/agentkey/SKILL.md)
DESKTOP_BASE="$HOME/Library/Application Support/Claude/local-agent-mode-sessions/skills-plugin"
LATEST_REPO_ZIP=$(mktemp -d)/agentkey.tar.gz
curl -fsSL https://github.com/chainbase-labs/agentkey/archive/refs/heads/main.tar.gz -o "$LATEST_REPO_ZIP"
tar -xzf "$LATEST_REPO_ZIP" -C "$(dirname "$LATEST_REPO_ZIP")"
find "$DESKTOP_BASE" -type d -path "*/skills/agentkey" 2>/dev/null | while read -r dst; do
  cp -R "$(dirname "$LATEST_REPO_ZIP")"/agentkey-main/skills/agentkey/. "$dst/"
done
# Then fully quit and restart Claude Desktop.

After this one bootstrap, future versions will be discovered automatically via the metadata tool.

Getting Help

Telemetry Opt-Out

AgentKey sends anonymous usage telemetry. Three ways to opt out, any of them works:

# Persistent opt-out (recommended)
touch ~/.config/agentkey/telemetry-disabled

# One-shot env override (CI / single session)
AGENTKEY_TELEMETRY=0 <your command>

# At install time
curl -fsSL https://agentkey.app/install.sh | bash -s -- --no-telemetry

To re-enable, delete ~/.config/agentkey/telemetry-disabled.

Sources & References

This page was researched from 2 independent sources, combined and verified for completeness.

Newsletter

The #1 AI Newsletter

The most important ai updates, guides, and fixes — one weekly email.

No spam, unsubscribe anytime. Privacy policy

Other Hermes Agent integrations