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

# Coverage and status

> Know which signals were evaluated before enforcing a decision.

SignupBear reports both overall status and per-signal coverage. Check these
fields when you send more than an email.

## Status

| Status     | Meaning                                                                        |
| ---------- | ------------------------------------------------------------------------------ |
| `complete` | Every requested, available signal was evaluated                                |
| `partial`  | At least one signal was evaluated and another requested signal was unavailable |
| `failed`   | No requested signal could currently be evaluated                               |

## Coverage

Each signal in `coverage` is one of:

* `complete`: evaluated by the current policy
* `unavailable`: requested, but the capability is not currently available
* `not_requested`: not included in the request

During private beta, an email-only request normally returns:

```json theme={null}
{
  "status": "complete",
  "coverage": {
    "email": "complete",
    "ip": "not_requested"
  }
}
```

An email and IP request normally returns `status: "partial"` because IP checks
are not yet available.

<Warning>
  An IP-only request is accepted by the API, but returns HTTP 200 with
  `status: "failed"`, `risk_level: "unknown"`, and `recommended_action: "flag"`.
  Do not treat HTTP 200 alone as permission to create an account.
</Warning>