Skip to content

Coverage

Most brand APIs advertise a library size — “50M+ logos” — which tells you nothing about whether your domains are covered. We publish measured hit rates instead, and you can check them yourself.

Try the coverage endpoint api.anylogo.dev/coverage

GET https://api.anylogo.dev/coverage
{
"segments": [
{ "segment": "Top 100 sites", "sampled": 120, "logoRate": 0.68, "vectorRate": 0.19 }
]
}
  • logoRate — share of sampled domains that returned a logo.
  • vectorRate — share that returned a scalable vector rather than a raster.

We sample real domains and request each one exactly as you would. No cherry-picking, no excluding domains that fail.

Segments matter more than a single headline number. Traffic-ranked lists are dominated by infrastructure hosts — CDN endpoints, DNS servers, API domains like gstatic.com or akamai.net — which have no logo because they aren’t brands. Coverage on those is low and always will be, which is why we report companies separately rather than blending them into one flattering average.

Coverage is not 100%, and we’d rather say so than imply otherwise. A handful of companies host their brand assets behind authentication, which puts them out of reach for any provider. Some sites publish no usable mark at all.

One result worth noting: our coverage is strongest on long-tail domains and weakest on the highest-traffic ones. That inverts the usual pattern. Providers with pre-built libraries index popular sites first and thin out as you go down the list; we fetch on demand, so obscurity costs us nothing — but the largest sites deploy the heaviest automated-request protection. When we can’t find a logo you have options — fallback=monogram returns a lettered tile so your interface never breaks, and a missing domain is fetched fresh the first time anyone asks for it, so coverage improves with use.

If a domain you need is missing, request it once and it enters the index.