Skip to content
Neural Evo

Overview

Validate first. Gate signup with one field.

Email Score inspects an address or bare domain, then returns verdict. Your backend can continue onboarding when the value is allow, or reject the attempt when it is block.

Integration rule of thumb

Call validate from your server. Branch on verdict === "allow". Store policyReason, checks.disposable, and deliverability for support tickets and analytics. Do not invent your own score from those fields unless you have a custom policy.

What runs in a validation

  1. Parse: confirm the input is a usable email or domain string.
  2. List and Space rules: apply disposable / block lists and any allow or block rules on your Space.
  3. Mail signals: look up DNS and MX (or skip when a known provider says DNS is unnecessary).
  4. Verdict: set allow only when checks.syntax is pass, checks.disposable is miss, and deliverability is deliverable. Every other outcome is block.

Email vs domain requests

user@company.com

Full address path. You get provider classification, disposable checks, and domain mail signals in one response.

company.com

Domain-only path. Useful when you already separated the host, or when you want a host-level gate before collecting a full email.

Prefer POST /api/v1/validate/detect if your client may send either shape. Both paths return the same response model, including verdict.

How to read allow and block

allow

Syntax passed, disposable checks missed, and mail signals look healthy. Safe default: create the account (or advance the next onboarding step).

block

Invalid syntax, disposable / blocklist hit, or deliverability that is undeliverable, unknown, or skipped. Safe default: stop with a neutral error and ask for another address.

Concrete outcomes

  • jordan@acme.io

    Typical business domain with MX: allow. Proceed with signup.

  • guest@mail.tempmail.com

    Matches a disposable / block list: block. Reject without naming the list publicly.

  • totally-broken

    Fails parse: block. Prompt the user to fix the field.

Space allowlists and blocklists still matter. A trusted host you allow, or an abusive host you block, updates the same verdict your API consumer reads.

Supporting fields (not the gate)

checks.disposable and policyReason
Explain list hits and overrides (clean, blocklist, allowlist, invalid syntax, and similar).
deliverability.status
Mail-ability signal: deliverable, undeliverable, unknown, or skipped. The usage page Status column mirrors this value. It is context for humans and charts, not a replacement for verdict.
provider and flags
Optional enrichment such as known mailbox providers and role accounts. Helpful for product analytics; still secondary to verdict.

Email Score does not ship a 0 to 100 risk score. You get structured facts plus a single decision field built from those facts and your Space rules.

Next pages

  • Quickstart: create a Space, mint a key, fire a first request.
  • API reference: request bodies, auth headers, and response schemas for email, domain, detect, and account.