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

# Introduction

Many emerging markets go through fast growth, industrialization, and periodic structural reforms. As part of that dynamic, their central banks often maintain higher policy rates than developed markets.

While these higher rates create attractive nominal yields, accessing them is difficult. Regulatory restrictions, limited custody options, fragmented financial infrastructure, and local-market access barriers make these opportunities inaccessible to most global investors.

Brix brings these emerging-market yields onchain. Though partnerships with regulated issuers and established financial institutions, Brix integrates tokenized, high-yield, low-risk, and highly liquid emerging-market instruments with DeFi.

By bridging between traditional high-yield markets and permissionless financial infrastructure, Brix enables strategies such as savings, hedging, leverage, and carry trades.

## Initial Launch

The first tokenized instruments integrated into Brix are iTRY and wiTRY.

iTRY is a Turkish Lira pegged stablecoin backed by a tokenized basket of highly liquid Turkish money-market funds, and wiTRY is its yield-bearing counterpart obtained through staking.


---

# 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:

```
GET https://docs.brix.money/overview/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.