> For the complete documentation index, see [llms.txt](https://docs.dexkit.com/defi-products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexkit.com/defi-products/dexcontracts/overview.md). # Overview Easily deploy your own smart contracts on blockchain with a seamless experience. This tool enables the rapid deployment of secure, verified open source contracts without any harm or risk to be included as components in a DApp created using DexAppBuilder. With a simple to operate and very efficient interface (made with the best development practices) any user can deploy dozens of smart contracts: **from NFT and ERC20 token minting to modern gated-access systems based in blockchain**. We use audited [Thirdweb smart contracts](/defi-products/dexcontracts/thirdweb-contracts.md), ensuring all parties security, scalability and multi-way technical support. Take a look at the solution directly by [entering the link](https://dexappbuilder.dexkit.com/contract-wizard). You can keep reading this documentation to learn everything about this product. --- # 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.dexkit.com/defi-products/dexcontracts/overview.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.