docs

Documentation

Divelai is in closed beta, and the full reference is open to teams in the beta rather than published on the open web. This page is the honest table of contents: what the documentation covers, and what a first integration actually looks like.

Request access

Quickstart

Three steps: get a key, point your client at the proxy, name a policy. The standard policy catches the common identifier classes, so the first request is already sanitized before you have written any configuration.

Verify it worked by reading the transformation log for your request ID — if nothing was detected, that is a finding rather than a success.

Beta participants get this, the full API reference, and a private channel with the engineers who wrote it.

# 1. Sanitize a payload directly, no proxy needed.
curl https://api.divelai.com/v1/sanitize \
  -H "Authorization: Bearer \$DIVELAI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "policy": "default",
    "text": "Email maria.alvarez@x.example re: 4242…"
  }'

# => { "text": "Email [EMAIL_7f2a] re: [REDACTED]",
#      "spans": 2, "request_id": "req_8c1f…" }

Reference sections

Quickstart

First sanitized request, verifying it worked, and reading the log.

API reference

Sanitize, rehydrate, policy, vault, and audit endpoints with error semantics.

SDKs

Client libraries and their release cadence [CONFIRM languages]

Policy language

Detectors, transforms, scoping, per-destination rules, and failure modes.

Deployment guides

Proxy, sidecar, Kubernetes, and self-hosted installs with vault setup.

Changelog

Versioned, including detector changes that alter what gets caught.

Docs are searchable and versioned, and every detector change appears in the changelog — a silent improvement to detection is still a change to what left your building yesterday versus today.

Prefer to see it on your own traffic?

Request access