> 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/asset-directory/asset-directory.md).

# Asset directory

The markets that are live on the Nexus Exchange today, and the asset classes that follow.

Every market on the Exchange is a perpetual future, quoted and margined in dollars.

**This page lists what is live.** `GET /markets` is the authority at any moment, and [Market Specifications](/trading/trading/perpetuals/market-specifications.md) carries the contract specification for each one: tick and lot size, margin rates, leverage, funding.

## Live today

### Crypto: 3 markets

| Market          | Underlying |
| --------------- | ---------- |
| `BTC-USDX-PERP` | Bitcoin    |
| `ETH-USDX-PERP` | Ether      |
| `SOL-USDX-PERP` | Solana     |

Crypto perpetuals trade **continuously**, with no daily break and no weekend close. Market identifiers take the form `<BASE>-USDX-PERP`, where [USDX](/overview/usdx.md) is the dollar unit the Exchange accounts in.

Margin rates and leverage ceilings are **per market**, not per class. `SOL-USDX-PERP` carries a different profile from the two majors. Read them from [Market Specifications](/trading/trading/perpetuals/market-specifications.md) or `GET /markets/{market_id}/risk-params` rather than assuming a class-wide value.

## Coming as the set expands

Two further classes are planned, in this order. Neither is listed today, and nothing below is a commitment to a date.

| Class                  | Status                                                                                                                                                                                                                 |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Equity indices**     | Planned. Index perpetuals rather than single-name equities.                                                                                                                                                            |
| **Pre-IPO perpetuals** | Planned. Needs mechanics the venue has not defined publicly: a settlement rule for the listing event itself, and a policy for extraordinary events where an anticipated listing is cancelled, delayed or restructured. |

Both classes track underlyings that **do not trade continuously**, so listing them requires session and calendar handling the venue does not enforce yet. See [Trading hours](/trading/trading/perpetuals/trading-hours.md). That handling, not the listing decision itself, is the real dependency.

***

<sub>Forward-looking statement. Any market or asset class described here as planned is an estimate only, subject to change without notice, and may differ materially from actual outcomes.</sub>


---

# 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 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/asset-directory/asset-directory.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 `automate deployments from our CI pipeline` 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.