AGENT SKILL

paradex-api

Paradex, the Starknet perpetual futures and options exchange: markets, order book, account, positions, fills, funding, and placing and cancelling orders. Use for ANY Paradex request. The tools are `paradex__*` MCP tools, called by exact name. For a data feed or other script, follow datafeeds/GUIDE.md instead: a script cannot call the tools. NOT Paradigm: an RFQ or a block trade is paradigm-rfq-trader even when it settles on Paradex.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
paradex-api
metadata
{ "author": "tradeparadigm" }
description
Paradex, the Starknet perpetual futures and options exchange: markets, order book, account, positions, fills, funding, and placing and cancelling orders. Use for ANY Paradex request. The tools are `paradex__*` MCP tools, called by exact name. For a data feed or other script, follow datafeeds/GUIDE.md instead: a script cannot call the tools. NOT Paradigm: an RFQ or a block trade is paradigm-rfq-trader even when it settles on Paradex.

02 资源文件 10

03 SKILL.md 正文

Paradex

Every Paradex read and write goes through the paradex MCP server. The server signs for you. Do not look for credentials, environment variables or a CLI. Call a tool with tool_call, passing its exact name below as id and its arguments as args. You do not need tool_search or tool_describe.

Data feeds and other scripts

For a data feed, or any script that reads Paradex, run the notification-feed skill's feeds.mjs init <name> --from paradex, then follow datafeeds/GUIDE.md in this skill's folder. Use these instead of the paradex__ tools: a script cannot call them.

The user's positions, already fetched

Where the posman skill tracks a Paradex account, its positions, open orders, balances and account summary are already on disk, refreshed on an interval: read them with posman.mjs show (one call, every venue) before calling the account tools. Read them fresh before sizing or placing an order. To track an account, posman's adapter for Paradex is paradex/account (posman/account/ in this skill's folder; its POSMAN.md says how to read each field).

Paradex is not Paradigm

Paradex is an exchange with an order book. Paradigm is an institutional RFQ platform, and Paradex is one of the venues it settles on. An RFQ, a block trade, a quote or crossing a quote is Paradigm: use paradigm-rfq-trader. An order on the book, a position, a fill or market data is Paradex: you are in the right place.

Tools

? marks an optional argument.

Account

  • paradex__paradex_account_summary(): account value, margin, leverage
  • paradex__paradex_account_balance(): token balances
  • paradex__paradex_account_positions(): open positions
  • paradex__paradex_account_overview(): summary, balances, positions, fees and margin mode in one call
  • paradex__paradex_account_fills(market_id, start_unix_ms, end_unix_ms): your executions
  • paradex__paradex_account_funding_payments(market_id?, start_unix_ms, end_unix_ms): funding paid and received
  • paradex__paradex_account_transactions(transaction_type?, start_unix_ms, end_unix_ms, limit?): deposits, withdrawals, transfers and other activity

Orders

  • paradex__paradex_open_orders(market_id?, limit?, offset?): resting orders
  • paradex__paradex_orders_history(market_id, start_unix_ms, end_unix_ms): past orders
  • paradex__paradex_order_status(order_id, client_id): one order. Pass "" for whichever id you do not have
  • paradex__paradex_create_order(market_id, order_side, order_type, size, price, trigger_price, instruction?, reduce_only?, client_id): place an order
  • paradex__paradex_cancel_orders(order_id?, client_id?, market_id?): cancel one order, or every order in a market
  • paradex__paradex_trade_preview(market_id, side, size, margin_methodology?): readiness checks and margin before and after a trade; run it before placing one

order_side is BUY or SELL. order_type is one of MARKET, LIMIT, STOP_LIMIT, STOP_MARKET, TAKE_PROFIT_LIMIT, TAKE_PROFIT_MARKET, STOP_LOSS_MARKET, STOP_LOSS_LIMIT. instruction is GTC (the default), POST_ONLY, IOC or RPI.

Market data

  • paradex__paradex_markets(market_ids?, jmespath_filter?, limit?, offset?): instruments, tick size, minimum notional
  • paradex__paradex_market_summaries(market_ids?, jmespath_filter?, limit?, offset?): mark price, 24h volume, open interest, underlying_price
  • paradex__paradex_bbo(market_id): best bid and offer
  • paradex__paradex_orderbook(market_id, depth?): book depth
  • paradex__paradex_klines(market_id, resolution?, start_unix_ms, end_unix_ms): candles; resolution is minutes, one of 1, 3, 5, 15, 30, 60
  • paradex__paradex_funding_data(market_id, start_unix_ms, end_unix_ms): funding rate history
  • paradex__paradex_trades(market_id, start_unix_ms, end_unix_ms): public trades

Market symbols look like ETH-USD-PERP. Take exact names from paradex__paradex_markets.

