# Page Not Found

The URL `about-shuttleone/case-studies` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Case Studies](https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/cross-chain-to-real-world/case-studies.md)
- [Cross-chain to Real world](https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/cross-chain-to-real-world.md)
- [Metachain- Cross-chain interoperability](https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/metachain-cross-chain-interoperability.md)
- [Plug N Play DeFi](https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/cross-chain-to-real-world/fly-shuttleone.md)
- [Distribution & Structure](https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/the-shuttleone-token/structure.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://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/cross-chain-to-real-world/case-studies.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://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://shuttleone.gitbook.io/step-by-step-guide-to-the-shuttleone-network/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., `/step-by-step-guide-to-the-shuttleone-network/about-shuttleone/cross-chain-to-real-world/case-studies.md`).

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