> ## Documentation Index
> Fetch the complete documentation index at: https://humanity-eaeda8f6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Humanity Public Dev API

> End-to-end guide for integrating with Humanity’s verification platform.

The Humanity Public Dev API gives developers typed OAuth tooling, preset verification, and status feeds that mirror the production platform. Everything in this space is generated from the same NestJS monorepo, so the contracts you see here are the ones that ship.

## What you can build

* **Frictionless onboarding** – gate app features behind Humanity presets such as `is_21_plus`, `is_human`, or industry-specific attestations.
* **Risk + compliance tooling** – subscribe to authorization and credential change feeds to keep downstream systems in sync.
* **Lifecycle automation** – drive OAuth 2.1 + PKCE flows, revoke tokens on entitlement changes, and poll for consent results without writing boilerplate.

<Columns cols={3}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Provision credentials, run the OAuth handshake, and verify your first preset in \~10 minutes.
  </Card>

  <Card title="@humanity-org/connect-sdk" icon="cube" href="/sdk/overview">
    Typed helper that wraps the generated REST client plus higher-level consent flows.
  </Card>

  <Card title="API reference" icon="terminal" href="/api-reference/introduction">
    Backed by the OpenAPI in this repo with Mintlify’s playground for every endpoint.
  </Card>
</Columns>

## Platform pillars

1. **Security first** – OAuth 2.1, PKCE, encrypted at rest, and auditable decision trails.
2. **Deterministic contracts** – DTOs live in `src/contracts`, SDK + docs regenerate from the same source.
3. **CQRS at the edge** – read/write isolation keeps authorization, consent, and access domains predictable under load.

## Surface map

| Domain             | Highlights                                                             | Primary endpoints                                   |
| ------------------ | ---------------------------------------------------------------------- | --------------------------------------------------- |
| OAuth              | Standard + advanced consent, approval callbacks, revocation            | `/oauth/authorize`, `/oauth/token`, `/oauth/revoke` |
| Presets            | Single + batch verification, evidence payloads, humanity user preset   | `/presets/{preset_name}`, `/presets/batch`          |
| Status feeds       | Incremental credential + authorization changes with pagination cursors | `/credentials`, `/authorizations`                   |
| Discovery & health | Well-known metadata, JWKS rotation, readiness                          | `/.well-known/*`, `/health`, `/ready`               |

<Callout>
  Every endpoint documented here is also available via the SDK’s typed client. Pick whichever interface fits your deployment strategy.
</Callout>

## Next steps

* Follow the [Quickstart](/quickstart) to stand up a local or sandbox integration.
* Review [Environments & tooling](/development) for base URLs, feature flags, and readiness probes.
* Dive into the [API reference](/api-reference/introduction) for detailed schemas, examples, and autogenerated snippets.