# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Introduction](https://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/introduction.md)
- [Partnership #1 - “Join the Planet” RWA (JTP RWA)](https://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/partnership-1-join-the-planet-rwa-jtp-rwa.md)
- [Our Community - The Planeteers](https://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/our-community-the-planeteers.md)
- [Partnership Highlights](https://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/partnership-highlights.md)
- [$PLANET Ecosystem & Token Utilities](https://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/usdplanet-ecosystem-and-token-utilities.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://planet-refi.gitbook.io/planet-refi-whitepaper/whitepaper/introduction.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://planet-refi.gitbook.io/planet-refi-whitepaper/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://planet-refi.gitbook.io/planet-refi-whitepaper/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., `/planet-refi-whitepaper/whitepaper/introduction.md`).

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