> For the complete documentation index, see [llms.txt](https://docs.humanity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humanity.org/understanding-humanity.md). # Understanding Humanity Welcome to the Humanity Developer Documentation. This resource provides comprehensive technical guidance for integrating Humanity into on-chain and off-chain systems, with a strong emphasis on privacy and decentralization. \ The documentation covers the protocol’s architecture, setup instructions for both testnet and mainnet, integration workflows, and a full API reference. Humanity enables secure, privacy-preserving Proof-of-Humanity verification using biometric data, ensuring that user identities can be authenticated without compromising personal information. Use this guide to build applications that incorporate human uniqueness and trust, while maintaining user privacy and data sovereignty by design. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.humanity.org/understanding-humanity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.