Skip to main content
Every AuthFlame check returns a summary object that condenses the underlying signals into two fields you can act on directly: risk_score and action.

​
The summary object

  • risk_score: an integer from 0 (safe) to 100 (highest risk).
  • action: the recommended enforcement decision, either ALLOW or BLOCK.
summary.action is AuthFlame’s opinion about what your signup flow should do.
  • ALLOW: proceed with account creation.
  • BLOCK: reject the signup. Show a generic error so you don’t leak which signal tripped.

​
Rolling your own thresholds

If you need custom behavior, branch on summary.risk_score directly and ignore action. For example, you could add an email verification step for free-trial signups that are allowed but score above 25, or block at a lower score than AuthFlame does if you want to be stricter. The score is derived entirely from the signals returned in the response, so it’s safe to use in your own rules engine. Keep in mind that some signals depend on live data, such as the disposable-domain list (updated regularly) and DNS lookups. The same address can therefore score differently over time if that data changes.