# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [🪂 Token Airdrop (Beta)](https://bull-byte-protocol.gitbook.io/bull-byte-protocol/bull-byte-protocol-tools/token-airdrop-beta.md)
- [Token vesting](https://bull-byte-protocol.gitbook.io/bull-byte-protocol/bull-byte-protocol-tools/token-vesting.md)
- [🚰 How to Manage Liquidity](https://bull-byte-protocol.gitbook.io/bull-byte-protocol/markdown/how-to-manage-liquidity.md)
- [Socials](https://bull-byte-protocol.gitbook.io/bull-byte-protocol/bull-byte-protocol-tools/socials.md)
- [Copy of Page 4](https://bull-byte-protocol.gitbook.io/bull-byte-protocol/bull-byte-protocol-tools/openapi/copy-of-page-4.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://bull-byte-protocol.gitbook.io/bull-byte-protocol/bull-byte-protocol-tools/token-airdrop-beta.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://bull-byte-protocol.gitbook.io/bull-byte-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://bull-byte-protocol.gitbook.io/bull-byte-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., `/bull-byte-protocol/bull-byte-protocol-tools/token-airdrop-beta.md`).

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