> For the complete documentation index, see [llms.txt](https://docs.openbisea.com/dexgo-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbisea.com/dexgo-white-paper/dexgo-overview/game-objects/routes-to-pass.md).
# Routes to pass
Routes are released one at a time by the influencer, with a maximum release of 20 routes for one leader. The influencer collects the route in the form:
* general title and description of the route (+ voice recording optional)
* recorded walking routes as Google Maps links between all points
* title and description of each point (+ voice recording optional)
* 360 degree photo at each point with marks where to sculpt text with interesting facts and the text itself
* quizzes on interesting facts with correct answers
* mini-game in augmented reality from the list (if there is no quiz and interesting facts)
* % reward distribution for each leg of the journey and for each stop (total 100%).
The starting price for creating a route is $50. However, each new creation increases its price by 10% for that influencer. After the route is implemented into the system by the project team, the influencer must buy shoes and go through the route himself. From that moment on, the route is activated and available in the system for any player who has bought shoes.
In order for opinion leaders to more actively attract players to competitions on their routes and thereby develop the game economy, dexGO provides maximum idle period. If no one passes the route within 90 days, it is deactivated and can no longer be used in the system.
### What do you need to know about routes?
* The date the route was created affects the maximum downtime period and revenue distribution. The earlier the routes are created, the more the influencer gets and the longer the maximum downtime period.
---
# 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.openbisea.com/dexgo-white-paper/dexgo-overview/game-objects/routes-to-pass.md?ask=&goal=
```
`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.