# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [CySEC: MiCA Legislation Hub](https://www.mica.wtf/national-competent-authorities/cysec/markets-in-crypto-assets-legislation-hub.md)
- [CBI: CASP Key Facts Document](https://www.mica.wtf/national-competent-authorities/cbi/casp-key-facts-document-guidance.md)
- [CBI: ART Key Facts Document](https://www.mica.wtf/national-competent-authorities/cbi/art-key-facts-document.md)
- [BaFin Merkblatt: Crypto Services (DE)](https://www.mica.wtf/national-competent-authorities/bafin/merkblatt-kryptowerte-dienstleistungen-nach-micar.md)
- [EBA/GL/2024/13 — Issuer Redemption Plans](https://www.mica.wtf/eu-level/guidelines/guidelines-on-redemption-plans-under-micar.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://www.mica.wtf/national-competent-authorities/cysec/markets-in-crypto-assets-legislation-hub.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://www.mica.wtf/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://www.mica.wtf/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., `/national-competent-authorities/cysec/markets-in-crypto-assets-legislation-hub.md`).

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