Skip to main content
The short version
  • API credits pay for the Logo.dev API (api.logo.dev) and the Logo.dev MCP.
  • The Logo.dev CDN (img.logo.dev) never uses API credits. It counts requests against your plan’s monthly CDN allowance.
  • Each request costs a set number of credits. See what each request costs.
  • With webhooks, you spend credits only on brands that changed, not on refreshing your whole list.
  • Every plan includes API credits each month. Pro and Enterprise can buy more.
  • When you run out, API requests return 402. We never bill for overage.

​
What each request costs

​
What is billed

  • Brand, brandmark, and logo requests are billed once per brand domain, per route, per 24 hours.
  • A brand that is found is billed, even if it has no image of the kind you asked for.
  • A brand that isn’t found (404) or is still being indexed (202) is not billed, and neither are retries.
  • Search is billed on every request, including searches that find nothing. A search refused for the rate limit (429) is not billed.
  • Webhook endpoints, subscriptions, events, and downloads from the temporary image URLs in API responses are not billed. Those downloads don’t count as CDN requests either.

​
Webhooks and credits

Webhooks are on paid plans. You choose which brands to follow, up to your plan’s limit. When a brand you follow changes, its brand.updated event lists what changed in changed_attributes. You decide what to request, and only that request spends credits: This costs far less than refreshing your whole list on a schedule. Refreshing 10,000 stored logos every month costs 20,000 credits a month. With webhooks, you spend 2 credits only when one of those logos changes.

​
Included and purchased credits

Every plan includes API credits each month. The pricing page lists how many. Included credits renew on your billing date and don’t roll over. On Pro, Enterprise, or a custom contract, the account owner can buy more on the billing page, at $10 per 1,000 credits, starting at $5. Purchased credits never expire. Auto-reload can buy more when your balance runs low. Community and Startup need to upgrade to Pro to buy credits.

​
When you run out

The API returns 402 with the code insufficient_credits, and the MCP returns a tool error. Requests work again when your included credits renew or you buy more. See out of API credits. The Logo.dev CDN isn’t affected, and we never bill for overage.

​
FAQs

Multiply your expected requests by each route’s cost. For example:
  • Brand data for 2,000 new signups a month: 2,000 × 5 = 10,000 credits a month.
  • Logos for 10,000 companies: 10,000 × 2 = 20,000 credits once.
  • Name autocomplete with 200,000 searches a month: 200 credits a month.
Repeats within 24 hours are free, so real usage is usually lower.
Yes. They are different routes, and each route is billed once per brand domain per 24 hours.
The dashboard shows it. REST lookups and searches also return a Credits-Remaining header with your balance when it is known. Credits-Charged is 1 when a request spent credits and 0 when it was free. It is not the amount. See response headers.
Your plan’s included credits, then purchased credits.
Yes. Each MCP tool costs the same as its REST route, under the same rules. Each tool bills to your team, or to your personal account if you have no team. MCP tools return no credit headers, so check the dashboard.
Yes. A team shares one API credit balance, and only the owner can buy credits.
No. The Logo.dev API rejects publishable keys. Use a secret key on your server. See API keys.
Not during the beta. Each person gets 1,000 requests per UTC day. See Transaction API.
Yes. GET /search is billed like GET /v2/search.