> 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 [USDX](/overview/usdx.md).

**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 — tick and lot size, margin rates, leverage, funding — for each one.

## Live today

### Crypto — 3 markets

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

Crypto perpetuals trade **continuously** — no daily break and no weekend close. Market identifiers take the form `<BASE>-USDX-PERP`.

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 is the substantive dependency, not the listing decision itself.

## Not listed

**Single-name equities.** The Exchange is designed for equity *index* perpetuals, not perpetuals on individual companies. Nothing in this section should be read as a commitment to list them.

***

<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 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://docs.nexus.xyz/asset-directory/asset-directory.md?ask=<question>&goal=<endgoal>
```

`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.