Skip to main content
Crivacy Docs

Crivacy developer docs

FHE-powered KYC credentials, wired into your app in minutes.

Add a Verify with Crivacy button to your site. Users verify their identity once on our consent flow; every participating firm receives a signed, tamper-evident credential, no PII leaves Crivacy's boundary.

Get startedRead the API reference
TERMINAL
$ curl -X POST https://app.crivacy.io/api/v1/oauth/token \
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "grant_type=authorization_code&code=..."

{
  "access_token": "tok_…",
  "id_token": "eyJhbGciOiJIUzI1Ni…",
  "token_type": "Bearer",
  "expires_in": 3600
}

  • FHE-powered

    Every credential is anchored on Sepolia for tamper evidence.

  • Verify once, reuse everywhere

    The user runs KYC with Crivacy a single time and every partner firm can reuse it.

  • Standard OAuth 2.0 + OIDC

    Authorization-code + PKCE. Works with any openid-client, authlib, or NextAuth setup.

  • Privacy-preserving claims

    Firms receive verification flags + a proof hash, never the user's raw PII.

  • Real-time webhooks

    11 signed event types so your back-office updates the moment a credential changes.

Start here

Four entry points, each curated for a different stage of integration.

Overview

1 page

Introduction and quick start

Guides

5 pages

In-depth integration guides

API Reference

1 page

Complete endpoint documentation

Resources

3 pages

Error codes, rate limits, changelog

Popular guides

The pages most integrators open first.

Documentation -- Crivacy Docs