Guides7 min

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:

  1. Browser SDK → toCheckBody / collect
  2. Server HTTPS POST /api/v1/check with sk_…
  3. Map verdict → allow / step-up / deny in your callback

Where to put the check

StackTypical hook
ClerkYour server gate before granting protected access; webhooks for monitoring
Auth0Actions / Rules on login & signup
Better AuthDatabase hooks / API route before session
FirebaseBlocking functions / Admin SDK path
CustomYour signup and login handlers

Mobile is the same contract

iOS, Android, and React Native apps call your backend over HTTPS; it creates a session and makes the authoritative check with a server-held key. 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

← All posts · Integration guides · Compare options