jupiter_swap_quote MCP tool; your backend signs the versioned transaction with the agent wallet accessKey and broadcasts via Solana RPC.
Supported chains
solana, solana-devnet
The agent must have a Solana address (solanaAddress) on the identity used for the swap.
Dashboard setup
- Open Agentic Stack → Integrations for your application.
- Enable Jupiter and enter your API key from dev.jup.ag.
- Save — credentials are encrypted server-side and included in agent validation for MCP calls.
Jupiter credentials are stored per application, not per end user. All agents under that app share the integration when enabled.
MCP tool: jupiter_swap_quote
| Parameter | Required | Description |
|---|---|---|
chain | No | solana (default) or solana-devnet |
input_token | Yes | Symbol (SOL, USDC) or SPL mint address |
output_token | Yes | Symbol or mint address |
amount | Yes | Human-readable sell amount |
slippage_bps | No | Default 50 (0.5%) |
Jupiter specialist chat
In the sample web app, open chat with?serviceAgent=jupiter (or pick the Jupiter category). The backend:
- Filters tools to Jupiter-relevant MCP calls (Solana token search, balances,
jupiter_swap_quote) - Injects Jupiter-specific system prompts
- Routes swap requests to
jupiter_swap_quote(not EVM swap tools)
Execution modes
TRANSFER_REQUIRE_CONFIRMATION | Behavior |
|---|---|
true (default) | User sees a swap confirmation card in chat — Confirm / Cancel before signing |
false | Backend auto-signs and broadcasts the swap transaction |
Transaction history
Confirmed swaps are recorded aschat_jupiter_swap in agent transaction history.
Related
Third-party integrations
BYOK overview, architecture, and deployment.
Swap confirmation
Confirm / cancel UX and REST endpoints.
MCP tools reference
Full tool catalog including
jupiter_swap_quote.Uniswap integration
EVM swaps via
uniswap_swap_quote.