> For the complete documentation index, see [llms.txt](https://docs.midasmarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midasmarkets.xyz/trading/jupiter.md).

# Jupiter

Jupiter is the Solana execution route in Midas for supported Solana swaps and Solana-side limit-order flows.

* **Solana swaps** — Jupiter routes swaps between supported Solana mints with quoted execution parameters.
* **SOL handling** — Native SOL routes use the wrapped SOL mint where needed while the route can wrap and unwrap for the user.
* **Limit orders** — Where enabled, Solana limit orders can lock balances on-chain until filled or cancelled.

## When Midas uses Jupiter

Midas uses Jupiter when the selected input and output assets are on Solana and the requested action is a supported spot route or Solana limit-order workflow.

## Mint resolution

Jupiter requires mint addresses, not vague symbols. Midas should resolve input and output mints before execution and reject ambiguous or unresolved tokens.

## Execution flow

A user or Ask Midas request becomes a quote and confirmation card. After the user confirms, the server executes the route and the portfolio updates as settlement is observed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.midasmarkets.xyz/trading/jupiter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.