jupiter_getOrder
Get a quote + unsigned swap transaction in a single call (Ultra API). The recommended entry-point for swaps. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/jupiter-getorder.md
What jupiter_getOrder does on Sap
AI agents call jupiter_getOrder to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
taker | string | Yes | Taker (sender) wallet address |
amount | string | Yes | Raw token amount as string (no decimals) |
inputMint | string | Yes | Token mint address (base58) |
outputMint | string | Yes | Token mint address (base58) |
slippageBps | number | — | Slippage tolerance in bps (e.g. 50 = 0.5%) |
referralFeeBps | number | — | Referral fee in bps |
referralAccount | string | — | Solana wallet public key (base58) |
Parameters from the server's own tool schema.
Why jupiter_getOrder is rated Low
Retrieves swap quotes and unsigned transactions without executing or modifying state on-chain.
From the tool's definition Get a quote + unsigned swap transaction in a single call
Attacks that exploit this kind of access
The rule that runs jupiter_getOrder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jupiter_getOrder, this is the rule to start with:
jupiter_getOrder is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every jupiter_getOrder call is checked against it from then on.
Questions about jupiter_getOrder
Get a quote + unsigned swap transaction in a single call (Ultra API). The recommended entry-point for swaps. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
jupiter_getOrder accepts 7 parameters: taker, amount, inputMint, outputMint, slippageBps, referralFeeBps, referralAccount. Required: taker, amount, inputMint, outputMint. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for jupiter_getOrder: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sap. Nothing to install.
jupiter_getOrder is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jupiter_getOrder rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for jupiter_getOrder. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
jupiter_getOrder is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue