The Risk Platform is available under contract. There is no free plan: Abstract turns it on for your account. Contact sales to get access.
allow, review or block) and the reasons behind it. Your application decides what to do.
What a check looks at
Each check combines several signals into one answer, so you don’t have to call and reconcile separate APIs:
You send whichever identifiers you have. A check needs at least one: an email, a phone number, an IP address or a device token.
How a check works
1
The browser collects a device token
The browser SDK runs on your signup and login pages and attaches a short-lived device token to the form submission. It never delays the submission.
2
Your backend sends a check
Your server calls the Risk API with the flow (
signup or login), the user’s email or phone, the original client IP and user agent, and the device token.3
Your policy produces a recommendation
The Risk Platform runs the policy for that flow and returns
allow, review or block, the rules that matched, and how complete the evidence was.4
Your application stays in control
The Risk API never blocks a user by itself. You choose whether to record the recommendation, send the account to review, or stop the signup. If the Risk API is slow or unavailable, your flow continues as usual.
Start by reviewing recommendations
The Risk API records what your policy recommends and leaves the decision to you. Start by sending checks and reviewing them in the dashboard. Tune your policies on your real traffic, then act on recommendations once they match what you see. See Recommendations and reasons.What’s in the dashboard
In the Abstract dashboard, open Risk Platform:- Dashboard: live check volume, recommendations over time, integration health and current alerts.
- Checks: every check with its recommendation, the signals it used, and a rule trace showing which conditions matched.
- Activity: repeated attempts from the same IP address, network or browser, with alert history.
- Policies: the rules that turn signals into a recommendation, with full version history and rollback.
- Lists: your own allow and deny lists of emails, IP addresses and phone numbers.
- Integration: setup steps and a health status for each flow, so you can confirm the browser and backend halves are connected.
- API Keys: your Site key and Secret keys.
Get started
Quickstart
Add the browser SDK and send your first signup and login checks.
Check endpoint
Request fields, response fields and errors.
Policies and rules
How a policy turns signals into a recommendation.
Keys
Site key and Secret key: which one goes where.