> For the complete documentation index, see [llms.txt](https://faq.rollercoin.com/rollercoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.rollercoin.com/rollercoin/f.a.q./events/expeditions-and-hamsters/13.-what-is-an-expedition.md).
# 13. What is an Expedition?
In **Expeditions**, you can send your Hamsters on exciting journeys! Each Expedition has its own **Duration** (how long it takes), **Difficulty** (the chance of the Hamster dying), **Reward Value** (the value of the rewards you receive), and **Reward Amount** (how many rewards you get).
Choose your best Hamster and send them out to earn rewards! To receive a Hamster, make sure to get it through the **Season Pass**.
Hamsters gain experience during Expeditions. With each level-up, they earn a skill point that you can use to upgrade them as you wish! However, after each Expedition, Hamsters need to rest. If an Expedition fails, the rest time doubles.
Once the Expedition is complete, you’ll receive your rewards. The harder the Expedition, the better the rewards!
{% hint style="info" %}
For more details, check out [the next question](/rollercoin/f.a.q./events/expeditions-and-hamsters/14.-how-does-an-expedition-work.md)!
{% endhint %}
---
# 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://faq.rollercoin.com/rollercoin/f.a.q./events/expeditions-and-hamsters/13.-what-is-an-expedition.md?ask=&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.
