AnyMailFinder Email Finder API

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.