# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Recovery Compensation Plan FAQs](https://recovery-republic.gitbook.io/recovery-republic-docs/faqs/recovery-compensation-plan-faqs.md)
- [General FAQ's](https://recovery-republic.gitbook.io/recovery-republic-docs/faqs/general-faqs.md)
- [Platform & Usage FAQs](https://recovery-republic.gitbook.io/recovery-republic-docs/faqs/platform-and-usage-faqs.md)
- [Program / Product FAQs](https://recovery-republic.gitbook.io/recovery-republic-docs/faqs/program-product-faqs.md)
- [Recovery Participation Rewards](https://recovery-republic.gitbook.io/recovery-republic-docs/recovery-participation-rewards.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://recovery-republic.gitbook.io/recovery-republic-docs/faqs/recovery-compensation-plan-faqs.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://recovery-republic.gitbook.io/recovery-republic-docs/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://recovery-republic.gitbook.io/recovery-republic-docs/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., `/recovery-republic-docs/faqs/recovery-compensation-plan-faqs.md`).

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