integrating-jupiter

Map developer intents to Jupiter API endpoints and outline integration plans.

4|5|Updated Mar 23, 2023
One-click install
npx skills add https://github.com/jup-ag/docs --skill integrating-jupiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrating-jupiter
Source: https://github.com/jup-ag/docs/tree/main
Command: npx skills add https://github.com/jup-ag/docs --skill integrating-jupiter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The integration skill provides a centralized, proven approach for navigating and integrating Jupiter APIs across Ultra Swap, Lend, Perps, Tokens, Price, and more to accelerate production-grade deployments.

Core Features & Use Cases

  • Centralized mapping of intents to API families (Ultra Swap, Tokens, Price, Lend, Perps, etc.) to guide end-to-end integration.
  • Best-practice guidance for error handling, auth, input validation, and idempotent flows to ensure production-grade robustness.
  • Real-world use cases such as token discovery, price lookups, swaps, portfolio operations, and prediction-market interactions.

Quick Start

Describe a complete end-to-end integration plan for a common Jupiter use case (e.g., SOL to USDC swap) including the required endpoints, headers, and a minimal call sequence.

Frequently Asked Questions about integrating-jupiter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Jupiter APIs for token swaps and price lookups?

Jupiter API integration requires mapping your developer intent to the correct API family, such as Ultra Swap for swaps or Price for lookups, then outlining required endpoints. This approach generates a production-ready plan with auth and input validation.

What is the best way to structure a Jupiter Ultra Swap API call sequence?

The best way to structure a Jupiter Ultra Swap call sequence is to follow the recommended call order with guardrails, ensuring input validation and auth requirements are met before executing the swap. This prevents common production integration errors.

Which Jupiter API should I use for token discovery versus portfolio operations?

Use the Jupiter Tokens API for token discovery and the Lend or Perps APIs for portfolio operations. The integration guide concisely identifies the correct API pathway based on your specific developer intent to streamline endpoint selection.

Does the Jupiter API integration plan include error handling and idempotent flows?

Yes, the Jupiter API integration plan includes best-practice guidance for error handling, auth, input validation, and idempotent flows. This ensures production-grade robustness across Ultra Swap, Lend, Perps, and other Jupiter APIs.

How do I handle authentication requirements when integrating multiple Jupiter APIs?

Handle Jupiter API authentication by applying the best-practice guidance for auth requirements provided in the integration plan. This ensures secure access across Ultra Swap, Tokens, Price, Lend, and Perps API families during production deployment.