Reference & Lookup Data · Integration
Owler
Add Owler to your product for your customers, and give your AI agents governed access to it.
Embed an Owler integration so your customers can enrich and research companies from inside your product using their own Owler account and their own request allowance. Owler, a Meltwater offering, is company intelligence: profiles for millions of public and private businesses, firmographic detail such as sector, size and revenue estimates, competitor sets, and news about the companies a customer follows. This is a read surface, so the value is lookups and enrichment rather than writing back. Every call runs per tenant, so one customer's usage never draws down another's allowance, and results map into your own fields as configuration rather than code. fastn owns the credential handling, retries, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers enrich a company record inside your product using their own Owler account rather than a key you pay for.
Look up firmographic detail on creation so a new account arrives with sector, size and revenue context already filled in.
Read competitor sets per tenant so your product can show who a company is measured against.
Pull recent company news so a user sees what changed at an account without leaving your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent researches a company before a call and cites the profile detail it used, with each lookup logged.
An agent enriches newly created records within governed permissions, drawing on that tenant's own allowance.
An agent reports which followed companies had notable news in the last week.
Example prompt
Enrich the accounts added this week with sector and size, and tell me which ones had news in the last month.
Set up Owler in 4 steps
- 01Enable the Owler connector in your fastn dashboard.
- 02Have each customer connect their own Owler account so lookups run under their credentials and allowance.
- 03Map the company profile, firmographic and news fields to your own fields, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Owler integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Owler integration without building it. Your customers connect their own Owler 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 Owler update is not your on-call problem.
- One integration serves your product and your agents. The same governed Owler 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
Apollo
SalesforceOften used alongside
Tools the same teams tend to run next to Owler, across other categories.
HubSpot
Notion
Snowflake
BoxOwler integration FAQ
How do I add an Owler integration to my product?
Enable the Owler connector in your fastn dashboard, then let each customer authenticate their own Owler account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Owler client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Owler account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Owler 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 Owler 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 researches a company before a call and cites the profile detail it used, with each lookup logged.
Who maintains the Owler integration?
fastn does. When Owler 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 Owler 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 Owler results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Owler 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 Owler integration?
A common starting point: enrich a company record inside your product using their own Owler account rather than a key you pay for. 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 Owler integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Owler does not change your per-connector cost. You can start free with 3 connected accounts.
Add Owler to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.