> ## Documentation Index > Fetch the complete documentation index at: https://docs.raze.bot/llms.txt > Use this file to discover all available pages before exploring further. # Build a perp operation > The instructions of one perp operation, as ONE transaction for `wallet` to sign, and with `serialize: true` the unsigned transaction itself. Nothing is signed, sent or reserved. The same body works on both venues; only `marketId` changes. The operations: | `op` | What it does | Jupiter | GMTrade | |---|---|---|---| | `open` | Open or increase a position at market | yes | yes | | `limit` | Open at a trigger price (long below the mark, short above) | `422 venue_form` | yes | | `close` | Reduce or close at market (`closeBps`, default all) | yes, paid out in USDC | yes, paid out in the position's collateral | | `tpsl` | Resting take profit (`tp`) or stop loss (`sl`) on a position | yes, paid out in USDC | yes, paid out in the position's collateral | | `update` | Move the trigger or the size of a resting order | `422 venue_form` (cancel, then `tpsl`) | yes | | `cancel` | Cancel a request or pending order (`orderId`) | yes, 45 s after it was created | yes, while pending | | `deposit` | Add collateral to a position (`amountUsd`) | yes | yes | | `withdraw` | Remove collateral from a position (`amountUsd`) | yes, paid out in USDC | yes, in the position's collateral | The transaction is, in order: a memo `dad-perp::` signed by the wallet, the funding route (if any), then the venue's instructions (token accounts created idempotently, native SOL wrapped before and unwrapped after, GMTrade's user and position accounts when missing, the order). It is a **v1** transaction (4 096 bytes, 64 instructions, 64 accounts, no lookup tables): compute limits are in its message, not in `instructions`. **Keeper execution.** Landing this transaction queues the operation; the venue's keeper executes it later (`venueForm` says how). On Jupiter a market request lives seconds and can be cancelled 45 s after its creation; on GMTrade an order can be cancelled while it is pending, and each order escrows a 300 000-lamport execution fee for the keeper, returned by `cancel`. **`clientOrderId` is not an idempotency key.** It derives the address of the request/order, so a retry of the same `(op, clientOrderId)` fails while the first one is still pending, but acts a second time once the keeper has executed it. Check whether the first transaction landed before retrying. Wallet accounts (positions, the GMTrade user account, the order named by `orderId`) are read from the chain at every call. Which fields each operation needs, and which venue supports which: [Perps](/router/perps#operations). ## OpenAPI ````yaml perp.openapi.yaml POST /perp/instructions openapi: 3.1.0 info: title: Raze Router Perps API version: 1.0.0 description: > Perpetual futures on Solana through the router: live markets, quotes, unsigned transactions and the live state of a wallet, on **Jupiter Perps** (`jupiter`) and **GMTrade** (gmsol / GMX-Solana, `gmtrade`). **The router never signs and never sends.** `POST /perp/instructions` returns the instructions and, on request, the serialized unsigned transaction; your backend has the wallet sign it and broadcasts it. **One operation, one transaction.** The collateral deposit travels in the same transaction as the order, and when the wallet pays with another token (`fundingMint`) an exact-out swap route into the collateral mint is placed in front of the venue instruction, in that same transaction. **Execution is asynchronous on both venues.** The transaction creates a request (Jupiter) or an order (GMTrade); the venue's keeper executes it afterwards in its own transaction, at its own oracle price. Watch `GET /perp/account` (or the chain) to see the fill. **Conventions, everywhere:** - Perps are off until you enable them: `ROUTER_PERP=jupiter,gmtrade` (or `all`) in the router's environment. A venue that is off answers `422 venue_disabled`. - Market ids are `:-PERP`, e.g. `jupiter:SOL-PERP`, `gmtrade:SOL-WSOL-USDC-PERP`. Case-insensitive; `-PERP` is optional; `jup:`, `gmsol:` and `gm:` are accepted as aliases. - USD amounts are integers in micro-USD: fields ending in `Usd` (requests) and `UsdE6` (responses), so `10000000` is $10. - Prices are integers, USD per whole token × 10^6 (`priceE6`, `triggerPriceE6`). - Leverage and shares are basis points: `leverageBps` 20000 = 2x, `closeBps` 10000 = all. - Token amounts (`collateralAmount`, `amountIn`…) are raw base units of the mint. - Amounts and prices are JSON integers (send them as numbers, not strings). A response field that does not apply is omitted, except in `/perp/account` where an unknown value is `null`. - Times are Unix **seconds**. - Failure: `{"error": "