> ## 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.

# Identifiers

> The inputs Brandfetch can resolve to a brand, and which API accepts each one

Every Brandfetch request starts with something that points at a company: a domain, a stock ticker, a name someone typed, or a line on a bank statement. Brandfetch resolves that input to one brand and returns its data.

## Which API accepts what

The table shows which identifiers the Logo API, Brand API, and Brand Context API accept.

| Identifier | Example | [Logo](https://docs.brandfetch.com/logo-api/overview.md) | [Brand](https://docs.brandfetch.com/brand-api/overview.md) | [Context](https://docs.brandfetch.com/brand-context-api/overview.md) |
| - | - | :-: | :-: | :-: |
| Domain | `nike.com` | ✓ | ✓ | ✓ |
| Website URL | `nike.com/running` | | ✓ | ✓ |
| Email address | `jane@example.com` | | ✓ | ✓ |
| Brand ID | `id_0dwKPKT` | ✓ | ✓ | |
| Stock or ETF ticker | `NKE` | ✓ | ✓ | |
| ISIN | `US6541061031` | ✓ | ✓ | |
| Crypto symbol | `BTC` | ✓ | ✓ | |

Two other inputs go through their own APIs instead. A company name such as `Nike` goes to the [Brand Search API](https://docs.brandfetch.com/brand-search-api/overview.md), which finds its domain so you can use the domain everywhere else, and a card or bank transaction label such as `NIKE STORE 0423 NEW YORK` goes to the [Transaction API](https://docs.brandfetch.com/transaction-api/overview.md), which returns the merchant's brand.

## Domain

The domain is the most reliable identifier. A company has one registrable domain, and Brandfetch can index any live domain, including companies nobody has asked about before. See [real-time indexing](https://docs.brandfetch.com/concepts/real-time-indexing.md).

## Website URL and email address

A URL resolves to the registrable domain of its host, and an email address resolves to the registrable domain of the part after the `@`. `https://www.brandfetch.com/developers/pricing` and `john@example.brandfetch.com` both return the same brand as `brandfetch.com`.

Brandfetch does not store the URL or the address. Your request logs show only the resolved domain. URLs and email addresses work on the shorthand route (`/v2/brands/{identifier}`), not on typed routes.

## Brand ID

Every brand has a Brand ID such as `id_0dwKPKT`. The Brand API returns it as `id`. Store it next to your own records so you can fetch the same brand later without resolving the domain again.

## Ticker, ISIN, and crypto symbol

Financial identifiers resolve to the company or asset behind them. Tickers cover stocks and ETFs, ISINs cover securities, and crypto symbols cover tokens such as `BTC` and `ETH`.

## Typed routes and auto-detection

The Logo API and Brand API accept a typed route, `{type}/{identifier}`, which states what the identifier is:

```bash theme={null}
https://api.brandfetch.io/v2/brands/domain/nike.com
https://api.brandfetch.io/v2/brands/ticker/NKE
https://api.brandfetch.io/v2/brands/isin/US6541061031
https://api.brandfetch.io/v2/brands/crypto/BTC
```

Without a type, the API guesses in this order: domain, ticker, ISIN, crypto. A string that is valid as more than one type can resolve to the wrong brand, so use typed routes in production.


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