> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brandfetch.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Brandfetch returns real company logos, brand data, and brand context. It does not design, generate, or edit logos.
> To show a logo in a user interface, use the Logo API as an image URL in an <img> tag, such as https://cdn.brandfetch.io/domain/{domain}?c={CLIENT_ID}. The client ID is public and belongs in frontend code. Never download, proxy, re-host, or optimize these images on a server, because requests that look programmatic are redirected with automated_traffic. In Next.js, this means next/image needs a custom loader or the unoptimized prop.
> To turn a company name that a user types into a domain, use the Brand Search API with the same client ID, and keep only the domain the user picks.
> For colors, fonts, downloadable logo files, and company data as JSON, call the Brand API from a server with the header Authorization: Bearer {API_KEY}, reading the key from an environment variable and never exposing it to the browser. Prefer typed routes such as /v2/brands/domain/{domain} and /v2/brands/ticker/{ticker} over the auto-detect route /v2/brands/{identifier}.
> Use the Brand Context API for a written summary of what a company does, who it sells to, and how it sounds, and the Transaction API to identify the merchant behind a card or bank transaction label.
> When a request fails, branch on the x-bf-error header code rather than on the status code or the message text. Every code, and what to do about it, is listed at https://docs.brandfetch.com/concepts/errors.
> Requests for brandfetch.com are free on the Brand API and Brand Context API, so use that domain in tests and examples.
> Brand API responses can be cached for up to 30 days, while Logo API images must be hotlinked rather than stored and Brand Search results must not be stored at all. See https://docs.brandfetch.com/concepts/caching.
> If the user has no credentials yet, https://brandfetch.com/auth.md explains how they get a client ID and an API key. An agent without an account can pay $0.10 per Brand API, Brand Context API, or Transaction API request with x402 or MPP, as described at https://docs.brandfetch.com/agents/pay-per-request.

# Limits and billing

> Free allowances, quotas, throughput limits, and overage for every Brandfetch API

Brandfetch has two kinds of products. The Logo API and Brand Search API are free and have generous monthly allowances. The Brand API, Brand Context API, and Transaction API share one paid quota, counted in **brand fetches**.

## At a glance

| Product | Free plan | Paid plans | Credential | Overage |
| - | - | - | - | - |
| Logo API | 1,000,000 requests / month | 5M to 20M requests / month | Client ID | No |
| Brand Search API | 500,000 requests / month | 1M to 5M requests / month | Client ID | No |
| Brand API | 100 brand fetches, one-time | Plan quota, shared | API key | Yes |
| Brand Context API | Shared with Brand API | Plan quota, shared | API key | Yes |
| Transaction API | Shared with Brand API | Plan quota, shared | API key | Yes |

Plan volumes and prices are on the [pricing page](https://brandfetch.com/developers/pricing).

## Brand fetches

One request to the Brand API, Brand Context API, or Transaction API is one brand fetch, drawn from a single shared balance. A brand fetch is counted when we looked the brand up. On the Brand API that means a `200`, a `304`, or a `404`, and on the Transaction API a `200` or a `404`. On the Brand Context API, only a returned context is counted, and no error response is charged.

Errors on our side and rate-limit refusals are never counted, and neither are these:

* Requests for `brandfetch.com` on the Brand API and Brand Context API, so you can test without spending quota.
* `HEAD` [prefetch](https://docs.brandfetch.com/concepts/real-time-indexing.md#prefetch-with-head) requests.
* `204` answers to [`cachedOnly`](https://docs.brandfetch.com/concepts/real-time-indexing#skip-the-crawl-with-cachedonly) requests.
* Images and screenshots linked from a Brand API response.

A [batch](https://docs.brandfetch.com/brand-api/batch.md) counts one brand fetch per identifier answered `200`.

Every response to a request made with an API key carries your plan quota in `x-api-key-quota` and your usage this month in `x-api-key-approximate-usage`. We email you at 80% of your quota.

## Overage

On a paid plan, brand fetches beyond your quota are billed at the overage rate, up to the spending limit you set in the [dashboard](https://developers.brandfetch.com/dashboard/billing). Once that limit is reached, or when it is set to \$0, requests draw on any [prepaid credits](https://docs.brandfetch.com/agents/overview.md#standing-access) you hold. When those run out, requests are refused with `429` and `x-bf-error: quota_exceeded` until the quota resets.

Overage is not available on the free plan, and it does not apply to the Logo API or Brand Search API.

## Free allowances

The Logo API and Brand Search API allowances are soft limits, so going over does not block you straight away. On the Logo API, we email you as you get close. Traffic far beyond the allowance can eventually be refused with `429` and `x-bf-error: quota_exceeded`.

Brand Search usage counts every `GET` answered `2xx` or `3xx`, including answers from the edge cache. Browser preflight requests, refused requests, and requests without a valid client ID are not counted.

## Throughput limits

Throughput limits protect the service from bursts. They are separate from your monthly quota.

| Product | Limit |
| - | - |
| Logo API | 1,000 requests per 5 minutes per IP, and 2,400 per 5 minutes per customer |
| Brand Search API | 200 requests per 5 minutes per IP, and 6,000 per 5 minutes per client ID |
| Brand API, Brand Context API | 100 requests per second sustained, with bursts up to 30,000 per rolling 5 minutes |

A throughput block returns `429`. Most carry no `x-bf-error` header, which is how you tell them apart from a quota refusal. The Brand Search per-client limit is the exception and sends `x-bf-error: rate_limited`. For search-as-you-type, debounce keystrokes to stay under both limits.

If you need more throughput, [talk to sales](https://brandfetch.com/developers/contact/sales).

## Paying per request

Agents without an account can pay for each Brand API, Brand Context API, or Transaction API request with x402 or MPP. A paid request costs \$0.10 and does not touch any quota. See [pay per request](https://docs.brandfetch.com/agents/pay-per-request.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.