Hunter

Enable the Hunter connector in your fastn dashboard, then let each customer authenticate their own Hunter account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Hunter client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Hunter account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent verifies an address before drafting outreach, so a bad send is caught first.

fastn does. When Hunter changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.

Per tenant, with a window that matches how fast the underlying data actually moves. Hunter is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.

A common starting point: verify an email address inside your product before it is saved or messaged. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Hunter does not change your per-connector cost. You can start free with 3 connected accounts.