{"success":true,"data":{"name":"email_status","description":"Deliverability of the person's best email, from verification rather than a guess. On a BUSINESS address (`work`, `work_other`, `other`), `verified` means OUR OWN verifier sent to the address and it accepted — nothing else earns the word, and a data supplier asserting that an address is good is not a check, whichever supplier it is: those are published as `untested`. PERSONAL ADDRESSES ARE THE EXCEPTION and the difference is worth knowing: we do not verify consumer domains at all, so on a personal address `verified` still means a supplier asserted it and you should treat it as a lead to verify rather than a confirmed one. The dedicated personal-email endpoint publishes no status for that reason. `catch_all` means WE probed the domain, on the same rule and with the same personal-address exception. In practice that changes nothing for catch_all — a catch-all verdict can only come from probing the domain, which no supplier does — so the whole of the current catch_all population already qualifies. This narrowed on 2026-09-20 and again on 2026-09-22, so a `verified` count taken before either date is not comparable with one taken after — the population is smaller each time and every address in it has been tested by us. ONE INCONSISTENCY WHILE THIS ROLLS OUT: enrichment (/v1/people/enrich, the v2 contact endpoints, MCP) applies the narrow rule per address; people search does not, because the search index carries no per-address verification provenance. A person can come back `verified` in a search row and `untested` when enriched, and the enriched answer is the correct one. Treat a search count of `verified` as an upper bound and confirm per address on enrichment. Safe to send: verified, and catch_all_valid — a mailbox on a catch-all domain whose EXISTENCE we confirmed through the provider's identity check (Microsoft 365 managed tenants and Google Workspace only; the domain would accept any address, this one is known to be real). It ranks between verified and catch_all and is earned only by that check, never by a supplier and never by re-reading an older catch_all verdict. As a FILTER, `catch_all` matches both catch_all and catch_all_valid (a confirmed mailbox is still on a catch-all domain), so an existing verified+catch_all filter keeps the promoted people; filter on `catch_all_valid` alone for the narrow set. Cannot be confirmed either way, because the domain accepts everything: catch_all. Do not send: invalid, spam_trap, abuse, disposable. Use with care: risky, role (a shared mailbox like info@) and derived (built from the company's address pattern and never tested). untested means nobody has checked this address yet — it may well be fine, and it is the largest group; unknown means it WAS checked and the result was inconclusive, which is a weaker signal than untested, not a stronger one. none means the person has no email.","total":13,"matched":13,"values":["verified","catch_all_valid","catch_all","risky","unknown","untested","invalid","role","disposable","spam_trap","abuse","derived","none"],"labels":{"verified":"Deliverable","catch_all_valid":"Catch-all, mailbox confirmed","catch_all":"Catch-all domain","risky":"Risky","unknown":"Unknown","untested":"Not yet checked","invalid":"Undeliverable","role":"Role address","disposable":"Disposable address","spam_trap":"Spam trap","abuse":"Abuse / complainer","derived":"Derived, not verified","none":"No email"},"truncated":false}}