Build Compass into your agent stack
Compass exposes a few surfaces designed for non-UI workflows:Coding Assistant
LLM-optimized docs Cursor, Claude Code, Copilot, and other AI assistants can fetch directly. Drop a single URL into your project config and let the agent write the integration.
MCP Server
A hosted Model Context Protocol server at
api.compasslabs.ai/mcp. Connect Claude or Cursor with one URL and every Compass product becomes a native agent tool — nothing to install.CLI
A scriptable command-line interface to every Compass endpoint. Use it for one-off queries, shell pipelines, CI jobs, or as the tool layer behind an autonomous agent.
Agent Skill
A packaged skill that teaches Claude Code, Cursor, or Codex to drive the CLI for you — describe a DeFi action in plain English and the agent picks the right
compass command and runs it.Which one?
Many teams use several: the coding assistant scaffolds an integration in their codebase, while the MCP server or CLI runs alongside for inspection, automation, and agent tooling.
Agent-friendly by design
The CLI ships with an--agent-mode flag that switches output to TOON (token-efficient) format and enables structured error messages. It auto-activates when the CLI detects it’s being invoked from a known agent environment (CLAUDE_CODE, CURSOR_AGENT, etc.) — so an agent calling compass earn vaults ... gets parseable output without you having to configure anything.
See the CLI page for details.
Get Started
New to Compass? Start with the SDK quickstart.
API Reference
Browse every endpoint the CLI and SDKs wrap.