> For the complete documentation index, see [llms.txt](https://everfall.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everfall.gitbook.io/docs/collections/mint.md).

# Mint information

This would be Everfall's first community collection. Price, package and launch details are still being decided. **There is no active mint or announced sale date.**

The collection has no confirmed position in the gameplay release schedule. Referral onboarding comes first; any eligible dungeon event would require a separately announced playable test.

The working proposal is below. Supply and pricing remain redacted until announced.

## Earn your place

Your first adventures could lead to more than loot. We are exploring ways for dungeon challenges and community participation to unlock Firstbound mint access.

The qualifying event and requirements will be announced before it begins. Current playtest runs do not count toward an allocation.

## Supply & pricing

| Detail       | Announcement |
| ------------ | ------------ |
| Total supply | ???          |
| Mint price   | ???          |
| Allocations  | ???          |

Details will be revealed before any sale opens.

## What the mint would support

Funds would support development, art, sound, servers, testing and community support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://everfall.gitbook.io/docs/collections/mint.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.