# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [2.1 Mission Objectives](https://billiard-hub.gitbook.io/docs/2.-mission/2.1-mission-objectives.md)
- [11.2 Key NFT Types and Use Cases](https://billiard-hub.gitbook.io/docs/11.-nft-and-digital-asset-strategy/11.2-key-nft-types-and-use-cases.md)
- [15.1 Platform Development Timeline](https://billiard-hub.gitbook.io/docs/15.-roadmap-and-future-plans/15.1-platform-development-timeline.md)
- [6.9 Automated Billiard Hall System: Overview & Revenue Model](https://billiard-hub.gitbook.io/docs/6.-business-model/6.9-automated-billiard-hall-system-overview-and-revenue-model.md)
- [6.6 NFT and Digital Content Sales](https://billiard-hub.gitbook.io/docs/6.-business-model/6.6-nft-and-digital-content-sales.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://billiard-hub.gitbook.io/docs/2.-mission/2.1-mission-objectives.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://billiard-hub.gitbook.io/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://billiard-hub.gitbook.io/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., `/docs/2.-mission/2.1-mission-objectives.md`).

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