Guides
AbuseGraph + Next.js App Router
Server Action with createCheckClient — browser SDK toCheckBody before creating the user.
Quick path
- Install
@abusegraph/sdkand@abusegraph/server; paste keys from the console. - On the signup form, run
collect→evaluate→toCheckBody. - Pass the body into a Server Action that calls
createCheckClient.checkbefore user creation.
Keys
| Key | Env | Use |
|---|---|---|
| Secret | ABUSEGRAPH_SECRET_KEY (sk_test_… / sk_live_…) | Server /api/v1/check |
| Publishable | NEXT_PUBLIC_ABUSEGRAPH_PUBLISHABLE_KEY (pk_test_…) | Browser SDK |
| Site | ABUSEGRAPH_SITE | DNS-verified domain |
Free includes 1,000 live API checks / month after DNS verify. Test keys never bill.
Env
ABUSEGRAPH_SITE=yourdomain.com
ABUSEGRAPH_CHECK_URL=https://abusegraph.com/api/v1/check
ABUSEGRAPH_SECRET_KEY=sk_test_…
ABUSEGRAPH_SECRET_KEY_TEST=sk_test_…
NEXT_PUBLIC_ABUSEGRAPH_PUBLISHABLE_KEY=pk_test_…Use sk_live_… / pk_live_… in production after DNS verify.
Server check
Use @abusegraph/server createCheckClient. Events: signup | login | password_reset | email_change. Optional sessionId.
import { createCheckClient } from "@abusegraph/server"
const abusegraph = createCheckClient({
secretKey:
process.env.NODE_ENV === "production"
? process.env.ABUSEGRAPH_SECRET_KEY! // sk_live_…
: process.env.ABUSEGRAPH_SECRET_KEY_TEST ??
process.env.ABUSEGRAPH_SECRET_KEY!, // sk_test_…
site: process.env.ABUSEGRAPH_SITE!,
})Browser signals (recommended)
init + collect + evaluate + toCheckBody — NEVER bare sdk.check() alone as the authoritative decision.
"use client"
import { init } from "@abusegraph/sdk"
const sdk = init({
publicKey: process.env.NEXT_PUBLIC_ABUSEGRAPH_PUBLISHABLE_KEY!, // pk_test_…
})
export async function collectForSignup(email: string) {
const collected = await sdk.collect()
const edge = await sdk.evaluate(collected, { email })
return sdk.toCheckBody(collected, {
email,
event: "signup",
verdictToken: edge.verdictToken.token,
})
}Next.js Server Action
"use server"
import { createCheckClient } from "@abusegraph/server"
const abusegraph = createCheckClient({
secretKey: process.env.ABUSEGRAPH_SECRET_KEY!,
site: process.env.ABUSEGRAPH_SITE!,
})
export async function signup(input: {
email: string
password: string
browserFields: Record<string, unknown>
}) {
const result = await abusegraph.check({
email: input.email,
event: "signup",
...input.browserFields,
})
if (result.verdict === "block") {
return { ok: false, error: "Unable to create account" }
}
// create user in your DB / auth provider
return { ok: true, summary: result.summary }
}Form submit:
const browserFields = await collectForSignup(email)
await signup({ email, password, browserFields })Lifecycle events
- login — separate Server Action with
event: "login"before issuing a session. - password_reset — call check in reset handler with
event: "password_reset". - email_change — call after email update with
event: "email_change".
Platform
Lists, rules, and linked accounts apply on every check — configure in the console. Optional session: POST /api/v1/session. Native apps: iOS, Android, React Native.
Verify
Submit signup once with sk_test_…, then open Activity. Blocked signups should return an error before user creation.