> For the complete documentation index, see [llms.txt](https://hyperliquid-co.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperliquid-co.gitbook.io/wiki/guide/builder-guide/hypercore/endpoints/info/spot.md).

# Spot

The **Spot** section of the `/info` endpoint provides details about **L1 Spot markets** on Hyperliquid. To make sense of the data structure, I have created the diagram below to visually represent the relationships between key objects.

🔗 **For full API details:** [Spot Endpoint Documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint/spot)

<figure><img src="/files/q00cxKcnPmjEvSx5Mflx" alt=""><figcaption></figcaption></figure>

**📌 Understanding Asset IDs in the Spot API**

Interpreting asset identifiers across the different API responses can be confusing. The diagram above helps clarify these relationships.

* The **"token"** field in `spotClearinghouseState` (e.g., `"token": 1105`) corresponds to the **index of that token ID in** **the** `"token"` **array of** `spotMeta`. You can find more details about the token in this **category** of data.
* Additionally, each asset is part of a **trading pair**, which is represented under `universe`.

**🔹 Key Points**

* All **universe indexes** are **numbers**, except **PURR/USDC**, which is an exception.
* The `"name"` field in `universe` is **@{index}**, but this index **differs from the token index** in `spotMeta`. Each trading pair has its **own unique index** within the `universe`.
* The `"name"` field in `tokens` represents the **coin (perp name)** of the asset.

**🔹 Spot Asset ID Calculation**

For spot endpoints, the **asset ID** is derived as follows:

```plaintext
spot_asset_id = 10000 + spotInfo["index"]
```

Where `spotInfo` is the object containing the desired **quote** and **base** tokens.

**Example: HYPE Token Asset IDs**

|              | **Mainnet** | **Testnet** |
| ------------ | ----------- | ----------- |
| **Token ID** | `150`       | `1105`      |
| **Spot ID**  | `107`       | `1035`      |

This distinction is crucial when submitting orders or querying data.


---

# 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://hyperliquid-co.gitbook.io/wiki/guide/builder-guide/hypercore/endpoints/info/spot.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.