# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [5.2 Educational Resources](https://gpt-protocol.gitbook.io/gpt-protocol/5.-support-and-resources/5.2-educational-resources.md)
- [3.1 Joining the GPT Protocol Community](https://gpt-protocol.gitbook.io/gpt-protocol/3.-community-and-governance/3.1-joining-the-gpt-protocol-community.md)
- [6.2 Privacy Policy](https://gpt-protocol.gitbook.io/gpt-protocol/6.-legal-and-compliance/6.2-privacy-policy.md)
- [1.3 Exploring $GPT Tokens and Blockchain](https://gpt-protocol.gitbook.io/gpt-protocol/1.-welcome-to-gpt-protocol/1.3-exploring-usdgpt-tokens-and-blockchain.md)
- [1.2 The GPT Protocol Ecosystem](https://gpt-protocol.gitbook.io/gpt-protocol/1.-welcome-to-gpt-protocol/1.2-the-gpt-protocol-ecosystem.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://gpt-protocol.gitbook.io/gpt-protocol/5.-support-and-resources/5.2-educational-resources.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://gpt-protocol.gitbook.io/gpt-protocol/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://gpt-protocol.gitbook.io/gpt-protocol/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., `/gpt-protocol/5.-support-and-resources/5.2-educational-resources.md`).

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