POST https://api.outreign.io/rest-api/email/verify. MCP: verify_email.
Accepts only email: a nonempty string up to 320 characters. The handler trims and lowercases it. Malformed syntax can produce an invalid verdict rather than a request-validation error. Checking an address never sends email or creates a lead.
Response fields
Illustrative response, not evidence about an actual mailbox:
Decide what to do
DNS/MX records only establish domain mail capability. They do not establish a particular person’s mailbox, consent, ownership or inbox placement. A valid result is not permission to contact someone.
Limits and freshness
Paid account required. Checks charge no reveal credit, but share a 10-request/minute account limit and a rolling 24-hour verification allowance across API, MCP and agent chat: Starter 100, Growth 250, Pro 500, Agency 1,500. These checks are a separate counter from calendar-day prospect searches. Cache results can be reused for 30 days; no public force-refresh argument is supported. Request limits still apply to cached checks and malformed addresses. Do not poll verification aggressively. When limited, wait rather than changing API keys: the verification cap is owner-scoped.Failure handling
Inspect both HTTP status and JSONerror. A handled provider failure can return HTTP 200 with status: "unknown", verified: null and an error. Preserve that uncertainty; do not convert null to true or false. See production guidance.