> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noresponse.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Signup assessment

> One call at account creation, login or purchase returns the current risk of the account and a decision that your platform applies.

> [!NOTE]
>
> 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](https://docs.noresponse.org/quickstart.md).

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](https://docs.noresponse.org/guides/signup-quickstart.md) 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`.

```json title="The part of every answer that you act on" theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "status": "partial",
  "flow": "account_creation",
  "account": {
    "id": "usr_8f2k1",
    "risk": {
      "score": 5,
      "decision": "allow",
      "reasons": [
        { "code": "context_locale_mismatch", "direction": "raises", "impact": "low", "identifier": "context" },
        { "code": "no_breach_history", "direction": "neutral", "impact": "none", "identifier": "email" }
      ]
    },
    "decisions_by_flow": { "account_creation": "allow", "login": "allow", "purchase": "allow" }
  }
}
```

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`.

| Status | HTTP | What it means |
| - | - | - |
| `complete` | 200 | Every source answered or failed for good. The score will not move. |
| `partial` | 200 | A decision exists, but one or more sources are still answering. The score can still move. |
| `pending` | 202 | No source answered before the deadline. This assessment has no score yet. On the first assessment of the account, `account` is absent. On a later assessment, `account` carries the earlier decision. |

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](https://docs.noresponse.org/guides/pending.md) tells you how to wait for the final answer. [Webhooks](https://docs.noresponse.org/guides/webhooks.md) 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](https://docs.noresponse.org/guides/assess.md) gives the two choices.

## Terms

The rest of this site uses these words.

| Term | Meaning |
| - | - |
| Assessment | One answer about one flow for one account. Its `id` starts with `asm_`. By default it stays for 365 days. |
| Account id | The opaque id of the account on your platform, sent as `account_id`. It goes in the body, not the URL. |
| Identifiers | What NoResponse looks up: one or more of `email`, `username` or `phone`. `name` and `ip` make the match more precise. |
| Risk score | `account.risk.score`, the current score of the account, from 0 (safe) to 100 (risky). It comes from the reasons that fired. |
| Decision | `account.risk.decision`: `allow`, `step_up`, `review` or `block`, for the flow that you assessed. `account.decisions_by_flow` gives one for each flow. |
| Reasons | `account.risk.reasons`: each reason that fired, with its direction, its impact and, if it applies, its identifier. The codes are stable. |
| Band | `detail.risk.band`: `low` for 0 to 29, `medium` for 30 to 59, `high` for 60 to 84 and `critical` for 85 to 100. |
| Status | `complete`, `partial` or `pending`, as above. A webhook can also carry `expired`, which means that the assessment is gone. |
| Source | One place where NoResponse asks about an identifier. `detail.risk.coverage` counts the sources. `detail.incomplete_sources` groups them into the lanes `accounts`, `phone`, `breach`, `domain` and `ip`. |
| Policy version | `detail.risk.policy_version` identifies the scoring policy. `detail.policy_version` identifies the assessment policy. Store both with each decision. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.