Credits, rate limits and caching
How each brand API counts a request, how fast you can call it and what you may store. These details decide your bill more than the headline price does.
Last updated 2026-11-10
The price on a pricing page is a monthly allowance. What you pay depends on how each call is counted, what happens past the allowance, and whether you may store results instead of asking again.
| Product | How a call is counted | Past the allowance | What you may store |
|---|---|---|---|
| Brandfetch | One brand fetch per Brand API call | $0.10 a fetch, up to a cap you set | Brand API data for 30 days |
| Logo.dev | 5 credits a brand lookup, once per domain per 24 hours | No overage; buy more credits | API results, on any plan |
| Context.dev | 10 credits a lookup; free when nothing is found | Credit blocks bought automatically | Not Logo Link images |
| LogoKit | Requests a day | 429 Too Many Requests | Only on Enterprise, refreshed within 30 days |
| Hunter | Not counted; fair use | Contact Hunter above 200,000 a day | Caching encouraged |
| Rainbrand | 100 credits a Brief, 200 a Review, 300 an edit, 500 a new brand | Top-ups or automatic top-ups | Not published |
DAMs are priced by plan, not by request; their rate limits are on each entry.
What are the rate limits?
Most providers answer with HTTP 429 when you go too fast; wait and retry. The published limits differ a lot: Brandfetch allows a sustained 100 requests a second, Logo.dev's API 100 a minute on its lower plans, Rainbrand 120 accepted requests per key, and Context.dev limits how many requests run at once. Each entry lists its own.
Three things that change the bill
- Repeat lookups. Logo.dev bills a domain once per 24 hours; elsewhere, store what you are allowed to store.
- Misses. Context.dev doesn't charge for a lookup that finds nothing, and Logo.dev doesn't charge for a 404.
- Image URLs. Logo images loaded through an image URL count against a separate, larger allowance at Brandfetch, Logo.dev and Context.dev.