Venue facts

  • Times are unix milliseconds. Run date +%s%3N for now before you build a window.
  • A tool that takes a window returns the first page and drops the cursor. A full page may have more behind it: halve the window and read each half. A fills page holds 100 rows.
  • Minimum notional and tick size come from paradex__paradex_markets. Check them before sizing an order.
  • create_order needs trigger_price as a number. Pass 0 when the order type has no trigger. A MARKET order takes price: 0.
  • client_id is required on create_order. Make one up per order and keep it, so order_status and cancel_orders can find the order.
  • Post-only is instruction: "POST_ONLY". Reduce-only is reduce_only: true.
  • cancel_orders with no arguments cancels every open order in every market. Name the order or the market unless the user asked for all of it.
  • Placing an order needs the signing key. The read-only token reads only.

When there are no paradex__ tools

The server did not start for this account. Tell the user which of these applies, cheapest to check first:

  • The change has not reached the agent yet. Ask the user to reload, or retry shortly.
  • No Paradex credential is enrolled.
  • The credential was enrolled with a custom host. Only a credential for one of the app's environments (mainnet, testnet, nightly) starts the server.
  • The credential is missing its account address, or a signing key is missing its public key.
  • Another MCP server is already named paradex.

Anything not covered here

Paradex's API reference is at https://docs.paradex.trade. Use it for margin rules, fee tiers and order semantics.

04 同仓库更多 Skills

tradeparadigm
tradeparadigm/dt-apps

example-api

A skill body that exists so the fixture is a complete app. It teaches nothing and is never published.

★ 0
tradeparadigm
tradeparadigm/dt-apps

telegram-bot

Send messages, photos and files to Telegram through the user's own bot, using a bot token held by the DIME credential proxy. Covers finding the chats the bot can reach, posting to a private chat, group or channel, editing and deleting what it sent, and sending from a data feed. Use for ANY request to message, notify or alert the user on Telegram, "send this to my Telegram", "post alerts to my channel", or a 403 from the credential proxy on api.telegram.org.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-rfq-trader

Trigger institutional block trades via Paradigm's DRFQv2 flow. The workflow is venue-agnostic — resolve instruments, build the RFQ / order payload, benchmark, run a confirmation gate, submit, verify settlement. Per-venue specifics (fair-value sources, naming conventions, edge syntax, settlement checks) live in references/venues.md. In scope today: PRDX (Paradex, primary focus) and DBT (Deribit). Adding more DRFQv2 venues is a references/venues.md edit, not a skill-body change. Covers takers (build, benchmark, cross) and makers (poll, price, manage). Every state-changing action goes through an explicit confirmation gate. Needs both Paradigm credentials enrolled. Use when the user asks to "send a Paradigm block RFQ", "block-trade X BTC", "send a BTC straddle on Paradex / Deribit", "quote rfq_X", "hit the best bid", "cancel rfq_X". Does NOT cover pricing a structure without trading (its legs' current marks are paradigm-data-discovery's), small central-order-book trades, post-trade analysis (paradigm-block-analyst), historical tape (paradigm-data-discovery).

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-options-recap

Options market recap for a requested or default window, invoked via /recap. Parses "/recap [asset] [options] [window]" (e.g. "/recap btc options 8h") and builds the fixed four-section recap — Snapshot, Biggest Print, Block Flow, Vol Surface — from bounded raw exchange venue files and source tapes, never from Dime hot files, read with the pod's AWS access. Use when the user types /recap or asks for a market recap, an options flow summary, "what happened in BTC options" or "last Xh of flow". A single question is not a recap: the biggest print across venues is paradigm-data-discovery's (paradigm-api reads only Paradigm's own tape), and the vol surface, one IV or one venue's data is paradigm-data-discovery's, as are dataset inventory, schema and historical lookups. The output format is fixed — always the same four sections in the same order.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-data-discovery

Catalog and query launcher for raw market data available to Dime in s3://dt-exchange-venue-data, s3://dt-paradigm-data, and s3://dt-paradex-data, read with the pod's AWS access. Use for data inventory, coverage, schema and historical analysis, for current venue market data (marks, IV, greeks, OI, funding, spot) on Deribit, OKX, Bybit and Bullish, and for recent block trades when the user has no Paradigm credentials enrolled (with them, paradigm-api reads the live tape). Explains the per-venue raw files and lets the model choose the bounded reads needed for the question. Does not cover account state, positions, vaults, or order placement.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-block-analyst

Cross-venue analysis of Paradigm RFQ block trades using live market data from Deribit, OKX, and Bybit. Invoked as `/analyze <rfq_id> <rfq description>`: resolves the rfq_id by searching the Paradigm trade tape via the paradigm-data-discovery skill (the daily execution partitions, keyed by RFQ_ID) for the cleared-block record, then fetches live marks, IVs, and greeks per venue, computes net greeks for multi-leg structures, benchmarks the fill vs mark, reports how much of the structure traded over 24h / 7d / 30d and where else it printed, reads whether the flow moved the vol surface, and outputs a concise analysis. Use when the user runs `/analyze <rfq_id> ...`, pastes a Paradigm block trade JSON, or asks to analyze, benchmark, or get market color on a Paradigm RFQ execution. Covers outright calls/puts (CL/PL), strangles (SN), straddles (ST), butterflies (BF), condors (CO), calendars (CA), risk reversals (RR), covered calls, and custom multi-leg combos (CM). Also handles perp combos. Reads the Paradigm trade tape from S3 with the pod's AWS access.

★ 0