email quality score api
Email quality score API
Use a quality score to capture how useful an email address is for your product and operations.
Quality is broader than validity because it includes usefulness and trustworthiness.
It helps you decide whether to accept, warn, or block the address.
It is best treated as an actionable metric, not just a label.
{
"result": "risky",
"score": 64,
"signals": ["mx_found", "free_email", "catch_all"]
}How is quality different from risk?
Risk focuses on abuse or failure; quality includes utility and expected value.
Can I customize it?
Yes. Your business rules should decide what counts as high or low quality.
Why a score is easier to use
A single score is easier to wire into product decisions than a long list of raw checks. It lets your app map email outcomes to simple actions such as accept, warn, review, or block.
What should affect the score
Score models usually combine syntax, MX, disposable status, role-based status, catch-all behavior, and optional SMTP results. The point is to make the decision explainable and consistent, not merely numeric.
FAQ
How do I use this page?
Use it as a quickstart reference and link it from your docs, onboarding flow, or marketing page.
What should I do next?
Create an account, try the demo, and move the integration into your backend with a real API key.
Is high score always safe?
No. It only means the address looks better by your configured criteria.
Should I expose the score to users?
Usually as a friendly result, not as the full internal formula.