_PERPETUAL`, e.g. `BTC_USDT_PERPETUAL`. Don't construct these yourself; pull from `get_instruments`. * **Idempotency**: REST order placement is not idempotent today. If you need at-most-once semantics, dedupe on your side using an external nonce. ### Rate limits Per-key limits are enforced server-side and refreshed at short intervals. Limits aren't published publicly because they tune over time; you'll see `429 Too Many Requests` or an equivalent error code when you hit them. If you operate at high request rates, contact the team for an appropriate tier. ### Error envelope REST responses use a uniform envelope: ```json { "status": "OK", "data": { ... } } ``` Errors: ```json { "status": "ERROR", "error": { "code": "INSUFFICIENT_FUNDS", "message": "...", "details": null } } ``` Some `*-by-base-currency` / `*-by-quoted-currency` endpoints return the raw outbox event directly (no envelope). The pages for those endpoints flag this explicitly. System-level failures (Kafka unreachable, internal timeout) return `HTTP 500` with an empty body. The common error codes: | Code | When | | --------------------------------------- | --------------------------------------------------------------------------------- | | `INVALID_REQUEST_DATA` | Malformed JSON or missing required fields. | | `UNAUTHORIZED` | No valid session or API key. | | `INVALID_INSTRUMENT_ID` | Instrument unknown or outside key's allowlist. | | `INSUFFICIENT_FUNDS` | Required margin + fee reserve exceeds `available`. | | `INSTRUMENT_IS_NOT_ACTIVE` | Instrument paused. | | `IN_EMERGENCY_MODE` | Engine in emergency mode; see [Mark price](/agentdex-docs/trading/mark-price.md). | | `AMOUNT_TOO_SMALL` | Below the instrument's minimum order size. | | `ORDER_VOLUME_MISMATCHES_CONTRACT_SIZE` | Volume not a multiple of contract size (contract-sized mode). | ### Picking a surface Start with MCP if you're driving from an LLM. Start with REST if you have an existing exchange-client codebase to port. Layer in WebSocket once you need to react to fills and price moves below the request-response loop. --- # 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://agentdex.gitbook.io/agentdex-docs/developers/api-overview.md?ask=&goal= ``` `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.