# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Markdown](https://khamphanhatban.gitbook.io/khamphanhatban/basics/markdown.md)
- [OpenAPI](https://khamphanhatban.gitbook.io/khamphanhatban/basics/openapi.md)
- [Lễ Hội Cá Chép – Văn Hoá Độc Đáo Tại “Xứ Phù Tang”](https://khamphanhatban.gitbook.io/khamphanhatban/quickstart/le-hoi-ca-chep-van-hoa-doc-dao-tai-xu-phu-tang.md)
- [Khám phá bảo tàng Doraemon – Hành trình trở về tuổi thơ](https://khamphanhatban.gitbook.io/khamphanhatban/quickstart/kham-pha-bao-tang-doraemon-hanh-trinh-tro-ve-tuoi-tho.md)
- [Tour du lịch Nhật Bản 3 ngày 2 đêm: Khám phá thủ đô Tokyo](https://khamphanhatban.gitbook.io/khamphanhatban/quickstart/tour-du-lich-nhat-ban-3-ngay-2-dem-kham-pha-thu-do-tokyo.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://khamphanhatban.gitbook.io/khamphanhatban/basics/markdown.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://khamphanhatban.gitbook.io/khamphanhatban/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://khamphanhatban.gitbook.io/khamphanhatban/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., `/khamphanhatban/basics/markdown.md`).

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