> For the complete documentation index, see [llms.txt](https://docs.runesdex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runesdex.com/what-is-runes-dex.md). # What is Runes Dex #### Runes Dex is the first decentralized AMM on Bitcoin. Our platform allows users to swap Runes directly from their own Bitcoin wallets — no sign-ups, gatekeepers, or wrapped assets. Unlike traditional exchanges that use order books to match buyers and sellers, Runes Dex uses liquidity pools. This makes it simple to swap tokens in a few steps, directly from your wallet. Trades settle on the Bitcoin network, offering a transparent, verifiable, decentralized, and permissionless experience — all without sacrificing self-custody. #### :tools: Core Features * [Exchange](/products/exchange.md): * [**Swap**](/products/exchange/swap.md): Trade Runes tokens directly from your wallet. * [**Liquidity Pools**](/products/exchange/liquidity-pools.md): Provide liquidity and earn trading fees. * [Explore](/products/explore.md): * [**Token Pages**](/products/explore/tokens.md): View token stats, mints, market activity, and trading history. #### :globe\_with\_meridians: Built for Bitcoin Runes Dex is purpose-built for Bitcoin Assets — enabling a permissionless trading layer for native Bitcoin tokens, like Runes. It's designed to scale with the ecosystem as new tools and layers emerge. --- # 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.runesdex.com/what-is-runes-dex.md?ask=&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.