# Use Cases

## This page has been deprecated. V1 documentation is partially maintained [here](https://docs.balancer.fi/v/v1/getting-started/use-cases)

## Use Cases

There are two categories of users who can benefit from the Balancer Protocol: liquidity providers - who own Balancer Pools or participate in shared pools, and traders - who buy or sell the underlying pool assets on the open market.

Anyone can be a liquidity provider. For example:

* Portfolio managers, who want to have controlled exposure to different assets without complicated and expensive rebalancing&#x20;
* Investors who have ERC20 tokens sitting idly in a wallet, and would like to put them to work earning passive income from fees&#x20;

Traders can choose from a diverse set of pools, each presenting a unique set of investment opportunities and challenges through its particular configuration of tokens, weights, and fees. The interplay between these settings, pool volume, and external prices generates market forces which incentivize traders to maintain stable token ratios, thereby preserving asset value for liquidity providers.

There are three main categories:

* "Retail" traders seeking to exchange tokens with low slippage at favorable rates
* Arbitrageurs seeking profit through leveling market inefficiencies between DEXs or CEXs&#x20;
* Ethereum smart contracts seeking liquidity for a variety of reasons, such as liquidating positions on other protocols, trading on behalf of users, etc.&#x20;


---

# Agent Instructions: 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:

```
GET https://balancer.gitbook.io/balancer/getting-started/use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
