# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Understanding Market Cap Requirements](https://pumpxbounty.gitbook.io/pumpxbountydocs/6.-advanced-features/understanding-market-cap-requirements.md)
- [Predicting Market Movements](https://pumpxbounty.gitbook.io/pumpxbountydocs/4.-how-to-place-bets/predicting-market-movements.md)
- [Wallet Connection Issues](https://pumpxbounty.gitbook.io/pumpxbountydocs/7.-troubleshooting/wallet-connection-issues.md)
- [Common Problems](https://pumpxbounty.gitbook.io/pumpxbountydocs/7.-troubleshooting/common-problems.md)
- [Introduction](https://pumpxbounty.gitbook.io/pumpxbountydocs/1.-introduction/introduction.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://pumpxbounty.gitbook.io/pumpxbountydocs/6.-advanced-features/understanding-market-cap-requirements.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://pumpxbounty.gitbook.io/pumpxbountydocs/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://pumpxbounty.gitbook.io/pumpxbountydocs/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., `/pumpxbountydocs/6.-advanced-features/understanding-market-cap-requirements.md`).

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