Developer docs

Build with Human Gateway.

Human Gateway helps partners add privacy-first human verification, private verified-human auth, signed callbacks, and partner-scoped user flows using hosted pages and SDK tooling.

Quickstart

Install the SDK, configure your project, launch Verify/Auth, and connect your backend callback.

SDK

Use the Human Gateway SDK from your frontend and server to run hosted flows and verify callback signatures.

Verify

Add proof-of-human checks for signup, voting, claims, gating, and other anti-sybil product actions.

Auth

Add private verified-human login flows with partner-scoped users and Human Gateway auth sessions.

Callbacks

Verify signed backend events, use raw request bodies, validate timestamps, and process events idempotently.

What Human Gateway provides

Human Gateway provides hosted Verify flows, hosted Auth flows, partner-scoped results, signed backend callbacks, a Partner Console, and an SDK for selected early partners.

The goal is to help apps verify human users without handling identity documents, biometric data, raw World ID nullifiers, or raw World ID proof internals.

Current status

Human Gateway is in early partner access. SDK behavior, dashboard features, API details, limits, and docs may evolve as the platform matures.

For production integrations, use explicit project and action settings, configure allowed origins carefully, verify signed callbacks in your backend, and review the Privacy Policy, Terms of Service, Security page, and Cookies Policy.

Core integration model

Create or receive a Human Gateway project.
Create Verify or Auth actions inside that project.
Configure allowed origins for the frontend SDK.
Configure a full backend callback URL for signed events.
Run hosted flows from your app.
Use signed callbacks as your backend source of truth.

Important legal and security notes

Human Gateway is not a KYC provider, civil identity provider, government identity verification system, sanctions screening service, or replacement for legal compliance checks required by regulated products.

Partners are responsible for their own application security, privacy notices, consent flows, callback endpoints, secrets, access decisions, and legal compliance.