canonical: https://jentic.com/apis/anymailfinder.com/anymailfinder # AnyMailFinder Email Finder API 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. ## For AI agents Find and verify a prospect's professional email address by name and company domain, with results scored as valid, risky, or bad. ## Scope Does not handle email sending, drip campaigns, or CRM record storage - use for finding and verifying professional email addresses only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Find Email - Person** — Resolve a person's professional email from a name and company domain - **Find Email - Decision Maker** — Find the most likely contact for a role category at a target company - **Verify Email** — Check deliverability of an email against the recipient mail server - **Report Bad Email** — Send feedback that a returned email no longer works ## Why Jentic - **Setup:** Wiring AnyMailFinder by hand means handling its API key auth, posting to the right v5.1 find and verify routes, and building your own retry and error handling for lookups that resolve asynchronously. Through Jentic you install once, import AnyMailFinder from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** AnyMailFinder addresses its work through request bodies rather than resource ids in the URL, so you limit the agent to the operations it needs, such as finding a person's email or verifying an address. Reporting a bad email is a separate operation that is only available if you include it in the allowed set. - **Credential handling:** Your AnyMailFinder API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a professional email address' or 'verify an email address', and Jentic returns the matching AnyMailFinder operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hunter.io API** — Email finder and verifier with domain search and pattern detection. - **RocketReach API** — Contact lookup including phone numbers and social profiles, not just email. - **Clearout API** — Bulk email verification with high-volume discount pricing. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the AnyMailFinder Email Finder API? Yes. Because you run Jentic One yourself, your own rules decide which AnyMailFinder operations and credentials the agent can use. AnyMailFinder identifies its work through request bodies rather than resource ids in the URL, so you can grant only the operations the agent needs, such as finding a person's email or verifying an address, and hold back others. Reporting a bad email is a separate operation that the agent can call only if you include it in the allowed set.