Skip to main content
Jupiter’s APIs are AI-native: no RPC, clean JSON, simple REST. Whether your agent is running locally or on a hosted platform, there’s a way to connect it to Jupiter.

Pick the Right Tool

Which tools to use depends on where your agent runs and what it needs to do:
GoalLocal (Claude Code, Cursor, Codex)Hosted (ChatGPT, Claude.ai)
Read the docsSkills + llms.txtDocs MCP + llms.txt
Execute operationsCLIJupiter MCP
Local agents have shell access, can install packages and run commands. The CLI + Skills combination integrates naturally into these environments. Hosted agents cannot install tools or execute shell commands. MCP exposes Jupiter’s capabilities as a network service that any agent can discover and call without prior setup.

Read the Docs

For agents that need to discover and understand Jupiter’s APIs before writing code or taking action.

llms.txt

LLM-optimised documentation index. Works everywhere, no setup required.

Skills

Pre-built context files that give coding agents structured integration guidance for Jupiter’s APIs.

Docs MCP

Search and query Jupiter docs via Model Context Protocol. For agents without filesystem access.

Execute Operations

For agents that interact with Jupiter directly - swap tokens, check prices, place orders.

Jupiter CLI

Trade from your terminal, Telegram, or through AI agents. Non-interactive, JSON-native, designed for both humans and LLMs.

Jupiter MCP

Execute Jupiter operations via MCP from any hosted platform. Coming soon.