> For the complete documentation index, see [llms.txt](https://elysia.gitbook.io/elysia-perps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elysia.gitbook.io/elysia-perps/mechanics/charts.md).

# Charts (OHLCV)

The price chart is built from **OHLCV candles**: for each time interval, the **O**pen, **H**igh, **L**ow, and **C**lose price plus the traded **V**olume.

## Where the candles come from

Candles are built from the **actual trades that fill on this market's order book**, not from an external feed. They reflect what really traded here, so the chart matches the fills and the last traded price. (This is distinct from the index and mark prices in [Mark & Oracle Price](/elysia-perps/mechanics/mark-and-oracle.md), which are reference prices, not the traded price.)

## Available intervals

| Group   | Intervals        |
| ------- | ---------------- |
| Minutes | 1m, 5m, 15m, 30m |
| Hours   | 1h, 4h           |
| Days    | 1d, 1w           |

The 1-minute candle is the base record; longer intervals are assembled from it, so all timeframes stay consistent with one another. The set of intervals is a platform-wide setting on Elysia Perps.

## Reading a candle

* **Open / Close**: the first and last trade price within the interval.
* **High / Low**: the highest and lowest trade price within the interval.
* **Volume**: how much traded during the interval.

An interval with no trades carries the previous close forward, so the chart has no gaps.

## Where to go next

* The reference prices behind margin and funding: [Mark & Oracle Price](/elysia-perps/mechanics/mark-and-oracle.md).
* Back to the trading basics: [Markets](/elysia-perps/trading/markets.md).


---

# 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://elysia.gitbook.io/elysia-perps/mechanics/charts.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.