Reference & Lookup Data · Integration
Brandfetch
Add Brandfetch to your product for your customers, and give your AI agents governed access to it.
Brandfetch resolves a company domain into brand assets through GET /v2/brands/{domain} on api.brandfetch.io with a bearer API key. The response is not a single logo: it is an array of logos, each with a type such as logo, symbol or icon, a theme of light or dark, and several formats including svg and png, so picking the right one for a dark UI means filtering on theme and format rather than taking the first item. Colours come back typed as brand, accent or dark, and fonts and company details such as industry and social links sit alongside them. The name search endpoint is a separate product that authenticates with a client identifier rather than the API key, which is a common source of confused 401s. Domains with no collected brand return a not-found rather than an empty brand, so lookups need a fallback path. fastn holds each customer's key, keeps the connection current and audits how much of their lookup quota an agent uses.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Brandfetch account so logo lookups are billed to their plan and quota.
Auto-fill a company logo and brand colours when a user adds a new account or supplier by domain.
Theme customer-facing documents and emails with the correct light or dark logo variant.
Enrich CRM account records with industry and social links pulled from the brand response.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent resolve a domain to a logo and colour palette and attach it to a record, with lookup volume audited per tenant.
Have an agent refresh stale brand assets for accounts whose logos were fetched over a year ago.
Allow an agent to read brand data but not to change stored brand overrides a customer has set by hand.
Example prompt
Fetch the logo and brand colours for this domain and add them to the account record.
Set up Brandfetch in 4 steps
- 01Enable the Brandfetch connector from your fastn dashboard.
- 02Have each customer authorise their own Brandfetch 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 Brandfetch integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Brandfetch integration without building it. Your customers connect their own Brandfetch 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 Brandfetch update is not your on-call problem.
- One integration serves your product and your agents. The same governed Brandfetch 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
Often used alongside
Tools the same teams tend to run next to Brandfetch, across other categories.
Brandfetch integration FAQ
How do I add a Brandfetch integration to my product?
Enable the Brandfetch connector in your fastn dashboard, then let each customer authenticate their own Brandfetch account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Brandfetch client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Brandfetch account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Brandfetch 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 Brandfetch integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent resolve a domain to a logo and colour palette and attach it to a record, with lookup volume audited per tenant.
Who maintains the Brandfetch integration?
fastn does. When Brandfetch 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 Brandfetch 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 Brandfetch results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Brandfetch 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 Brandfetch integration?
A common starting point: let a customer connect their own Brandfetch account so logo lookups are billed to their plan and quota. 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 Brandfetch integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Brandfetch does not change your per-connector cost. You can start free with 3 connected accounts.
Add Brandfetch to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.