Email verification with business identity and company discovery.
Verify deliverability and enrich with lead and company data in one request. API and MCP support.
// POST /v1/verify-enrich · 200 OK · 42ms
{
"email": "j.morgan@acme.com",
"verdict": "valid",
"score": 98,
"checks": {
"syntax": true,
"smtp": true,
"catch_all": false,
"disposable": false
},
"person": {
"name": "Jordan Morgan",
"title": "VP of Marketing"
},
"company": {
"name": "Acme Corp",
"domain": "acme.com",
"industry": "Software",
"size": "201–500",
"location": "San Francisco, US"
}
}Three things returned from a single call.
Verification answers is this email real. Reverse enrichment answers who is behind it. Mailtrue returns both in one response — no two-vendor stitch.
Deliverability verdict
Full SMTP handshake, syntax, MX, catch-all and disposable checks. Sub-50ms p95.
Who the address belongs to
From the verified email, return the person's name and job title. Identity from address — never the other way around.
Firmographics from the domain
Industry, size, location and the canonical company record — capped at firmographics, by design.
An API first.
An MCP server second.
The distribution moat. Multi-language SDKs, an OpenAPI you can generate against, async bulk jobs. And — uniquely — a first-party MCP server so the verify call lives inside the agentic workflow, not bolted to the side.
One endpoint, shape-stable JSON
POST /v1/verify-enrich returns the same record schema for every email — your code never branches on missing fields.
Drop it into your agent
First-party MCP server. Cursor, Claude Desktop, your custom agent — exposes verify + enrich as tool calls.
Bulk file jobs
Upload CSV or JSONL, poll the job, download the enriched output. 100k addresses in minutes, not hours.
Typed, idiomatic clients
Official Node, Python and Go. Auto-retry, structured errors, full type coverage on the response.
# Verify + enrich a single address curl https://api.mailtrue.io/v1/verify-enrich \ -H "Authorization: Bearer mt_live_…" \ -H "Content-Type: application/json" \ -d '{"email":"j.morgan@acme.com"}' # → { status, score, person, company }
Four buyers, one guarantee.
Input is always an email. Enrichment is capped at firmographics. Enforced at the API, not just in positioning — which is exactly what each of these teams is buying.
Verify before send. Backfill what's missing.
Verify lists pre-send to stay under bounce thresholds, then reverse-enrich every verified address to fill CRM gaps — without a second vendor in the pipeline.
- Bulk verify CSV / pipeline call
- Reverse enrich on the same response
- Direct CRM push from one call
List cleaning, embedded.
Drop Mailtrue into your send pipeline. Verify on import, suppress invalid, enrich what's missing — non-competitive with Skrapp by design.
- Per-tenant API keys
- Volume pricing for embedded use
Email-in, firmographics-out — for agents.
First-party MCP server turns verification + enrichment into typed tool calls. The agent doesn't scrape, it asks Mailtrue.
- MCP — Cursor, Claude Desktop, custom
- Shape-stable tool responses
- Per-call budget caps
Subscription, no list-upload lock-in.
Start free with 100 credits. Subscribe for 10,000 a month. Trial credits don't expire — margin comes from enrichment, optional.
- Subscription · cancel anytime
- Verify-only or verify+enrich
Drops in where
your email already flows.
Native connectors with the major send platforms and CRMs. First-party MCP for the agent stack. Zapier and n8n for the long tail.
100 credits free.
Then $19/mo.
Free trial credits get you started. The subscription unlocks the monthly pool — one credit per call, whether you just want the deliverability verdict or you also want the person and the company.
One unit, one price. Verify a list, enrich the survivors — both spend the same credit.
- 01Free trial
100 credits at signup. They don't expire — use them when you need them.
- 02One credit, one call
Each request is one credit, whether you just verify or verify + enrich. No split meter to reason about.
- 03Subscribe when you're ready
Subscription credits refresh each billing month. Cancel anytime; trial credits stay with the account.
- 04API included
Same price as the dashboard. No premium tier to unlock the obvious.
Engineering-grade from the inside out.
The infrastructure stats that matter to a developer evaluating whether to put us in front of their send pipeline.
One address in.
Two answers out.
100 free verifications. Live API key in 30 seconds. Drop the MCP server into your agent on the way out.
$ npm i mailtrue $ export MAILTRUE_KEY=mt_live_… $ mt verify j.morgan@acme.com → valid · Jordan Morgan · VP Marketing · Acme
FAQ
Questions teams ask before switching.
How accurate is Mailtrue compared to NeverBounce or ZeroBounce?+
We benchmarked one million mixed-quality emails against both providers. Mailtrue matched or beat them on every category and caught 14% more catch-all risks. We're happy to share the full benchmark on request.
Do you store the emails I verify?+
Never by default. Verification results are cached for 24 hours via salted hash only — so repeated lookups don't burn credits — and you can disable caching entirely with one toggle. SOC 2 Type II, GDPR-compliant.
How fast is the API?+
15ms median, 180ms p99 for the real-time endpoint. Fast enough to drop into a signup form without spinners. Bulk CSV runs at ~1M emails per hour.
Can I switch from NeverBounce without rewriting my code?+
Yes. Our /v1/verify endpoint accepts the same request shape and returns a compatible response. Most teams change one base URL and one API key.
What happens if I run out of credits?+
Nothing breaks. Your API keeps responding with a 402 you can handle gracefully. Upgrade to the subscription to unlock the monthly credit pool.