> 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/build-with-humanity.md).

# Build with Humanity

Choose between SDK/API integration (traditional web2) or on-chain smart contracts (web3) to add proof-of-humanity verification. Includes quickstart links for both paths.

{% hint style="info" %}
🔐 **Looking for SSO?** Our SDK quickstart provides "Sign in with Humanity" — same OAuth pattern as Google or GitHub login, working integration in \~10 minutes.\
\
:arrow\_forward: [SDK QuickStart](/build-with-humanity/build-with-the-sdk-api/sdk-quickstart.md)\
\
**Want to start testing against Sandbox?** You do not need real users to start building on Humanity.\
\
:arrow\_forward: [Generating Mock Credentials](/developer-guides-and-tutorials/generating-mock-credentials.md)
{% endhint %}

Humanity is an identity and verification layer you can add to web apps, mobile apps, and smart contracts.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><strong>SDK / API</strong> </h3></td><td><mark style="color:$primary;"><strong>For web, backend, and mobile applications</strong></mark></td><td>Human verification and much more via OAuth. React SDK, Connect SDK, and REST API.</td><td><a href="https://383350980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL1EBectYBMnvu9vU5N1M%2Fuploads%2FSXhHdNa7tDH1gk19LNft%2Foff-chain-cover.png?alt=media&amp;token=b4f7d0b5-0dc6-46fd-abb1-e7993d0d9e2b">off-chain-cover.png</a></td><td><a href="/build-with-humanity/build-with-the-sdk-api/sdk-quickstart.md">SDK QuickStart</a></td></tr><tr><td><h3>ON-CHAIN</h3></td><td><mark style="color:$primary;"><strong>For decentralized applications</strong></mark></td><td>Work directly in smart contracts using the Verification Oracle.</td><td><a href="https://383350980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL1EBectYBMnvu9vU5N1M%2Fuploads%2FEKqX6gyyj8nutNgZsS3P%2Fon-chain-cover.png?alt=media&amp;token=b2602790-b79b-426a-ad70-3006287aadb7">on-chain-cover.png</a></td><td><a href="/build-with-humanity/build-on-chain/on-chain-quick-start-guide.md">On-Chain Quick Start Guide</a></td></tr></tbody></table>

{% hint style="info" %}
👀 Not sure where to start? Explore the [Demo Hub](https://demo.humanity.org/) to see what you can build with Humanity.
{% endhint %}


---

# 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.humanity.org/build-with-humanity.md?ask=<question>&goal=<user_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.