Skip to main content
Age Verification researches public sources to establish a person’s date of birth, or an age estimate grounded in evidence when the exact date isn’t public, and returns the evidence and sources behind it. For when and how to use it in a trust-and-safety or KYC flow, see the Age Verification guide.

Endpoint

API Reference

See the full request/response schema and parameters in the API Reference.

Request

POST /verify-age takes one field. lead_info and input are accepted as aliases for subject, so a People Intelligence request body works unchanged. The research plan, fields and tier are fixed; struct, tier and webhook_url are not accepted. The response is the job handle:

Status

GET /verify-age/{task_id} returns {"task_id", "status"} until the job finishes, and the full result once status is completed.

Response

Each date component is null unless a source establishes it, and day and month are always null when year is. age.value can be set while the date components are null.

Usage

Pricing

Each POST /verify-age is charged at the high tier rate of People Intelligence. Polling is free. See Credits & Pricing Guide for more information. Age Verification runs high tier research but does not need high tier access: any org with credits can call it.

Errors

For error responses (400, 403, 404, etc.), see Handling Errors.