Skip to main content
Signup assessment is in maintenance. It gets fixes, and no new features. Investigation and people screening run on the same lookups. Start with the quickstart.
The signup assessment tells you how risky a new account is before your platform creates it or gives it free credits. Your backend makes one call at account creation, login or purchase. The call sends the email, username or phone that the user typed. NoResponse looks up the identifiers and answers within 3 seconds. The signup quickstart builds this gate.

What NoResponse looks up

The lookup covers these data:
  • The accounts that the user holds on other platforms.
  • Breach, credential-list and stealer-log exposure.
  • Phone data: line type, carrier, spam reports and caller-ID names.
  • IP data: VPN, proxy, Tor, hosting and country.
  • The history on your platform: repeat identifiers, shared IPs and the outcomes that you report.

The answer

The answer is an assessment. It starts with account, which is the one current risk of the account. account holds a score from 0 to 100, the reasons that moved the score, and a decision for the flow that you assessed. The decision is allow, step_up, review or block. Your code applies the decision with its own rules, so you keep control of the account. The facts of this assessment alone are under detail.
The part of every answer that you act on
The standard answer has more data under detail. It holds the score, band, confidence and reasons of this assessment. It also holds typed summary facts for each identifier. For example: how many accounts the email has, whether the phone is VoIP, and whether the IP is a proxy. The detailed view adds the breach tables that matched, and one signal for each source answer.

How a call goes

  1. Your account creation route calls POST /v1/assessments with the flow, the identifiers and an Idempotency-Key.
  2. NoResponse answers within 3 seconds. At quick depth, the default for a login, it answers within 500 ms. Most answers carry the decision for the account.
  3. Your code applies its own rules to the decision, score and reasons. Then it creates the account, asks for a second factor, or puts the account in a queue for your team.
  4. If sources were still answering, a signed webhook delivers the updated assessment. Your code runs the same rules again.
  5. Later, your platform reports the outcome of the account. This makes the next score for that user better.

The three statuses

Every assessment has a status. Read a partial answer carefully. The answer is usable, and your code can act on it, but a later revision can change it. One real account creation answered partial with a score of 8 and allow. Five seconds later the same assessment was complete with a score of 33, after the accounts source answered. Each revision has a higher detail.assessment_version. Store the version that you acted on next to the decision. Pending, retries and idempotency tells you how to wait for the final answer. Webhooks tells you how to receive it. An answer without account has no decision. Your code applies the fallback that you chose for that case. Assess account creation, login and purchase gives the two choices.

Terms

The rest of this site uses these words.