Skip to main content
Logo.dev meters the Logo.dev CDN and the Logo.dev API separately. CDN requests draw on a monthly allowance. Requests to the API spend API credits, and lookups and search also have per-minute limits. The pricing page lists the allowance, the API credit grant, and the limits for each plan. We email you before you reach a monthly limit.

​
Logo.dev CDN limits

Every request to img.logo.dev counts as one CDN request, whatever it returns. On the Community plan, the monthly allowance is a hard cap. Past it, requests return 429 until the allowance resets at the start of the next month, or until you upgrade. The Community plan also has a per-minute limit for the account and for each IP address. The IP limit is shared by every Community key used from that address. Over either limit, the response is 429 with a Retry-After header that gives the seconds to wait. On paid plans, the CDN has no per-minute limit, and the monthly allowance is soft. Your logos keep loading if you go over, and we ask about a higher plan if it becomes a pattern. We never move you to a higher plan or bill you automatically. Fair use still applies on every plan. If logos stop loading and we have not emailed you, a limit is not the cause. See troubleshooting.

​
API credits

Requests to the Logo.dev API spend API credits. See API credits for what each request costs, what is billed, and what happens when you run out.

​
Logo.dev API rate limits

The API has separate pools of limits for lookups, search, and flags. Pro, Enterprise, and custom contracts get higher lookup and search limits than the other plans. Every key on the account draws on the same pools. For a team key, the team is the account. Logo.dev MCP tool calls draw on the same limits as REST requests. Flags (POST /v2/flag and the MCP flag tool) are limited to 10 requests per minute per account. Other routes are not rate limited, but each plan caps how many subscriptions and webhook endpoints you can have. Brand and image lookups share two limits: requests per minute, and requests open at the same time. Every identifier type draws on the same limits.

​
Search rate limit

Search has its own per-minute limit, separate from the lookup limits. It applies to GET /v2/search, the deprecated v1 GET /search, and the MCP search tool. Search has no limit on open requests. A search refused for the rate limit is not billed.

​
Handle a 429

Every lookup and search response, including a 429, reports your per-minute window in the RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers. A search response reports the search window. See response headers. Over a limit, the response is 429 with the code rate_limited. To recover:
  • If RateLimit-Remaining is 0, you reached the per-minute limit. Wait RateLimit-Reset seconds, then retry.
  • Otherwise, you have too many lookups open. Send fewer requests in parallel, and retry with exponential backoff and jitter.

​
FAQs

Your dashboard shows your CDN requests and your API credit balance. On the API, the Credits-Remaining and RateLimit-Remaining headers report your balance and your window on each lookup and search.
On a paid plan, your logos keep loading, though it’s a sign to upgrade. On the Community plan, the cap is firm, and requests stop until the next month’s reset.
For custom limits or higher volumes, contact us.