# Page Not Found

The URL `files/-Mk9cJ3Uno1JBY815Xcs` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [What can you do with your 1POOL tokens?](https://1pool.gitbook.io/1pool-finance/1pool-token-sale-info/what-can-you-do-with-your-1pool-tokens.md)
- [1POOL Tokenomics](https://1pool.gitbook.io/1pool-finance/1pool-tokenomics.md)
- [Token allotment for the ICO and Unsold tokens](https://1pool.gitbook.io/1pool-finance/1pool-token-sale-info/token-allotment-for-the-ico-and-unsold-tokens.md)
- [Risk and Vulnerabilities](https://1pool.gitbook.io/1pool-finance/risk-factors-and-vulnerabilities.md)
- [1POOL Tokenomics - Reward Token emission](https://1pool.gitbook.io/1pool-finance/1pool-tokenomics/1pool-tokenomics-reward-token-emission.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 documentation index with the `ask` parameter:

```
GET https://1pool.gitbook.io/1pool-finance/1pool-token-sale-info/what-can-you-do-with-your-1pool-tokens.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.

### Option 2 — Browse the documentation index

Full index: https://1pool.gitbook.io/1pool-finance/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://1pool.gitbook.io/1pool-finance/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., `/1pool-finance/1pool-token-sale-info/what-can-you-do-with-your-1pool-tokens.md`).

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