Skip to main content
Brandfetch is built to be used by software that acts on its own: coding assistants, research agents, commerce and personalization pipelines. This section is the map. It covers the ways in, what an agent with a wallet but no account can do, and the machine-readable documents Brandfetch publishes so that an agent can find all of this by itself.

​
Three ways in

MCP server

Tools for brand search, brand data, brand context, transaction enrichment and logo URLs. OAuth, or a bearer token.

REST API with an API key

Every API over HTTPS. The key comes from a developer account and is metered against its quota.

Pay per request

No account. Send the request bare, receive a 402 with a price, pay it in USDC with x402 or over MPP through Stripe, and get the data.

​
Which one to pick

Everything an API key can do, a paid-per-request call can do too, with one exception: pay-per-request covers the Brand API and the Brand Context API. The Brand Search API is free and needs no credential at all.

​
Standing access

POST /v2/agents/access?usd=N sells standing access for a single payment of N whole US dollars, between 1and1 and 500 — USDC over x402, or over MPP with USDC.e on Tempo or a card. The payer receives:
  • an organization it owns, created on its first purchase,
  • an API key holding 20 prepaid credits per dollar paid — one credit is one Brand API or Brand Context API request,
  • a bearer token for the MCP server.
Paying again from the same wallet adds credits to the same key; a card names no wallet, so each card payment buys its own key. GET /v2/agents/access describes the offer in a form an agent can act on. The full contract is in the reference: the offer and the purchase; the payment mechanics are the same as for paying per request.

​
Discovery

An agent that has never heard of Brandfetch can find all of the above from brandfetch.com: an llms.txt, an API catalog, an MCP server card, OAuth metadata and an agent skill, all under the standard well-known locations. Discovery lists every document and what it is for.

​
What the data looks like

  • The Brand API returns logos, colors, fonts, images and company details as JSON, for a domain, ticker, ISIN, crypto symbol or brand ID.
  • The Brand Context API returns a narrative brand profile for grounding a model, as JSON or, with Accept: text/markdown, as Markdown ready to drop into a prompt.
  • The Logo API serves logos from a CDN by URL, without a request to the REST API.