Skip to main content
Brandfetch uses two credentials. A client ID identifies your app on public requests that run in the browser, and an API key authorizes server-side requests that return brand data. Both live in the developer dashboard and are created with a free account.

Client ID

The client ID is a public identifier, so it is fine to ship it in HTML, mobile apps, and frontend code. It tells us which app made the request, which is how free usage is counted and kept fair.
A request without a client ID is refused. Logo API images must also be embedded directly, not downloaded by a script; the Logo API usage guidelines explain why.

API key

The API key is a secret. Keep it on your server, in an environment variable, and send it as a bearer token:
Requests for brandfetch.com are free on the Brand API, so you can build and test an integration without spending your quota. Image URLs inside a Brand API response already carry a client ID signed for your key. Use them exactly as returned.

MCP server

The Brandfetch MCP server signs you in with OAuth when you add it to Claude, Cursor, or another MCP client. For clients without OAuth, or for scripts and CI, create an MCP token in the Keys and MCP section of the dashboard and send it as Authorization: Bearer <token>.

Without an account

An agent that has no account can still call the Brand API, Brand Context API, and Transaction API. A request without a credential is answered 402 Payment Required with a price, and the agent pays it in USDC over x402 or through MPP. Pay per request covers the flow, and standing access turns one payment into an API key with prepaid credits.