Email Validation API
Free plan · From $28.90/moActively maintained
≈ 1visits/mo
Little sign of use · estimate, read Oct 13, 2026
- For
- Product and marketing teams checking email addresses at signup or across lists
- Price
- Free plan · From $28.90/mopricing page, read Oct 21, 2026
- Activity
- Actively maintainedsite updated 5 days ago
- Runs as
- API
- Used for
- Check individual email addresses on catch-all domains
- Validate email lists in bulk
- Add email verification to signup forms
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsinboxtrue.com ↗
- MCP servercom.inboxtrue/inboxtrueverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-21
- Address to connectapi.inboxtrue.com/mcp
- API docsinboxtrue.com/docsthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Email Validation API for?
Sign in to leave a noteWhat is Email Validation API?
Checks email addresses for syntax, MX records, mailbox existence, disposable domains and catch-all status in one API call.
Who is Email Validation API for?
Product and marketing teams checking email addresses at signup or across lists
How much does Email Validation API cost?
Email Validation API has a free plan; paid plans start at $28.90/mo, per its pricing page on 2026-10-21.
Is Email Validation API free?
Yes, Email Validation API has a free plan, per its pricing page on 2026-10-21.
Do people use Email Validation API?
Little sign of use: ≈ 1 visits/mo · estimate, 2026-10.
Is Email Validation API still maintained?
Actively maintained: site updated 5 days ago.
How do I cancel Email Validation API?
In its own words (terms of service, 2026-10-21): “You may cancel your account at any time.”
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.