Reference & Lookup Data · Integration
Crustdata
Add Crustdata to your product for your customers, and give your AI agents governed access to it.
Crustdata is organised around screeners and enrichment: /screener/company takes a filter body and returns matching companies, while enrichment endpoints take a company domain or a LinkedIn URL. Much of what you get back is a dated series rather than a snapshot, so headcount, job openings and web traffic arrive as arrays keyed by date and the caller has to choose which point in time to store. Several responses are column-oriented, with a fields list alongside rows, so mapping them as ordinary nested JSON produces the wrong shape. Authentication is an Authorization header carrying the API token, and a bad key returns a JSON message about an invalid API key rather than an empty body, which makes failures easy to detect but easy to swallow too. Some datasets refresh weekly rather than daily, so consecutive calls legitimately return identical values for several days. fastn stores each customer's token, normalises the paging and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Crustdata key so enrichment runs against their own entitlement.
Track headcount trend for accounts in a portfolio and flag sustained contraction.
Enrich a company record from its domain at signup and keep the firmographic fields refreshed.
Run a screener query to build a target list without exporting spreadsheets between tools.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent how an account's headcount has moved over the last two quarters, with each call audited per tenant.
Have an agent check open job postings at a company before a renewal conversation.
Let an agent screen for companies matching an approved filter and return the matching domains.
Example prompt
How has this company's headcount changed over the past two quarters?
Set up Crustdata in 4 steps
- 01Enable the Crustdata connector from your fastn dashboard.
- 02Have each customer authorise their own Crustdata 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 Crustdata integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Crustdata integration without building it. Your customers connect their own Crustdata 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 a Crustdata update is not your on-call problem.
- One integration serves your product and your agents. The same governed Crustdata 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 Crustdata, across other categories.
Salesforce
HubSpot
Notion
SnowflakeCrustdata integration FAQ
How do I add a Crustdata integration to my product?
Enable the Crustdata connector in your fastn dashboard, then let each customer authenticate their own Crustdata account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Crustdata client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Crustdata account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Crustdata 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 Crustdata integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent how an account's headcount has moved over the last two quarters, with each call audited per tenant.
Who maintains the Crustdata integration?
fastn does. When Crustdata 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 a Crustdata 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 Crustdata results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Crustdata 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 Crustdata integration?
A common starting point: let a customer connect their own Crustdata key so enrichment runs against their own entitlement. 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 Crustdata integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Crustdata does not change your per-connector cost. You can start free with 3 connected accounts.
Add Crustdata to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.