# Page Not Found

The URL `introduction-of-nft-in-lucky-heco-event` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [📑How to confirm and use NFT won in Lucky Heco Event](https://docs.nextype.finance/tutorial/introduction-of-nft-in-lucky-heco-event.md)
- [How to add NFT in MetaMask?](https://docs.nextype.finance/tutorial/introduction-of-nft-in-lucky-heco-event/how-to-add-nft-in-metamask.md)
- [⚔️NEO FANTASY Pre-launch Events](https://docs.nextype.finance/neo-fantasy-pre-launch-events.md)
- [Tutorial For NEO FANTASY Pre-launch Events](https://docs.nextype.finance/neo-fantasy-pre-launch-events/tutorial-for-neo-fantasy-pre-launch-events.md)
- [🔥THE ULTIMATE NT BURNING PLAN — 575,000,000 NT To Be Burnt](https://docs.nextype.finance/the-ultimate-nt-burning-plan-575-000-000-nt-to-be-burnt.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://docs.nextype.finance/tutorial/introduction-of-nft-in-lucky-heco-event.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://docs.nextype.finance/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.nextype.finance/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., `/tutorial/introduction-of-nft-in-lucky-heco-event.md`).

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