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

# App Guide

This guide contains all the information necessary to interact with all aspects of Auto Finance.

## Autopools 

Learn how to provide liquidity with Autopools and take advantage of their powerful LP optimization.

[Read more](/using-the-app/app-guide/autopools.md)

## Staking AUTO

Stake **AUTO** to receive **sAUTO** and participate in the protocol’s current staking and reward system. This section walks through staking, viewing positions, managing withdrawals, and understanding rewards in the app.

[Read more](/auto-pools-protocol/staking-auto.md)

## AUTO/ETH LP

AUTO/ETH is now a Uniswap v4 pool, migrated from the old TOKE/ETH Sushiswap LP. 

[Read more](/using-the-app/app-guide/auto-eth-lp.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.auto.finance/using-the-app/app-guide.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.