Provero

Age Verification API

Verify age without asking for ID.

Confirm whether a mobile subscriber meets an age threshold using mobile-network data — without putting every customer through a document upload.

  • 18+, 21+, 25+ or your chosen threshold
  • UK mobile networks
  • Real-time API
Try it free Pricing and additional coverage on request

Confirm an age threshold in one API call

Send Provero a mobile number and the minimum age you need to verify.

The mobile network data is checked and Provero tells you whether the available subscriber information confirms that threshold.

You don't receive the person's date of birth or exact age. You get the answer your workflow actually needs: "Does the available data confirm this subscriber meets the required age?"

  • Choose the threshold

    18+, 21+, 25+, 50+ or another minimum age.

  • No document upload

    Use mobile-network data before asking the customer to photograph or upload identity documents.

  • One clear primary result

    meets_age_requirement tells your workflow whether the requested threshold was confirmed.

More than a simple age response

One primary age result, with supporting signals alongside it.

  • Age requirement

    Whether the available subscriber information confirms the minimum age you requested.

  • Identity-verified supporting signal

    Where available, see whether the information used for the age check was verified against official identification.

  • Adult-content restriction

    See whether the network reports an adult-content restriction as active.

  • Parental controls

    See whether parental controls are reported as active.

  • Mobile network

    Return the mobile network code associated with the result where available.

The supporting signals provide additional context but do not replace or override the primary age result. Where a supporting signal is returned empty, that means the information was not available rather than that the answer is no.

Understand the result

Age Verification returns one primary result, and an answer that isn't available is kept distinct from a negative one.

Threshold confirmed

meets_age_requirement: true

The available subscriber information confirms the minimum age you requested.

Threshold not confirmed

meets_age_requirement: false

The available information did not confirm the requested threshold. This does not reveal the subscriber's exact age and must not be described as proof that they are below the requested threshold.

Age verification unavailable

If the subscriber cannot be found, the network is unsupported, the subscriber has opted out or age verification isn't available for that number, Provero returns a distinct error — subscriber_not_found, network_not_supported, subscriber_opted_out or age_verification_not_available — rather than treating that as a negative age result.

UK mobile-network coverage

EE, O2, Vodafone & Three
Available across the UK's four main mobile networks
Age Verification currently supports Pay Monthly subscribers on all four UK networks.
Pay Monthly
Where coverage is strongest
Coverage is currently strongest for Pay Monthly subscribers, who are the subscriber type supported on all four networks today.
Other markets
On request
Additional market and network coverage can be discussed before you build against the check.
Ask us about additional market and network coverage →

Keep low-friction users out of document flows

  • Age-restricted registration

    Check an age threshold as part of sign-up before escalating to document verification.

  • Age-restricted purchases

    Add a real-time age signal at checkout where age matters.

  • Progressive age assurance

    Start with a low-friction network check and use another permitted age-assurance route where the network cannot return the result you need.

  • Reduce unnecessary document collection

    Avoid collecting identity documents from users where a network-based age result is sufficient for your process.

  • Combine age and identity signals

    Run Age Verification alongside Mobile Network Identity Verification, HLR, SIM Swap and other Provero checks.

See how Provero fits into KYC, IDV & fraud workflows →

Age verification at the point you need it

Run Age Verification in real time at sign-up or checkout, or process existing records in bulk.

During sign-up

Check the threshold while somebody is registering, before deciding whether to escalate them to a document flow.

At checkout

Add a real-time age signal at the point of an age-restricted purchase.

In any age-restricted workflow

Call the check wherever a threshold has to be confirmed, rather than only at the start of the journey.

Across existing records in bulk

Process a file of existing records in bulk rather than one number at a time, so the same age result is available for records you already hold.

Alongside other Provero checks

Return the age result next to Mobile Network Identity Verification, SIM Swap Detection, HLR and other Provero signals.

Age Verification API example

POST /api/validate/age

Request 

{
  "mobile_number": "+447700900123",
  "minimum_age": 18
}

Example response 

{
  "status": "success",
  "verification_id": "age_example",
  "mobile_number": "+447700900123",
  "minimum_age": 18,
  "meets_age_requirement": true,
  "identity_verified": true,
  "adult_content_restriction_active": false,
  "parental_controls_active": false,
  "mobile_network_code": "23410"
}

