# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [4.5. Intellectual Property Rights](https://qrdano.gitbook.io/qr-paper/4.-nft-collections/4.5.-intellectual-property-rights.md)
- [4.2. “Pieces of the Puzzle” Utility NFT](https://qrdano.gitbook.io/qr-paper/4.-nft-collections/4.2.-pieces-of-the-puzzle-utility-nft.md)
- [4.3. “See the Unseen” Utility NFT](https://qrdano.gitbook.io/qr-paper/4.-nft-collections/4.3.-see-the-unseen-utility-nft.md)
- [4.1. Storyline NFT Collection](https://qrdano.gitbook.io/qr-paper/4.-nft-collections/4.1.-storyline-nft-collection.md)
- [6.2. Example of Incentive Distribution](https://qrdano.gitbook.io/qr-paper/6.-community-wallet/6.2.-example-of-incentive-distribution.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://qrdano.gitbook.io/qr-paper/4.-nft-collections/4.5.-intellectual-property-rights.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://qrdano.gitbook.io/qr-paper/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://qrdano.gitbook.io/qr-paper/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., `/qr-paper/4.-nft-collections/4.5.-intellectual-property-rights.md`).

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