> 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/the-problem-we-solve.md).
# The Problem We Solve
Traditional identity systems lack privacy, uniqueness verification, and user sovereignty. Learn how Humanity solves bot prevention, KYC, and age verification challenges.
We envision a world where **biometric data** is used for verification in a **non-intrusive and privacy-preserving way**.
Existing systems often rely on centralized authorities for identity validation, which introduces risks of data breaches, censorship, and inefficiencies. Humanity addresses these issues by enabling users to autonomously verify credentials via decentralized means. This trust-less model enhances security and accessibility while reducing dependency on third-party entities.
By decentralizing all operations, Humanity ensures:
* **Immutability**: Once credentials are recorded on the blockchain, they cannot be altered or deleted without consensus.
* **Transparency**: All transactions are visible to users and auditors, fostering trust among participants.
* **Autonomy**: Users maintain full control over their identities and earnings without relying on external entities.
Even in the context of Blockchain adoption, its anonymous nature has contributed to the concerning issue of [**Sybils**](https://en.wikipedia.org/wiki/Sybil_attack), which refers to a single entity controlling multiple identities. This problem is further compounded by the rise of AI, which is making it even more difficult to determine who is behind each identity. This undermines the integrity of decentralized networks and leads to concerns about the mentioned Sybil attacks as well as fair airdrops, governance voting, and more.
---
# 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.humanity.org/understanding-humanity/the-problem-we-solve.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.
