Adaptive Access
Age assurance inside CDK: k-ID decides when a user must prove their age, runs the check, and keeps the result on the user's session.
Adaptive Access is how CDK runs age assurance. Instead of asking every user for proof up front, k-ID decides when proof is needed: at the age gate, when a user reaches a protected feature, or not at all. When a user passes, the result is saved on their CDK session and later decisions reuse it.
Adaptive Access was previously called Automatic age assurance.
Two places to ask for proof
| Product-level age assurance | Feature-level age assurance | |
|---|---|---|
| When it runs | At the age gate, before the session exists | When the user reaches a protected feature |
| Who is asked | Every user whose claimed age is at or above the trigger age you set | Users old enough for a feature that needs a verified age in their market |
| API that returns the check | POST /age-gate/check | POST /session/upgrade |
| Challenge type | CHALLENGE_AGE_GATE_AGE_ASSURANCE | CHALLENGE_SESSION_UPGRADE_BY_AGE_ASSURANCE |
| After the user passes | k-ID creates the session | The feature's permission is enabled on the existing session |
| Compliance Studio setting | Product-level access | Feature-level access |
You can use either, both, or neither, and set them per market. Both are configured on the same screen in Compliance Studio. See Configure Adaptive Access.
Product-level: proof before entry
Use product-level age assurance when the whole product needs proof of age, for example an adults-only app. Users who claim an age at or above the trigger age verify themselves before k-ID creates their session. Users below the Digital Consent Age still go through parental consent as usual.
Product-level age assurance verifies every user at or above the trigger age at sign-up, including users who never reach a restricted feature.
Feature-level: proof at the feature
Use feature-level age assurance when only some features need a verified age, for example paid loot boxes or targeted ads in Brazil. Users sign up normally. A permission that needs a verified age carries a verifiedAgeThreshold and stays enabled: false until the user proves they meet it. Your app asks for the check only when the user reaches that feature.
The CDK knows which permissions need a verified age in each market, and at what age. With feature-level age assurance on, those rules apply to your product, and you can override them per feature and per market.
How a check works
- CDK decides. From your Compliance Studio settings, the user's market and claimed age, and any platform age signal you sent, k-ID decides whether the user passes, needs age assurance, needs parental consent, or isn't allowed.
- The user verifies. If age assurance is needed, the API returns a challenge with a
url. The user opens it and proves their age with one of the methods your product offers, such as facial age estimation, an ID document, or an AgeKey. - The result is saved. When the user passes, k-ID saves the result on the session as
ageVerificationand sets the permissions it unlocks. A failed check creates no session at the age gate and leaves the permission disabled at a feature. - The next decision reuses it. A later
POST /session/upgradefor a feature at the same or a lower age is granted without another check.
Your app never decides who must verify, and never interprets a verification result itself. It reads the session's permissions, which already reflect the outcome.
What CDK handles for you
- Market rules. Which features need a verified age, and at what age, comes from the CDK's rules for each market. You don't maintain a list of thresholds in your code.
- Platform age signals. A trustworthy platform signal at or above the age being checked, such as an
apple-iossignal withdeclarationType: governmentIDChecked, satisfies the check without a challenge. See Platform age signals. - Facial age estimation margins. An estimate too close to the age to call sends the user to another method instead of failing them. See How verification works.
Adaptive Access or AgeKit+ on its own
Ask one question: does the age result end the job, or does it shape the experience after?
| Adaptive Access in CDK | AgeKit+ on its own | |
|---|---|---|
| Use it when | Age decides access to the product or to features, now or later | You need a single age check and will build everything after it yourself |
| Who decides when to ask | k-ID, from your Compliance Studio settings and each market's rules | Your code |
| Where the result lives | On the user's CDK session, as ageVerification and permissions | In your system, after you read the verification result |
| Next market, feature, or parental consent need | Change settings in Compliance Studio; the integration stays the same | New code |
Choose Adaptive Access if your product has accounts, age-sensitive features, rules that differ by market, or parental consent coming. CDK keeps the check and the session at k-ID, so if you can't let k-ID hold a session for the user, use AgeKit+ on its own.