# Page Not Found

The URL `bitrgb-doc/project-overview/bitrgb` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [3 Overview of SATPORT](https://bitrgb.gitbook.io/satport-docs-1/3-overview-of-satport.md)
- [4.1.1 Private Key Sharding](https://bitrgb.gitbook.io/satport-docs-1/4-satport-technical-architecture/4.1-hyper-scalability-solution-zk-hss/4.1.1-private-key-sharding.md)
- [2.1 Limited Empowerment of BTC Native Assets](https://bitrgb.gitbook.io/satport-docs-1/2-limitations-of-btc-and-btc-pegged-assets/2.1-limited-empowerment-of-btc-native-assets.md)
- [4.1.3 "Peg-In" Process](https://bitrgb.gitbook.io/satport-docs-1/4-satport-technical-architecture/4.1-hyper-scalability-solution-zk-hss/4.1.3-peg-in-process.md)
- [8 RaaS Strategy](https://bitrgb.gitbook.io/satport-docs-1/8-raas-strategy.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://bitrgb.gitbook.io/satport-docs-1/3-overview-of-satport.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://bitrgb.gitbook.io/satport-docs-1/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://bitrgb.gitbook.io/satport-docs-1/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., `/satport-docs-1/3-overview-of-satport.md`).

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