Documentation

Quickstart

Run an age check in under five minutes. First get an API key, then call the API.

1. Get a merchant API key

Buy a pack or plan on the pricing page, then claim your key on the claim page — it is shown once, and only its hash is stored. Or start the 100-check trial on the claim page, no card required. Store your key server-side — never expose live keys in public client code; use test-mode keys while integrating.

2. Add the widget to your checkout

Paste this where your checkout button lives. The widget gates clicks on any element with data-verifyage-gate.

<script src="https://api.verifyage.example/v1/widget.js"
        data-api-key="<redacted>"
        data-threshold="21"></script>
<button data-verifyage-gate>Checkout</button>

3. Call the API directly (optional)

Prefer server-side? Call the REST endpoint yourself.

curl -s https://api.verifyage.example/v1/verify \
  -H "X-API-Key: <redacted> \
  -H "Content-Type: application/json" \
  -d '{"method":"dob","dob":"1990-04-12","threshold":21}'

# {"id":"chk_...","result":"pass","threshold":21,"method":"dob","estimated_age":36}

4. Review your checks

Every check is logged. Pull your audit trail and remaining balance anytime.

curl -s https://api.verifyage.example/v1/checks \
  -H "X-API-Key: <redacted>"

Honest limits

The dob and self_declaration methods are check mechanisms, not legal proof of age in most regulated contexts.
Document and estimation checks run through a connected verification provider. Until a live provider account is connected, sessions run through a sandbox provider and every result is labeled a simulation — sandbox results are not real verifications.
The merchant remains responsible for legal compliance in their jurisdiction — thresholds, acceptable methods, and record-keeping vary by state and product category.