Illustrative example. +447700900123 is a reserved number kept aside for documentation, so the result shown is not a real verification. meets_age_requirement is the primary result; identity_verified, the adult-content restriction and parental controls are supporting signals alongside it.

Read the full Age Verification API documentation →

Age Verification pricing

Pricing depends on volume and network coverage.

Age Verification is quoted per account so the rate reflects the networks and volumes you actually need. Everything else runs on the same prepaid Provero balance.

See published pricing.

Talk to us about pricing and coverage: pricing@provero.io

Related checks

Age is one question about a record. These are the checks people usually run alongside it.

See every Provero check →

Age Verification FAQ

How does mobile network age verification work?

You send Provero a mobile number and the minimum age you need to verify. The mobile network data associated with that subscriber is checked, and Provero returns whether the available information confirms the threshold you asked for. Nothing has to be photographed or uploaded by the customer.

What age thresholds can I check?

You choose the minimum age on each request. Common thresholds are 18, 21, 25 and 50, and any whole number from 0 to 120 is accepted, so the threshold can match whatever your process requires. The response repeats the minimum age you sent alongside the result.

Does Age Verification return someone's exact age or date of birth?

No. It returns whether the available subscriber information confirms the minimum age you requested. You do not receive a date of birth or an exact age.

What does meets_age_requirement: false mean?

It means the available information did not confirm the requested threshold. It does not reveal the subscriber's exact age and must not be described as proof that they are below that age.

What happens when an age result isn't available?

Provero returns a distinct error rather than a negative age result: subscriber_not_found where the number isn't recognised, network_not_supported where the network cannot answer an age check, subscriber_opted_out where the subscriber has disabled verification, and age_verification_not_available where the service cannot return a result for that number. Route those users to another age-assurance step rather than treating them as having failed the threshold.

What supporting signals does the API return?

Where available: identity_verified, showing whether the information used for the age check was verified against official identification; adult_content_restriction_active and parental_controls_active, showing what the network reports for that subscriber; and mobile_network_code. Each can come back empty, which means the information was not available rather than that the answer is no. They provide additional context but do not replace or override meets_age_requirement.

Is this the same as identity verification?

No. Age Verification answers an age-threshold question, not who the person is. The identity_verified signal is supporting context about the information behind the age check, not an identity or KYC result. Where you need identity corroboration, Mobile Network Identity Verification is a separate check.

Does Age Verification work without an ID upload?

Yes. The check runs on mobile-network data, so customers do not have to photograph or upload an identity document for the age check itself. Document verification can be kept for the cases where the network cannot return the result you need.

Can I run Age Verification in bulk?

Yes. Age Verification runs both as a real-time API call at sign-up or checkout and as a bulk process over existing records, so you can check a threshold at the moment of the decision or work through records you already hold. The same result and supporting signals are returned either way.

Which UK mobile networks are supported?

EE, O2, Vodafone and Three. Coverage is currently strongest for Pay Monthly subscribers. Email pricing@provero.io about additional market and network coverage.

Does it work with PAYG numbers?

Not at the moment. Age Verification currently supports Pay Monthly subscribers on EE, O2, Vodafone and Three. Where a number isn't covered, Provero returns a distinct error rather than a negative age result, so a PAYG number should be routed to another age-assurance step rather than treated as having failed the threshold.

Can I combine Age Verification with MNO KYC, SIM Swap or HLR?

Yes. Age Verification runs on its own or alongside other Provero checks, including Mobile Network Identity Verification, SIM Swap Detection and HLR Phone Verification, so an age answer arrives next to your identity, risk and contactability signals.

Does mobile network age verification satisfy age-assurance regulation?

Whether a particular method is sufficient depends on your jurisdiction and the requirements that apply to your service. Mobile network age verification is best used as a low-friction stage within an age-assurance process, with another permitted route available where the network cannot confirm the threshold. Confirm what your own obligation requires before relying on it.

Run an Age Verification check

Create a Provero account and run Age Verification in real time through the API or as a bulk upload.

Try it free