Pricing
Verified answers, kept correct.
The check is the easy part. What you pay for is the work of keeping it right as trusted lists, anchors and issuers change. A check counts toward your plan only when a wallet presented an attestation that verified. Every other check is free.
Starter
€49 per month
- Verification against the Commission's trusted lists, both production and acceptance
- Both transports the EU age verification profile defines, chosen per browser
- Trusted lists refreshed and anchors watched for you, so a lapsed issuer is our problem first
- Dashboard, API keys, signed webhooks and an export of every check
- Stats on the dashboard, the API and the MCP server: the summary and the trend over time
- Email support
- 5,000 verified checks a month, fair use
- €490 a year, two months free
Growth
€249 per month
- Everything in Starter
- Stats in full: the funnel, why attempts were refused and breakdowns by project, key or method
- Priority support
- 50,000 verified checks a month, fair use
- €2,490 a year, two months free
Platform
€990 per month, on an annual commitment
- Everything in Growth
- No volume to watch on any property you run
- A named contact
- Unmetered
Self host
from €4,990 per month, on an annual commitment
- The whole platform on your own hosts, so not even the yes or no leaves your boundary
- The same trusted list refresh and anchor monitoring, running where you run it
- Updates and support from the people who build it
- Unmetered
Every plan is the whole product: the dashboard, API keys, webhooks, both transports the EU age verification profile defines and a test mode that never counts toward your plan. The plans differ in volume, in the stats reads they include, in support and in where the verifier runs. Above the included volume nothing is charged per check. If you run past it, we talk about the right plan.
What counts as a check
A verified check is one where a wallet presented an attestation that verified: the signature checks out, the issuer is on the trusted list and the response answers the session that asked. Those count toward your plan, whether the answer is yes or no.
None of these count:
- The device has no wallet
- The wallet has no age attestation to present
- The person declines the request
- The session times out
- A presented attestation fails verification
- Every test mode check, always
One case cuts the other way: a wallet can present an attestation that verifies but does not carry the claim you asked for. That check counts, because the verification work happened.
Where it works today
Checks from the EU age verification app complete in production today. Denmark is the first country on the Commission's production trusted list, so live coverage starts there. The Commission works with seven frontrunner states and expects the solution available across the EU by the end of 2026, subject to member states being ready. Test mode works today against the pilot's test issuers, from any member state. The security page explains the trusted list mechanics behind that.
The EU Digital Identity Wallet is a separate path and it is still gated. That wallet checks who is asking before it releases anything, so it needs a relying party access certificate, which we applied for on 5 August 2026 and do not yet hold. Every relying party that wants to use that wallet has to register first and then identify itself to the wallet with such a certificate, incumbents included (Article 5b of Regulation (EU) 2024/1183 and Article 7 of Implementing Regulation (EU) 2025/848). The EUDI page covers that path.
Age verification API
Start with a sandbox key
Signup is open and a test project works as soon as you create one. Sending real traffic needs us to switch your organisation to live mode, so that part stays a conversation. A sandbox key is free and it stays free.