> For the complete documentation index, see [llms.txt](https://docs.rujira.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rujira.network/resources/micar-compliant-white-paper.md).

# MiCAR Compliant White Paper

Ruji Holdings Limited has voluntarily submitted a MiCA-compliant whitepaper for Rujira token (RUJI), which is classified as an “Other Crypto-Asset” under Regulation (EU) 2023/1114 on Markets in Crypto-Assets (MiCA). Unlike Asset-Referenced Tokens (ARTs), Electronic Money Tokens (EMTs), or Utility Tokens, RUJI is not subject to a mandatory whitepaper requirement. However, pursuant to Article 6(1), second subparagraph of MiCA, service providers may voluntarily publish a whitepaper to promote transparency, regulatory clarity, and investor confidence. This document provides key disclosures regarding Rujira’s characteristics, associated risks, and the exemptions though decentralization to the regulatory framework under which RUJI can be offered within the EU/EEA.

The white paper is available here: [Rujira MiCAR Compliant White Paper\_v1.1.pdf](https://drive.google.com/file/d/1pVN7wRJeN_RLq9kjg9R6zeyLf4fQ49vk/view?usp=sharing)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rujira.network/resources/micar-compliant-white-paper.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.
