> For the complete documentation index, see [llms.txt](https://docs.bstable.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bstable.finance/introduction.md). # Introduction In crypto, change is constant. The price volatility of most cryptocurrencies has hindered the development of decentralized finance. Because of this, Stablecoins have become an essential ingredient of the crypto pie and have been one of the main foundations upon which DeFi has been built on so far. Hundreds of DeFi products across blockchains rely on stablecoins as safe-haven assets and hundreds of thousands of users are already using decentralized protocols to earn a higher interest on their stablecoins than is possible on their fiat. While stablecoins and DeFi have opened the doors to a new world of finance, there are many financial processes that remain undisrupted by stablecoins and cryptocurrency in general. Cryptocurrency payment solutions, for example, have yet to gather mass adoption. bStable’s strives to fill this gap with a **payment solution that is trust-less and non-custodial, and easy to use.** --- # 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.bstable.finance/introduction.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.