# Page Not Found

The URL `key-features/for-liquidity-providers` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [6.4 - Add Liquidity — Automated](https://docs.usenest.xyz/tutorials/6.4-add-liquidity-automated.md)
- [6.2 - Add Liquidity — Classic](https://docs.usenest.xyz/tutorials/6.2-add-liquidity-classic.md)
- [6.3 - Add Liquidity — CLAMM](https://docs.usenest.xyz/tutorials/6.3-add-liquidity-clamm.md)
- [6.5 - Remove Liquidity / Exit](https://docs.usenest.xyz/tutorials/6.5-remove-liquidity-exit.md)
- [7.2 - Security Model](https://docs.usenest.xyz/protocol-and-security/7.2-security-model.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usenest.xyz/tutorials/6.4-add-liquidity-automated.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.

### Option 2 — Browse the documentation index

Full index: https://docs.usenest.xyz/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.usenest.xyz/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/tutorials/6.4-add-liquidity-automated.md`).

You may also use `Accept: text/markdown` header for content negotiation.