Accuracy

Accuracy notes — Email verification and catch-all handling

Guidance for interpreting email verification results, including catch-all verification accuracy and identity signals.

Accuracy notes

Use Relentless Identity as a verification signal before sending, routing, or enriching a contact record.

Practical guidance

  1. Treat deliverable as the strongest positive signal in the response.
  2. Treat undeliverable as a signal not to assume the address is usable.
  3. Store the returned address when Finder resolves a verified result.

What to expect

  • Some responses include extra provider and MX context.
  • The compact public contract stays the same across dashboard, REST, and MCP flows.
  • The clearest production signal is whether the result is usable for your next step, not how much supporting detail was returned.

Quick links

Browse the docs

Start with the overview, move into authentication and implementation details, then keep the reference pages nearby while you build.

Relentless Identity Documentation — Email Finder and Verification APIGetting started — B2B email finder and verificationAuthentication — Email verification API accessCrypto paymentsREST API reference — Email Finder API and Verification APIMCP reference — Email verification agent workflowsCatch-all verification — Email verification for accept-all domainsAccuracy notes — Email verification and catch-all handlingResponse semantics — Email verification API results

Agent-ready docs

Copy this page or hand an agent `llms.txt`

Copy the current page as Markdown, or copy `llms.txt` when you want to give an assistant a clean index of the docs, reference, and related pages.

Open llms.txt

Companion routes

Reference, pricing, and access

Jump from the guides into the live API reference, pricing, or token management when you are ready to move from evaluation to production use.

View pricingAPI referenceManage tokens