Build with isHuman credentials
Integrate Stripe-verified proof-of-humanity into your app with site-private PPIDs, local verification, and revocation-aware controls. Start with docs and SDK references, then wire API keys for your runtime.
1) Onboard
Implement wallet bridge + verifier to request and validate site-bound credentials in browser.
- Set `siteId` to your canonical hostname or registered site identity.
- Use `verify()` before sensitive actions.
- Fail closed on missing, expired, or revoked proofs.
2) Operate
Use the isHuman API surfaces for verification lifecycle, site blocks, and network revocation requests.
- Start verification with `/api/ishuman/start-verification`.
- Check status with `/api/ishuman/verification-status/<session_id>`.
- Apply site-local abuse blocks with API keys.
3) Manage Access
Use authenticated key management for your runtime and site operations dashboards.
- Runtime/customer keys are managed in the key manager.
- Admin and wallet session are required for privileged actions.
- Keep key scopes minimal and rotate regularly.
Legacy internal consoles are restricted to admin-only routes and are not served on public developer paths.