AnyMailFinder Email Finder API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey4 EndpointsREST
For Agents
Find and verify a prospect's professional email address by name and company domain, with results scored as valid, risky, or bad.
Use for: I need to find the email address of a person at a specific company, Find the head of marketing at acme.com, Verify whether sales@example.com is deliverable, Look up the decision maker for engineering hiring at a company
Not supported: Does not handle email sending, drip campaigns, or CRM record storage - use for finding and verifying professional email addresses only.
Jentic publishes the only available OpenAPI specification for AnyMailFinder Email Finder API, keeping it validated and agent-ready. AnyMailFinder finds and verifies professional email addresses for prospecting, recruiting, and sales outreach. The API resolves a person email by name and domain, finds the decision-maker email for a target role at a company, verifies an email's deliverability against the recipient's mail server, and accepts bad-email reports to keep results fresh. Authentication is a Bearer token passed in the Authorization header.
Install Jentic One Beta
Connect the AnyMailFinder Email Finder API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AnyMailFinder Email Finder API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AnyMailFinder Email Finder API.
Resolve a person's professional email address from a full name and a company domain
Find the email of a decision-maker for a job category at a target company
Verify whether an email address is deliverable, risky, or invalid before sending
Report a bad or bounced email back to AnyMailFinder so it stops being returned to others
Receive credit-aware responses so an agent can budget API spend per lookup
Use Cases
Patterns agents use AnyMailFinder Email Finder API for, with concrete tasks.
★ Outbound prospecting list build
Resolve professional email addresses for a list of named prospects and their employer domains so an outbound team can run a cold campaign without scraping. The agent calls /find-email/person with full name and domain, then runs each result through /verify-email to drop any invalid addresses before import into a sequencer.
For each row in a prospect CSV, POST {full_name, domain} to /find-email/person, then POST the returned email to /verify-email and keep only results marked valid
Decision-maker discovery for ABM
Find the email address of the senior person responsible for a function (sales, engineering, finance) at a named company, without having a specific person's name. The agent calls /find-email/decision-maker with the company domain and a category, and AnyMailFinder returns the most likely contact for that role.
POST to /find-email/decision-maker with {domain: 'acme.com', category: 'sales'} and return the matched email and confidence score
Pre-send email verification
Verify a list of email addresses against the recipient mail server before a marketing or transactional send to drop bounces and protect sender reputation. /verify-email returns a status of valid, risky, or invalid, plus the SMTP-level reason. Agents use the result to filter recipients before handing the list to SendGrid or Mailgun.
For each address in a list, POST it to /verify-email and exclude any address with status != 'valid' from the next campaign send
AI agent integration via Jentic
An agent enriching a CRM record can search Jentic for 'find a professional email address', load the AnyMailFinder schema, and call the right operation without managing API keys. Bad-email feedback can be looped back through /report/bad-email to keep results fresh for future runs.
Search Jentic for 'find a professional email address', load /find-email/person, execute it for each Salesforce contact missing an email, and write the result back
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for anymailfinder email finder api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/find-email/person
Find a person's email by full name and domain
POST
/find-email/decision-maker
Find the decision-maker email for a role category at a company
POST
/verify-email
Verify deliverability of an email address
POST
/report/bad-email
Report a previously returned email as bad
POST
/find-email/person
Find a person's email by full name and domain
POST
/find-email/decision-maker
Find the decision-maker email for a role category at a company
POST
/verify-email
Verify deliverability of an email address
POST
/report/bad-email
Report a previously returned email as bad
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AnyMailFinder API keys are held in the Jentic vault (MAXsystem). The Bearer token is attached server-side, so the secret never appears in the agent's prompt or logs.
Intent-based discovery
Agents search Jentic by intent ('find a professional email address', 'verify an email address') and get the right AnyMailFinder operation with its argument schema, no docs reading required.
Time to first call
Direct integration: a few hours for auth, retry, and credit-aware error handling. Through Jentic: under 30 minutes - search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AnyMailFinder Email Finder API through Jentic.
Why is there no official OpenAPI spec for AnyMailFinder Email Finder API?
AnyMailFinder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AnyMailFinder Email Finder API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AnyMailFinder Email Finder API use?
API key auth is passed as a Bearer token in the Authorization header. Through Jentic the key is stored encrypted in the MAXsystem vault and injected per call, so the agent never handles the secret.
Can I find a decision maker without knowing their name?
Yes. POST to /find-email/decision-maker with the company domain and a role category (for example sales or engineering) and the API returns the most likely contact for that function with a confidence score.
How do I verify an email address through Jentic?
Search Jentic for 'verify an email address', load the schema for /verify-email, and call it with the address to check. The response indicates whether the address is valid, risky, or invalid based on an SMTP probe.
What are the rate limits for the AnyMailFinder Email Finder API?
Rate limits and monthly credit caps depend on the AnyMailFinder plan and are not declared in the OpenAPI spec. Each find and verify call typically consumes one credit; check your dashboard for the current quota.
What happens if the API cannot find an email?
The find endpoints return a not-found status with no email body and do not consume a search credit, so an agent can retry with a different name or fall back to a decision-maker lookup without paying twice.
GET STARTED