Integrate account protection with Clerk, Auth0, Better Auth, and Firebase
One pattern for every auth stack: collect in the browser, check with a secret key in your hook, enforce the verdict before createSession / createUser.
By AbuseGraph Team
Stop rewriting detection per vendor
Whether you use Clerk, Auth0, Better Auth, Firebase, or a custom session store, the AbuseGraph integration is the same:
- Browser SDK →
toCheckBody/ collect - Server
createCheckClientwithsk_… - Map verdict → allow / step-up / deny in your callback
Where to put the check
| Stack | Typical hook |
|---|---|
| Clerk | beforeSignUp / server actions around signup |
| Auth0 | Actions / Rules on login & signup |
| Better Auth | Database hooks / API route before session |
| Firebase | Blocking functions / Admin SDK path |
| Custom | Your signup and login handlers |
Mobile is the same contract
iOS, Android, and React Native packages speak the same check API. See the iOS, Android, and React Native guides.
Prove the domain, then go live
Live keys unlock after DNS proof. Test keys never bill — use them in CI and local auth.
Browse all stacks on the integrations page.
Further reading
Next
Put a live check on signup
Free forever — 1,000 live API checks / month. Unlimited test keys. No credit card.
Related reading
- Guides
Email risk API for signup and invite flows
When you only have an email — scoring disposable domains, role accounts, and risky patterns before you send the invite.
- Guides
Credential stuffing defense for login APIs
How velocity, bot-like clients, and breach-aware signals help stop stuffing without locking out real users.
- Guides
Password reset fraud — the quiet account takeover path
Why password-reset and email-change events need the same risk API as signup — and how to wire them without rewriting your auth stack.