Comparison
Compare brand APIs
Most brand APIs look a domain up in an index they built ahead of time. We read the live site when you ask, and charge $0.01 per successful call. Here is how that compares, and when the other kind is the better choice.
Updated September 23, 2026
Two kinds of brand API
Brandfetch and Logo.dev each hold an index: brands collected ahead of time and looked up when you ask. Because the work is already done, an index can answer for a company whose site blocks bots. Both sell subscriptions with free tiers. Context.dev also sells a subscription, tiered by credits.
We do the other thing. We read the live site when you ask, so what comes back is the brand as the site shows it now, or from our cache of it, which we refresh after a week. We charge $0.01 for each successful call, paid up front as credits that never expire, and an error costs nothing. There is no subscription.
An index wins on reach. A site that turns away automated requests still resolves for an index, while from us it comes back thinner, or as a blocked error you are not charged for. A live fetch wins when you want the brand as it is now and would rather pay per call than for a plan.
JupiterFetch vs Brandfetch
Brandfetch is the established product in this category and covers more domains than we do. What each of us returns, how each charges, and when to choose them instead.
Read the Brandfetch comparison
Replacing the Clearbit Logo API
Clearbit's free Logo API shut down in December 2025. What we return in its place, why it is not a URL swap, and when Logo.dev is the closer fit.
Read the Clearbit replacement guide
JupiterFetch vs Firecrawl
Firecrawl reads the whole web, and its branding format is one output of its scrape endpoint. What each of us returns, how each charges, and when to choose Firecrawl.
Read the Firecrawl comparison