AgentKey
One MCP gateway and master key for live search, scrape, social, finance, and crypto data.
AgentKey is Chainbase's hosted MCP server and installer/plugin that routes agent requests across ~1,800 live-data tools (search, scrape, social, crypto, finance, business, e-commerce) behind one subscription and auto-failover. The open-source CLI/plugin configures supported coding agents; the MCP endpoint itself is managed at api.agentkey.app.
Official resources
Selection advice
Quick comparison
AgentKey concentrates on live external data through one MCP connection and credit plan. Composio focuses on SaaS action catalogs with managed OAuth; Arcade.dev focuses on authorized MCP tool runtimes.
| AgentKey | Composio | Arcade.dev | |
|---|---|---|---|
| Best for | Agents that need live web, social, market, and on-chain data without per-provider keys | Agents that must act inside many SaaS apps with managed OAuth | Teams standardizing MCP tool authorization and production permissions |
| Primary surface | Hosted MCP gateway + one-line installer/plugin for coding agents | Managed toolkits, OAuth, SDK/REST actions, and MCP options | MCP runtime with auth, permissions, and audited execution |
| Tradeoff | Strong live-data coverage vs dependency on a managed credit gateway | Broad SaaS actions vs less focus on social/on-chain data marketplaces | Strong auth runtime vs no unified live-data credit marketplace |
Best for
- live web/social/market data over MCP
- one master key instead of many provider APIs
- coding agents that need discover → describe → execute tool calls
- auto-failover across upstream data providers
Not ideal for
- teams that only need internal SaaS write actions (CRM/tickets)
- fully air-gapped deployments that cannot call a hosted MCP endpoint
- projects that already own and prefer to operate every data API directly
Core concepts
Minimal implementation shape
Run `curl -fsSL https://agentkey.app/install.sh | bash` (or the Windows install script), create an `ak_...` master key in the console, restart your agent, then ask it to `find_tools` for a live query and `execute_tool` on the returned Provider/Operation.