# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [₿ Private](https://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/upcoming-utilities/private.md)
- [Upcoming Utilities](https://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/upcoming-utilities.md)
- [BitLand P2E](https://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/upcoming-utilities/bitland-p2e.md)
- [BitLand DAO](https://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/bitland-dao.md)
- [BitLand Protocol](https://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/upcoming-utilities/bitland-protocol.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://bitland-whitepaper.gitbook.io/bitland-whitepaper/bitland-ecosystem/upcoming-utilities/private.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://bitland-whitepaper.gitbook.io/bitland-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://bitland-whitepaper.gitbook.io/bitland-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., `/bitland-whitepaper/bitland-ecosystem/upcoming-utilities/private.md`).

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