> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/readme.md).

# Exchange

A perpetual futures exchange: what it trades, how it prices, and how it manages risk.

The Nexus Exchange is a perpetual futures venue: a central-limit order book with a native matching engine, risk system and oracle, quoted and margined in dollars. On testnet, balances are synthetic [USDX](/overview/usdx.md) from the faucet, which has no real-world value.

> **The API base URL has changed.** The Exchange API moved from `https://exchange.nexus.xyz/api/exchange` to `https://api.testnet.nexus.xyz/v1`. Point your client at the new base. On 2026-09-28, `GET /markets/summary` returned HTTP 500 on the old base and HTTP 200 on the new one. Request signing is unchanged: you sign the path without the base prefix, so `/v1/markets` signs `/markets`, as `/api/exchange/markets` did. See [APIs & rates](/apis-and-rates/apis-and-rates.md).

Start with [Introduction](/overview/introduction.md) for what is live today, or go straight to the mechanics.

|                    |                                                                                                                                                                                                                                                     |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Trade**          | [Quickstart](/trading/trading/quickstart.md) · [Order types](/trading/trading/perpetuals/order-types.md) · [Market Specifications](/trading/trading/perpetuals/market-specifications.md)                                                            |
| **Mechanics**      | [Margining](/trading/trading/perpetuals/margining.md) · [Funding rates](/trading/trading/perpetuals/funding-rates.md) · [Liquidations](/trading/trading/perpetuals/liquidations.md) · [Price oracles](/trading/trading/perpetuals/price-oracles.md) |
| **What is listed** | [Asset directory](/asset-directory/asset-directory.md)                                                                                                                                                                                              |
| **Integrate**      | [APIs & rates](/apis-and-rates/apis-and-rates.md) · [Market maker guide](/apis-and-rates/apis-and-rates/market-maker-guide.md)                                                                                                                      |

The **API Reference** section documents every endpoint, schema and authentication scheme.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexus.xyz/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.