> For the complete documentation index, see [llms.txt](https://docs.jrny.club/jrny-club/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jrny.club/jrny-club/the-planet-xolo-ecosystem/xolo-keys.md).

# XOLO Keys

<figure><img src="/files/Crq1jwxTijLSLXx7v5ae" alt=""><figcaption></figcaption></figure>

> [XOLO Keys](https://opensea.io/collection/xolo-keys) is a collection of up to 10,000 Key Cards that was airdropped to all JRNY Club holders. The Keys can be[ exchanged](https://planetxolo.com/claim/) (burned) for a Planet XOLO NFT or kept as a collectible.  The window is opened indefinitely for exchanging Keys.  These Keys can be obtained via [OpenSea](https://opensea.io/assets/ethereum/0x40875223d61a688954263892d0f76c94fd6b3d4a/1).&#x20;
>
> &#x20;
>
> Holding a Key yields additional Stardust within the JRNY Club Discord server but does not stack based on the amount held.
>
> &#x20;
>
> The [Villagers of XOLO](/jrny-club/the-planet-xolo-ecosystem/planet-xolo-villagers.md) and XOLO Keys supply are inversely related, meaning that when a key is exchanged (burned), the Key supply decreases, while at the same time, the Villagers of XOLO supply increases.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jrny.club/jrny-club/the-planet-xolo-ecosystem/xolo-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.