The account-protection market — and where AbuseGraph fits

Four shapes buyers already see

Teams shopping for signup and login protection usually meet one of four product shapes:

Device-ID tools — sticky visitor identifiers. Public entry often near ~$99/mo for ~20k calls. Great for “who is this browser?” — thin on “should we allow this signup?”
Account-abuse platforms — risk APIs aimed at registration and takeover. Public entry often near ~$200/mo for ~100k calls. Strong when you want decisions; pricing past the entry tier is often opaque.
Network / bot edge bundles — sold with CDN or bot management. Strong before traffic hits your app; less focused on explainable account verdicts once the request is inside your product.
Fraud suites — payment + account modules, sales-led, often $500+/mo or six figures/year. Right when chargebacks and checkout fraud are the job.

Those bands are anonymous public list prices as of 2026 — not endorsements. Exact quotes vary. The shape is what matters.

AbuseGraph is an account-protection API for signup and login:

You get	Why it matters
Score + verdict + reasons	Security and support can agree on what happened
Free forever (1,000 live checks) + unlimited test keys	Validate before you buy
Pro $99 / 20k (+ $4/1k) · Scale $199 / 100k (+ $2/1k)	Public market entry + published overages, with a decision — not only an ID
DNS domain proof	Live keys unlock after ownership verification
Exposure watch after signup	Alerts when a real user’s credentials show new exposure later
You keep enforcement	Looks good / Verify first / Watch closely / Block — in your app

Be honest with yourself:

Need chargeback guarantees or deep payment fraud → evaluate a fraud suite.
Need only a sticky device ID and nothing else → a pure fingerprint product may fit.
Already all-in on a CDN bot bundle → keep it for edge filtering; AbuseGraph sits next to your auth for account decisions.