> For the complete documentation index, see [llms.txt](https://docs-en.a7a5.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.a7a5.tech/introduction-to-a7a5/key_features.md).

# Key Features

Key Features of the A7A5 token:

* **Asset Tokenization:** A7A5 represents a stablecoin, maintaining a 1:1 peg to the Russian Rouble.
* **Liquidity and Accessibility:** A7A5 will be available on top-tier centralized and decentralized exchanges, including a regulated centralized crypto exchange in Kyrgyzstan, ensuring high liquidity and accessibility for all types of users. It will be traded against the most liquid fiat and crypto assets, providing instant liquidity access to all A7A5 holders.
* **Income Distribution:** A7A5 automatically distributes 50% of its daily income among all token holders within 24 hours after interest is credited to our deposits, without requiring any action from the holders.
* **Regulatory Compliance:** The A7A5 framework integrates Know Your Customer (KYC) and Anti-Money Laundering (AML) procedures, ensuring adherence to regional regulations. The token’s compliance with Kyrgyz Republic's newly adopted crypto regulations further enhances its legitimacy.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-en.a7a5.tech/introduction-to-a7a5/key_features.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 `automate deployments from our CI pipeline` 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.
