Originally Posted by agemin_john

Hi cerulean,

Great questions. Let me go point by point:

SDK availability
Our SDK is Javascript-based since it’s designed for the frontend. It works both as vanilla JS for older sites and as a Node package for modern frameworks. For backend use cases (like PHP), most operators just call our API to retrieve the verification result. That said, for age verification specifically, a backend integration is usually unnecessary — frontend SDK + API callback is enough.

Compliance with U.S. laws
Biometric methods (e.g., facial recognition for age estimation) are considered “commercially reasonable” under U.S. state laws. States such as Texas (HB 1181) and Louisiana (PAVE Act) explicitly recognize biometric and ID-based verification as valid methods if they align with standards like NIST IAL2, which our solution does. So yes, our system satisfies current U.S. state-level age verification requirements.

Insurance & liability
By law, the content publisher (site operator) carries primary liability if a minor gains access. Using a third-party vendor provides a defense if you can demonstrate you applied “reasonable efforts” through a recognized verification method. Enforcement varies: fines can range from $1,000 to $250,000 per violation in state-level cases, with injunctions or lawsuits also possible. Vendors (like us) don’t automatically provide a safe harbor, though contracts can shift some risk through indemnification.

We do maintain our own insurance, but not one that automatically extends to cover clients — mainly because we can’t control implementation on your side. Our recommendation is that you obtain coverage for age-verification liability; many insurers now ask specifically whether you’re using a tested solution, which can strengthen your position.

I hope this cleared some of it. And if you have other questions or need any integration help, we are here to help.


John
Team Agemin.com