> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/markets.md).

# Markets

Draft: review pools before adding them to a strategy.

## Markets

Every pool Brava can deploy into.

This is where a strategy’s holdings come from. Review a pool before you allocate capital.

### What to look for

Trace the collateral. Understand the yield. Assess the exit.

Those questions define the screen. They show what backs a pool, where its return comes from, and how you exit it. A rate alone is not a reason.

### Using it

Filter and sort to narrow the set. Add a pool to a strategy when it fits.

Adding a pool moves nothing. Allocation is a separate, explicit action.

### Liquidity

Where available, Brava shows liquidity depth for a pool. Depth determines how much you can exit at once. It matters more than headline rate at larger sizes.

{% hint style="warning" %}
This draft needs product review. Confirm the available columns, metrics, filters, and data sources before publishing.
{% endhint %}


---

# 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.brava.finance/platform/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.