Skip to main content
This guide runs a batch of age verifications and sorts each person into pass, fail or manual review based on the evidence. For the request and response fields, see the Age Verification reference.

Try it in the dashboard

Open Age Verification in the API Playground, enter what you know about the person under Subject, and run it. The playground runs the same job as the API and shows the date of birth, age, evidence and sources.

Verify a batch and gate on confidence

Each verification runs high tier research and takes a few minutes, so start them all first and then poll. This script checks whether each person is at least 18 and sends anything uncertain to a human.

Reading the result

  • Gate on age.confidence or date_of_birth.confidence, not on whether a value is present. Both are 0–100.
  • A null date component means no source established it. A known birth year with an unknown day and month still pins the age to within a year.
  • age.value can be an estimate when no date of birth was found. Its confidence reflects that.
  • Keep evidence and sources with any decision you act on, so a reviewer can check them.

Getting better matches

  • Send every identifier you have in subject. A name alone rarely identifies one person; a company, location, email or LinkedIn URL usually does.
  • Reuse People Intelligence payloads as they are: lead_info is accepted in place of subject.
  • From an AI client, use the sixtyfour_verify_age_start and sixtyfour_verify_age_status tools in the MCP server.