> For the complete documentation index, see [llms.txt](https://realitymeta.gitbook.io/rm-core-badges/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://realitymeta.gitbook.io/rm-core-badges/introduction.md).

# Introduction

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

The new Reality Metaverse Badge System has been designed to encourage engagement while offering maximum special perks to our loyal users.

### **The Badge Tiers (Ranks)**

Our new system contains six badge tiers:

1. Common
2. Uncommon
3. Rare
4. Epic
5. Legendary
6. Artifact

Each of these badges has distinct requirements and accompanying benefits. You can purchase the badges with the loyalty points you collect:

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

{% hint style="info" %}
The system constantly develops for improvement and innovation, which means changes may be implemented to enhance the user experience.
{% endhint %}

{% hint style="info" %}
Only credential requirements fulfilled after this date and time are eligible for the loyalty points: 01.11.23 - 00:00 UTC
{% 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 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://realitymeta.gitbook.io/rm-core-badges/introduction.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.