Jupiter primary sources — 2026-04-30

Project status in this pass

• No single canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official developer docs, llms surfaces, and the public CLI repository.

Primary-source snapshots

1) Docs index / llms.txt

• URL: https://dev.jup.ag/docs/llms.txt
• Key excerpt:
  • Opens with “Jupiter is DeFi infrastructure on Solana.”
  • Says all APIs are REST/JSON, require no RPC node for the managed path, and return clean responses that LLMs and AI agents can parse directly.
  • Enumerates product surfaces across Swap, Trigger, Recurring, Lend, Price, Tokens, Portfolio, Prediction, AI tooling, and developer-platform setup.

2) Plans and pricing page

• URL: https://developers.jup.ag/docs/portal/plans
• Key excerpt:
  • Says all plans use the same api.jup.ag API with the same freshness and latency, and that upgrading primarily changes rate limits and credits.
  • Documents keyless access at 0.5 requests per second, which is explicitly framed as suitable for lightweight AI-agent or test use cases.
  • Shows how broad the platform surface is by listing endpoint-credit costs across Swap, Trigger, Recurring, Tokens, Price, Portfolio, Lend, Send, Studio, and Prediction.

3) Trigger Order API overview

• URL: https://developers.jup.ag/docs/trigger
• Key excerpt:
  • Describes Jupiter Trigger as advanced order infrastructure for limit orders, take-profit/stop-loss (OCO), and conditional chains (OTOCO) on Solana.
  • Says V2 stores pending orders off-chain and private by default until execution, specifically to close a common MEV attack vector.
  • Explains the vault-based operating model and challenge-response JWT plus API-key authentication.

4) Ultra overview

• URL: https://developers.jup.ag/docs/ultra
• Key excerpt:
  • Marks Ultra as superseded by Swap V2 but still describes Jupiter’s managed execution design in unusually concrete terms.
  • Highlights RPC-less swaps, automatic gasless support, Real-Time Slippage Estimator (RTSE), and sub-second landing through Jupiter Beam.
  • This is strong evidence that Jupiter is operating an execution and landing stack, not merely publishing routing quotes.

5) Studio overview

• URL: https://developers.jup.ag/docs/studio
• Key excerpt:
  • Describes Jupiter Studio as APIs for token creation with flexible bonding curves, LP-fee management, vesting schedules, and dedicated token pages on jup.ag.
  • Shows Jupiter also extending into creator and token-launch tooling.

6) AI / CLI docs

• URL: https://developers.jup.ag/docs/ai/cli
• Key excerpt:
  • Describes the Jupiter CLI as a terminal, Telegram, and agent-facing interface for spot trading, perps, and lend.
  • Says the CLI is non-interactive and LLM-friendly by design, with structured JSON output.
  • Explicitly points builders toward OpenClaw and other agent setups, which reinforces Jupiter’s AI-native posture.

7) CLI repository README

• URL: https://raw.githubusercontent.com/jup-ag/cli/main/README.md
• Key excerpt:
  • Expands the CLI scope to Spot, Perps, Lend, Prediction Markets, Token Verification, and more.
  • Documents JSON output mode and --dry-run transaction previews for agent-friendly workflows.
  • Shows Jupiter maintaining a first-party execution interface beyond browser and raw REST usage.

8) CLI package metadata

• URL: https://raw.githubusercontent.com/jup-ag/cli/main/package.json
• Key excerpt:
  • Publishes the package as @jup-ag/cli.
  • Lists distributable docs, llms.txt, and the CLI entrypoint as part of the shipped package.
  • Reinforces that AI/documentation affordances are built into the released developer toolchain.

Working conclusion

Jupiter is best cataloged as a Solana execution and builder control plane: routing, managed transaction landing, advanced order automation, market-data and portfolio APIs, token-launch tooling, and explicit AI-agent integration surfaces in one platform. In this pass, the docs corpus and CLI repo—not a whitepaper—were the decisive primary sources.