The Email Finder API That Verifies Before It Answers.

An email finder APIis an endpoint that takes a person’s name and a company domain and returns their work email address programmatically, so your product, CRM enrichment job, or outbound pipeline can discover addresses without a human pasting names into a web form.

The Verifox version goes one step further: it verifies every candidate over SMTP before answering, so the address you receive is one the engine actually reached, not a pattern guess. For one-off lookups in the browser, the email finder tool runs the same engine without any code.

You POST firstName, lastName, and domain to /v1/email-finder and get a jobId back right away. The engine then generates every plausible permutation of that name at that domain and verifies each one with a live SMTP handshake, plus MX, catch-all, and disposable checks.

When you poll GET /v1/email-finder/:jobId and status reads completed, the bestMatch field holds the winning address with its reachable verdict and a confidence score. The full request and response shapes are in the API reference.

Every result passes through the same 9-point engine that scores 99.99% accuracy on a 1,000-address benchmark list: syntax, domain and MX records, a real SMTP mailbox ping, disposable and role detection, catch-all detection, and AI-confidence scoring on catch-all domains.

That last part matters because 20-40% of B2B addresses sit behind catch-all domains where a plain handshake says yes to everything. The confidence score in the response tells you how much to trust each match, and the deeper checks are described on the email verification service page.

One find costs 10 credits, charged when you start the job. Polling the job status is free. A new account starts with 1,000 free credits, or 2,500 if you sign up with a work email, and no card is required.

Past the free balance, credits are pay-as-you-go and never expire, so a quiet month costs nothing. Volume tiers are shown for your region on the pricing page.

Send your key in the X-API-Key header on every request, exactly as the code samples on this page show. Keys look like vfx_... and are generated in the dashboard after you create a free account.

Keep the key server-side. Calls travel over HTTPS only, and you can rotate or revoke a key from the dashboard at any time without touching the others.

The standard limit is 60 requests per minute per key. Finder jobs run asynchronously, so the POST returns in milliseconds and the verification work happens in the background; the documented example job completes in about 15 seconds.

The underlying verification engine runs at a median of ~380 ms per single check and sub-50 ms on cached results, which is what keeps multi-permutation jobs quick. If you hit a 429, back off briefly and retry.

Yes. Because each find is one POST, you can queue an entire prospect list by firing requests inside the rate limit and polling the jobIds as they complete. For spreadsheet-sized batches without code, the bulk email finder handles upload, dedupe, and export in the browser.

And when you need every address at one company rather than one person, the find email by domain tool and the domain email extractor work the problem from the company side.

B2B contact discovery is generally processed under legitimate interest, but the obligations are yours: a lawful basis, a clear opt-out in outreach, and honoring erasure requests. The API only returns business addresses inferred from public name-at-domain patterns, never scraped personal inboxes.

On our side, Verifox is SOC 2 Type II audited, and addresses are processed in memory, never stored, logged, or sold. The data-handling detail lives in the privacy policy.

Same engine, different surface. The web email finder is built for a human doing a handful of lookups, while the API is built for volume and automation: enrichment pipelines, CRM hygiene jobs, signup-form enrichment, anything that runs without a person watching.

The API also gives you the raw job object, so you can branch on the reachable verdict and confidence score in code, and the history endpoints let you save and query past searches. For LinkedIn-specific workflows there is a dedicated LinkedIn email finder.

Yes, natively. The Verifox MCP server wraps this endpoint as the find_email tool with get_find_job for polling, so Claude, Cursor, or any MCP client can turn a name and a domain into a verified address inside an agent loop.

Both paths bill the same 10 credits per find against the same balance. If you are building retrieval into a product rather than an agent, the plain REST endpoint on this page is usually the simpler wire. The AI email finder page covers the agent-side workflow in more depth.