jupiter-development

Implement Jupiter-based Solana integrations for token swaps, pricing, and lending.

4|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill jupiter-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupiter-development
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/jupiter-development
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill jupiter-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables safe, standards-compliant development of Jupiter-based Solana integrations by following official docs and guardrails.

Core Features & Use Cases

  • Select the correct Jupiter surface (Ultra, Tokens API V2, Price API, Lend) for token swaps, pricing, discovery, or lending tasks.
  • Follow official docs to implement integrations with proper routing, auth, and rate-limit considerations.
  • Document decisions and maintain alignment with Jupiter's current surface as source of truth.

Quick Start

Follow current Jupiter docs to identify the proper surface (Ultra vs Metis, Tokens API, Price API, Lend) and implement with the recommended flow; no hard-coded secrets and use API keys per docs.

Frequently Asked Questions about jupiter-development

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

FAQPage Schema
How do I integrate Jupiter Solana APIs for token swaps and pricing?

Jupiter Solana integration requires selecting the correct surface (Ultra, Tokens API V2, Price API, or Lend) and implementing according to official docs with proper routing and authentication. Align with current Jupiter surfaces as the source of truth.

What is the correct Jupiter API surface for token discovery and lending?

For Jupiter integrations, the correct surface for token discovery is Tokens API V2, while lending tasks use the Lend surface. Ultra handles token swaps, and Price API manages pricing queries.

Do I need an x-api-key to authenticate Jupiter api.jup.ag requests?

Yes, authenticating Jupiter api.jup.ag requests requires an x-api-key. You must validate hostnames and use API keys per official docs, explicitly avoiding any hard-coded credentials in your Solana integration.

How do I choose between Jupiter Ultra and other surfaces for Solana swaps?

Choosing between Jupiter Ultra and other surfaces involves aligning with current official docs. Ultra is designated for token swaps, while Tokens API V2, Price API, and Lend serve specific discovery, pricing, and lending tasks.

What are the guardrails for safe Jupiter Solana development?

Guardrails for safe Jupiter Solana development include validating hostnames, using x-api-key for authentication, avoiding hard-coded credentials, and maintaining alignment with current Jupiter surfaces as the source of truth.

Can I hard-code API credentials when building Jupiter integrations?

No, you must not hard-code API credentials when building Jupiter integrations. The guardrails require using API keys per official documentation and validating hostnames for secure api.jup.ag requests.