Reference & Lookup Data · Integration
Icypeas
Add Icypeas to your product for your customers, and give your AI agents governed access to it.
Icypeas exposes its lookups under app.icypeas.com/api, and the endpoints are POST only, so a GET against email-search returns a method-not-allowed rather than anything useful. Authentication is not a single bearer token: the account holds an API key and a secret, and each request carries a signature derived from them together with a timestamp, so a stored token on its own will not authenticate and clock skew produces rejections that look like bad credentials. Searches are asynchronous by design: a single email search returns a request id and the actual result arrives later, either through a webhook you register or by reading the results back, which means an integration must keep the request id joined to whatever record triggered it. Results are returned with a certainty level rather than a plain found or not found, and catch-all domains come back flagged as unverifiable, so business logic needs to handle three outcomes rather than two. Bulk jobs are separate from single searches and are billed per credit as rows are processed, so a partially completed file still consumes quota. fastn holds each customer's key and secret, signs each call, and keeps every lookup attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Icypeas account so enrichment runs on their credits rather than yours.
Verify an email address at the point a lead is created in your product and store the certainty level with it.
Run a domain scan when a new company record appears so contact suggestions arrive without manual research.
Submit a bulk file of stale contacts for verification and write the outcomes back onto your own records.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent verify a specific contact address before an email is sent, with credit use audited per tenant.
Let an agent report how many records in a segment came back unverifiable or catch-all.
Allow an agent to queue a bulk verification within a defined credit ceiling for that customer.
Example prompt
Is this contact's email address still valid, and how confident is the result?
Set up Icypeas in 4 steps
- 01Enable the Icypeas connector from your fastn dashboard.
- 02Have each customer authorise their own Icypeas account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Icypeas integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Icypeas integration without building it. Your customers connect their own Icypeas account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Icypeas update is not your on-call problem.
- One integration serves your product and your agents. The same governed Icypeas connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Icypeas, across other categories.
Salesforce
HubSpot
Notion
SnowflakeIcypeas integration FAQ
How do I add an Icypeas integration to my product?
Enable the Icypeas connector in your fastn dashboard, then let each customer authenticate their own Icypeas account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Icypeas client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Icypeas account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Icypeas 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.
Can AI agents use this Icypeas integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent verify a specific contact address before an email is sent, with credit use audited per tenant.
Who maintains the Icypeas integration?
fastn does. When Icypeas 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.
Whose credentials does an Icypeas lookup run under?
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.
How should Icypeas results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Icypeas 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.
What can I build with the Icypeas integration?
A common starting point: let a customer connect their own Icypeas account so enrichment runs on their credits rather than yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Icypeas integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Icypeas does not change your per-connector cost. You can start free with 3 connected accounts.
Add Icypeas to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.