> For the complete documentation index, see [llms.txt](https://docs.flash.trade/flash-trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flash.trade/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/concepts/prices-and-markets.md).

# Prices & markets

Where prices come from and how equity market hours are surfaced.

## Prices

Prices come from **Pyth Lazer** feeds, filtered to the tokens present in the pool config. Read them with [`GET /prices`](/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/reference/market-data.md#prices) or [`GET /prices/{symbol}`](/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/reference/market-data.md#prices-symbol).

Each price is an integer plus an exponent — apply `price × 10^exponent`, or just read `priceUi`:

```json
{ "price": 54812000000, "exponent": -8, "priceUi": 548.12, "marketSession": "regular", "timestampUs": 1717407600000000 }
```

## Market sessions

Some markets are equities (e.g. SPY, MSTR, CRCL) that only trade during market hours. Every price carries a `marketSession` so you can reflect the current session in your UI:

| Value        | Meaning               |
| ------------ | --------------------- |
| `regular`    | Regular trading hours |
| `preMarket`  | Pre-market session    |
| `postMarket` | After-hours session   |
| `overNight`  | Overnight session     |
| `closed`     | Market closed         |

When a market is closed and has no fresh price, price and trade endpoints for that symbol can return `503`.

## Markets

A market is a `(target custody, collateral custody, side)` triple. You never construct that yourself — pass `marketSymbol` + `side` and the backend resolves the market against the live pool config. Enumerate raw markets, pools, and custodies under [Market data](/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/reference/market-data.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://docs.flash.trade/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/concepts/prices-and-markets.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.