> For the complete documentation index, see [llms.txt](https://doc.metarun.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.metarun.game/metarun.md).

# Metarun

Metarun is a Feature-packed runner game leveraging single and multiplayer modes. It offers actual ownership of assets by incorporating NFTs and a marketplace built to support its ecosystem, fueled by its native currency.

A prodigious blend of traits from conventional games such as graphics and gameplay mechanics mixed with non-custodial smart-contracts-powered features such as NFT, DeFi, and Blockchain. Players can earn in-game currencies utilized for several cardinal upgrades such as characters, abilities, pets, and visual styles.

The environment is detailed and full of interactive items. Each game level is carefully crafted to offer unique visual styles that are pleasing to the eye. In addition, levels have diversified obstacles that the characters must jump over, slide under or dodge to survive.

![](/files/Ei0O7v8LHT1GFCIJOEdg)


---

# 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://doc.metarun.game/metarun.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.