Build Jupiter integrations with safer API calls.
What it does
Guides developers in choosing Jupiter endpoints and building integrations with authentication, error handling, and production safeguards.
When to use it
Use when choosing or calling Jupiter endpoints, integrating its financial features, or debugging Jupiter API calls.
How to use it
It changes how the agent implements Jupiter integrations by requiring documentation-led endpoint selection, authentication checks, and typed error handling.
What you provide
- An existing project
Uses
What you need · 3
The quickstart reads the API key from the environment and supplies it as x-api-key for Jupiter REST requests.
Trigger order mutations require a JWT alongside x-api-key. The token is obtained by signing a wallet challenge and verifying the response; its storage location is not stated.
Routes token verification and metadata updates to this skill rather than handling them here; whether installation is required is unstated.
Access · 1
This skill
developers.jup.ag
Fetches current Jupiter documentation