Give AI trading agents a real strategy engine.
AI trading agents need rails: typed components, validation, backtests, deployment paths, and execution logs they can read. Keel exposes all of it through CLI, API, and MCP — so agents can compose strategies, run backtests, deploy live on Hyperliquid, and inspect what happened, all programmatically.
What goes wrong when agents have no infrastructure.
Three failure modes — and the structure that fixes each.
An LLM agent asked to “write a trading strategy” will hallucinate code, invent functions, and skip evaluation. The output looks plausible and runs nowhere.
Agents work inside a typed component registry. Every output is a structurally valid pipeline that can be backtested and deployed without rewriting.
Agents that propose trades or strategies without running them through realistic backtests produce confidence without evidence.
Agents can run multi-asset portfolio backtests with real fees, slippage, and funding through the same engine as the UI. Confidence comes from the simulation.
Giving an autonomous agent custody of your funds is a recipe for catastrophic loss when it goes off-script.
Live deployment requires user authorization. Keel is non-custodial — keys never leave your wallet, and you can revoke access anytime.
CLI, REST API, and MCP.
Same component registry, same backtest engine, same deployment path — exposed three ways so agents and humans use the same primitives.
Python CLI for agents
Component search, strategy authoring, validation, backtest, and deploy from the command line.
Programmatic access
Strategy CRUD, backtest, deployment, and execution logs via REST. Same surface the UI uses.
Model Context Protocol
Native tool integration for Claude, Codex, and other MCP clients. Agents call Keel tools directly.
Common questions
What models work with Keel’s MCP server?
Any LLM that supports the Model Context Protocol — Claude, ChatGPT/Codex, and other MCP-compatible clients. The MCP server exposes the same component discovery, validation, and backtest endpoints the CLI uses.
Can agents trade autonomously?
Agents can compose and backtest strategies autonomously. Live deployment requires user authorization — Keel is non-custodial and uses Hyperliquid’s native delegation, so the user signs off on what runs. Agents propose; humans confirm.
Is there an OpenAPI spec?
Yes. The REST API has an OpenAPI spec covering strategy CRUD, backtest, deployment, and execution-log endpoints. The CLI and MCP server are wrappers over the same API surface.
How do I install the MCP server?
Install keel-trade with pipx, then register keel mcp serve with your MCP-compatible client. The host launches that command as a stdio child process; you do not run a daemon, open a port, or start a separate service. The agent gets direct keel_* tools for component search, strategy compose, backtest, summarize, sharing, and live preview.
Can my agent deploy live without my approval?
No. Live deployment to Hyperliquid requires explicit user authorization — the agent cannot bypass the non-custodial signing flow. This is a feature, not a limitation.
What can an agent do that a human cannot?
An agent can iterate on strategy variants overnight, run dozens of backtests in parallel, scan the component registry for candidates that match a hypothesis, and surface the top results. The human still decides what to deploy.
Keep exploring
AI Trading Strategy Builder
For humans using AI to build strategies — the UI side of the same component system.
What is a Strategy OS?
The category Keel sits in — full-lifecycle strategy infrastructure.
Keel MCP
Agent-first product page with self-registration, quick install, stdio setup, and app handoff.