> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/readme.md). # Welcome {% embed url="" %} ### About COTI COTI is a groundbreaking blockchain network designed to enable computation on encrypted data through the use of Garbled Circuits. By combining advanced cryptographic techniques with blockchain technology, COTI opens new possibilities for secure and private data processing. ### What You'll Find Here Our developer documentation serves as a comprehensive guide to understanding and working with the COTI network. Here's what you can expect: * [**Technology Overview**](/coti-documentation/how-coti-works.md): Dive into the technical foundations of the COTI network, including the cryptographic principles and innovative solutions behind its operation. * [**Quickstart Guide**](/coti-documentation/build-on-coti/quickstart.md): Get up and running with the COTI network quickly, using step-by-step instructions and practical examples. * [Privacy on Demand](/coti-documentation/privacy-on-demand.md) — Private computation on COTI with EVM orchestration (PoD) --- # 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.coti.io/coti-documentation/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 `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.