CAIRL Checkbox
Request an age claim through a supported CAIRL flow
A component surface for supported age checks. Configure the request, direct the person through the applicable flow, and receive the authorized result.
What it does
Age-gating requirements vary by jurisdiction, audience, and use case. The requesting service remains responsible for selecting an appropriate supported flow and policy.
CAIRL Checkbox is a component surface that can trigger supported age and identity capabilities. The applicable flow determines the evidence, authorization, information returned, and retention boundary.
In supported claims-sharing flows, a service can receive a verified claim without receiving the underlying ID document.
Key capabilities
Copy-paste integration
Drop a div and one script tag onto WordPress, Shopify, or plain HTML. Redirect or iframe mode — no npm, no React required.
Bounded claims sharing
Supported claims-sharing flows can return a signed result without sending the underlying ID document.
Flow-specific handling
Current technical documentation defines the evidence, account, biometric, retention, and response boundaries for each supported mode.
Deterministic sandbox
pk_sandbox_* keys return deterministic fixtures with zero human in the loop. Swap to pk_live_* when production opens — same integration contract.
Ready when you are
Move from explanation to implementation.
CAIRL is built to let users control identity and let platforms trust the result. Choose the next step that matches the surface you are building.
In supported claims-sharing flows, your service can receive a verified claim without receiving the underlying ID document.
Self-serve. No sales call. Sandbox is free.
What it costs
Typical age check, per verification. No subscription tiers — prepaid wallet, metered pricing.
~$0.10
per age check — a fraction of typical document-upload identity verification.
Per age check, typical claim bundle. Self-serve metered pricing — no per-seat minimums and no enterprise contract.
Copy-paste quickstart
The quickstart is the marketing: two lines of HTML, a server-side token exchange, and boolean claims on your callback. No sales call, no implementation review — sandbox keys work in public docs.