> For the complete documentation index, see [llms.txt](https://docs.ridethebus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ridethebus.xyz/project-tokens/ticket-stub.md).

# Ticket Stub

### Details

* When you board a bus, you go through the process of:
  * Choosing a route 
  * Burning a *Bus Ticket*
  * Receiving a *Ticket Stub* with verification of your seat on the bus

{% hint style="danger" %}
Do not lose your *Stub*! It is proof that you were a passenger on a winning route.
{% endhint %}

### Choosing a route

* Each level has `level + 1 routes` 
* For example:
  * Level 1 has 2 routes
  * Level 2 has 3 routes
  * ..
  * Level 4 has 5 routes...

Only one route can survive each round!

#### ---After the Round---

### Claiming a stub

You survived your journey! Congrats. 

You now have two options:

1. Pick a route on the next level and keep riding.
2. Bail and snag some cash on your way off the bus.

### Last Chance Raffle

Your bus did not make it 😭

* You have one last hope: Try your luck in the *Last Chance Raffle*

###


---

# 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.ridethebus.xyz/project-tokens/ticket-stub.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.