Reference & Lookup Data · Integration
Dun & Bradstreet
Add Dun & Bradstreet to your product for your customers, and give your AI agents governed access to it.
Embed a Dun & Bradstreet integration so your customers can match and enrich their own company records from inside your product, using their own subscription and entitlements. Lookups run per tenant so usage is attributable to the customer that caused it, and bulk enrichment runs are throttled so they do not exhaust a customer's allowance. fastn handles each customer's credentials and API upkeep, so onboarding a new subscription is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers match their own company records to a D-U-N-S number from inside your product.
Enrich accounts with firmographic and corporate linkage data so records are usable at signup.
Read the risk and credit data a customer is entitled to so onboarding checks happen in your app.
Re-check records on a schedule so stale company data is refreshed automatically per tenant.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent enriches a company record before answering a question about who the customer is.
An agent runs a match or lookup within governed permissions and per-tenant entitlements.
An agent reacts to a new account in your product and enriches it before the next workflow step.
Example prompt
Match this week's new accounts to a D-U-N-S number and list the ones that came back with no confident match.
Set up Dun & Bradstreet in 4 steps
- 01Open the Dun & Bradstreet connector from your fastn dashboard.
- 02Have each customer authenticate their own subscription with least-privilege credentials.
- 03Map the company fields your product writes into, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Dun & Bradstreet integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dun & Bradstreet integration without building it. Your customers connect their own Dun & Bradstreet 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 Dun & Bradstreet update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dun & Bradstreet 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
ClearbitWorks well with
Salesforce
NetSuiteOften used alongside
Tools the same teams tend to run next to Dun & Bradstreet, across other categories.
HubSpot
Notion
Snowflake
BoxDun & Bradstreet integration FAQ
How do I add a Dun & Bradstreet integration to my product?
Enable the Dun & Bradstreet connector in your fastn dashboard, then let each customer authenticate their own Dun & Bradstreet account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dun & Bradstreet client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dun & Bradstreet account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dun & Bradstreet 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 Dun & Bradstreet integration?
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 enriches a company record before answering a question about who the customer is.
Who maintains the Dun & Bradstreet integration?
fastn does. When Dun & Bradstreet 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 Dun & Bradstreet 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 Dun & Bradstreet results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Dun & Bradstreet 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 Dun & Bradstreet integration?
A common starting point: match their own company records to a D-U-N-S number from inside your product. 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 Dun & Bradstreet integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dun & Bradstreet does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dun & Bradstreet to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.