> For the complete documentation index, see [llms.txt](https://docs.mudigital.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mudigital.net/protocol-overview/mubond.md). # muBOND muBOND is a credit-backed USD yield token supported by high quality Asia government and corporate borrowers. muBOND is designed for higher potential returns in exchange for providing insurance to AZND holders. muBOND is suitable for users seeking leveraged returns on the underlying Asset Pool while retaining full DeFi composability * **Risk:** First loss credit tranche * **Yield Allocation:** 10-20% of net yield from the Asset Pool; price adjusts periodically to reflect accrued yield * **Collateral:** Portfolio of Asia credit assets, including public bonds and private credit; same portfolio underlies AZND and muBOND * **Utility:** Freely transferrable onchain, usable in DeFi markets muBOND repricing happens on a regular basis, to reflect mark to market changes in the underlying portfolio as well as accrual of yield. These price updates are expected to be published weekly at inception with the frequency intended to increase over time --- # 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://docs.mudigital.net/protocol-overview/mubond.md?ask=&goal= ``` `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.