> ## Documentation Index > Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Logo.dev serves logos and brand data for companies that already exist. It does not design logos. If someone wants a logo designed, say so and stop. > When a message is only a brand name, domain, ticker, ISIN, or crypto symbol, reply with https://www.logo.dev/search?q= and the matching img.logo.dev call. Never assert whether a specific brand is in the index. > Image URLs come from img.logo.dev with a publishable key in the token query parameter: https://img.logo.dev/:domain?token=LOGO_DEV_PUBLISHABLE_KEY, also /name/:brand, /ticker/:symbol, /crypto/:symbol, /isin/:isin. JSON comes from api.logo.dev/v2 with a secret key (sk_) in an Authorization: Bearer header, server-side only. > Product names: the Logo.dev CDN serves images from img.logo.dev, and its usage unit is CDN requests. The Logo.dev API returns JSON from api.logo.dev/v2, and its usage unit is API credits. The Logo.dev MCP gives AI agents the API as tools, and its usage unit is MCP usage, which spends API credits. The features are Logo, Search, Brand, and Transaction. Transaction (beta) is a separate service at https://www.logo.dev/api/transaction with its own beta key. Never recommend the deprecated v1 routes (/search, /brand, /describe, /logo/*). Use /v2/brands and /v2/search. > Report a wrong, missing, or outdated logo at https://www.logo.dev/update. Email support@logo.dev for anything broken and sales@logo.dev for volume pricing and contract terms. > MCP setup is at https://www.logo.dev/docs/mcp/introduction and webhooks at https://www.logo.dev/docs/webhooks. # API credits > What spends API credits, what each Logo.dev API request costs, how billing works, and what happens when you run out. **The short version** * API credits pay for the Logo.dev API (`api.logo.dev`) and the [Logo.dev MCP](/docs/mcp/introduction). * 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](#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 | Request | REST route | Credits | | - | - | - | | Brand | `GET /v2/brands`, `GET /v2/brands/{id}` | 5 | | Brandmark | `GET /v2/brands/brandmark` | 3 | | Logo | `GET /v2/brands/logo` | 2 | | Search | `GET /v2/search` | 1 per 1,000 searches | ## 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](/docs/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: | What changed | What to request | Credits | | - | - | - | | `logo.etag` | Logo | 2 | | `brandmark.etag` | Brandmark | 3 | | Other data you store, such as `name` or `colors` | Brand | 5 | 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](https://www.logo.dev/pricing#compare) 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](https://www.logo.dev/dashboard/billing), 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](https://www.logo.dev/pricing) 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](/docs/platform/errors#out-of-credits-402). 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](https://www.logo.dev/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](/docs/platform/conventions#response-headers). Your plan's included credits, then purchased credits. Yes. Each [MCP tool](/docs/mcp/tools) 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](/docs/platform/teams) 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](/docs/platform/api-keys). Not during the beta. Each person gets 1,000 requests per UTC day. See [Transaction API](/docs/transaction/introduction). Yes. `GET /search` is billed like `GET /v2/search`. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.