# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Privacy Policy](https://solar-studios.gitbook.io/solar-studios/additional-information/privacy-policy.md)
- [Web3 Integration with Altura](https://solar-studios.gitbook.io/solar-studios/solar-dominion/web3-integration-with-altura.md)
- [Liquidity Pools & Fee Structure](https://solar-studios.gitbook.io/solar-studios/solar-dex/liquidity-pools-and-fee-structure.md)
- [Airdrop & Rewards Guidelines prior to TGE](https://solar-studios.gitbook.io/solar-studios/introduction-welcome-to-solar-studios/airdrop-and-rewards-guidelines-prior-to-tge.md)
- [Solar Manga](https://solar-studios.gitbook.io/solar-studios/introduction-welcome-to-solar-studios/solar-manga.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://solar-studios.gitbook.io/solar-studios/additional-information/privacy-policy.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://solar-studios.gitbook.io/solar-studios/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://solar-studios.gitbook.io/solar-studios/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., `/solar-studios/additional-information/privacy-policy.md`).

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