rwa.wtfdocs
MCP

Trade

Read an account and submit orders through the rwa.wtf MCP.

Trade is the higher-permission MCP scope. A Trade key includes every Intel route, then adds 6 tools for account data and order management, 37 tools total. It uses the same MCP endpoint and the same market-data routes as an Intel key.

The additional Trade routes can submit orders with real funds on the connected account. Use an Intel key when an agent only needs research data.

Connect · View Intel routes · View Trade routes

Trade routes

Account data

ToolReturns
get_account_snapshotCollateral, available balance, committed margin, margin requirements, positions, leverage, liquidation prices, assets, and order counts
get_account_activityActive orders, inactive orders, fills, and funding history

Call get_account_snapshot before sizing or closing an order. get_account_activity does not return current balances or positions.

Orders

ToolRequired inputResult
place_ordermarketId, side, kind, quantity, leveragePlaces 1 order
cancel_ordermarketId, clientOrderIndexCancels 1 resting order
cancel_all_ordersmarketIdCancels every resting order in 1 market
modify_ordermarketId, clientOrderIndex, quantity, priceReprices or resizes 1 resting order

quantity, price, and triggerPrice are decimal strings. Call get_markets for current market IDs, quantity precision, price precision, and leverage limits.

Place order fields

FieldValues
sidebuy, sell
kindmarket, limit, stop-loss, stop-loss-limit, take-profit, take-profit-limit, twap
leverage1 to 100, subject to the market limit
reduceOnlyPrevents the order from increasing exposure
postOnlyValid for resting orders, not market orders
expiryMs0 for good till canceled
slippageBps1 to 500, default 5
idempotencyKeyReuse the same value when retrying the same order

price is required for limit and TWAP orders. triggerPrice is required for stop and take-profit orders.

  1. Call get_markets and identify the market ID.
  2. Call get_account_snapshot and check available collateral, current exposure, margin, and leverage.
  3. Submit the order with an explicit quantity and idempotency key.
  4. Call get_account_activity to confirm its status and obtain client_order_index.
  5. Modify or cancel a resting order with clientOrderIndex.
  6. Call get_account_snapshot again to verify the final position and margin state.

Order handling

  • The venue generally rejects orders below $10. Market-specific quantity minimums also apply.
  • place_order creates 1 order. It does not attach a stop-loss or take-profit bracket.
  • To protect an open position, submit a separate reduce-only stop-loss or take-profit order after the entry fills.
  • Use client_order_index from get_account_activity for cancel and modify calls. Do not use order_index, it can exceed the range represented safely by JSON numbers.
  • cancel_all_orders removes resting orders in 1 market. It does not close a position.
  • A market order can fill before a response is received. Do not retry it with a new idempotency key.

Permissions

Trade keys can read their own venue account and submit, modify, or cancel orders. They cannot:

  • Deposit funds
  • Withdraw funds
  • Add a withdrawal address
  • Start a venue migration
  • Read the browser session
  • Create or revoke API keys

Funding, withdrawals, migration, and key management require an authenticated browser session. No MCP tool can move funds off the venue.

Limits and revocation

Trade keys share the account limits documented on the Intel page. Account and order calls also count toward the broader 60-request rolling-minute limit.

Revoking a key stops new requests immediately. It does not cancel resting orders or close positions. Review the account in the terminal before revoking a key that has traded.

On this page