> For the complete documentation index, see [llms.txt](https://docs.entangle.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.entangle.fi/universal-token-standard/developer-guides.md). # Developer Guides The Universal Token Standard (UTS) is a framework for deploying and managing omnichain tokens across multiple blockchains. It uses mint-and-burn or lock-and-unlock mechanisms to ensure consistent token supply during cross-chain transfers. Integrated with the Entangle Bridge, UTS supports EVM and non-EVM environments, enabling seamless token management and interoperability across diverse blockchains. ## Explore
Manual DeployQuick Launch Guide.pngManual Deploy
Bridge SDKArhitecture.pngBridge SDK
Token VerificationHow to Integrate.pngToken Verification
Fees Calculation & Gas Estimation LogicLiquid Vault Audit.pngFees Calculation & Gas Estimation Logic
EstimationsConnecting Custom Data.pngEstimations
--- # 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.entangle.fi/universal-token-standard/developer-guides.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.