> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/features/anchors.md). # Anchors Keeta's Anchor system allows users to securely move their digital assets across multiple payment networks, blockchains or traditional banks without extensive fees. Any network can be connected to Keeta through the Anchor system, allowing that network's native assets to be traded freely with any other asset on Keeta. This feature brings a new level of interoperability to ecosystems that are otherwise fragmented. Any foreign asset that is tokenized on Keeta is done so 1:1 and can be returned back to the native asset at any point. Upon sending the asset back to its native network, the original asset is released and the tokenized version on Keeta is burned. Traditional payment systems like the SWIFT and the Automated Clearing House (ACH) can also be connected to Keeta, creating a payment ecosystem with unprecedented global interoperability. Fiat currencies can be transferred with the same security and performance as digital assets, and the two can be interchanged seamlessly. Regulatory compliance protocols are built-in to the network natively, making the ecosystem feasible for central banks, commercial banks, and other highly-regulated financial entities. --- # 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.keeta.com/features/anchors.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 `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.