> For the complete documentation index, see [llms.txt](https://docs.znsconnect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.znsconnect.io/readme.md). # Welcome ZNS Connect is pioneering the future of Web3 identity — transforming complex wallet addresses into personalized, multi-chain domain names. Our decentralized identity layer powers seamless social interactions, cross-chain integrations, affiliate growth, and next-gen digital profiles. *** ## 🌐 Quick Links * 🔗 **Website**: * ✨ **Mint your domain**: * 📖 **Full Docs & Tools**: [https://docs.znsconnect.io](https://docs.znsconnect.io/) *** ## 🏛️ Ownership & Legal Info ZNS Connect is a product developed and managed by **AltBridge Labs S.A.**, a registered legal entity headquartered in Panama.\ All technologies, dashboards, and smart contracts under ZNS Connect are the exclusive intellectual property of AltBridge Labs S.A. *** ## 🚀 What You’ll Find in This Docs Portal * 🔧 How to integrate ZNS domains into your dApp or project * 🪝 Affiliate system and API reference * 🌉 Smart contract links, cross-chain architecture, and partner methods * 🛠️ Troubleshooting, tips, and direct contact channels *** Need help? Join our global community: * Telegram → * Twitter → --- # 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.znsconnect.io/readme.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.