> ## 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.
# Brandfetch for agents
> How an AI agent discovers Brandfetch, gets in, and pays — with or without a human in the loop
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
Tools for brand search, brand data, brand context, transaction enrichment and logo URLs. OAuth, or a bearer token.
Every API over HTTPS. The key comes from a developer account and is metered against its quota.
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
| Situation | Use |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| A person is present, or the agent runs inside an assistant such as Claude, Cursor or Codex | The [MCP server](/mcp/overview), signed in with OAuth |
| The agent is deployed by a team that has a Brandfetch account | An [API key](/brand-api/overview) from the developer dashboard, as `Authorization: Bearer ` |
| Nobody is around to sign up, and the agent makes a handful of requests | [Pay per request](/agents/pay-per-request): one x402 or MPP payment per call, no state to keep |
| Nobody is around to sign up, and the agent makes many requests | [Standing access](#standing-access): one x402 or MPP payment buys an API key with prepaid credits |
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 $1 and $500 — USDC over x402, or over [MPP](https://mpp.dev) 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](/mcp/overview).
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](/reference/agents-access-offer) and [the purchase](/reference/agents-access-purchase); the payment mechanics are the same as for [paying per request](/agents/pay-per-request#standing-access).
## 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](/agents/discovery) lists every document and what it is for.
## What the data looks like
* The [Brand API](/brand-api/overview) returns logos, colors, fonts, images and company details as JSON, for a domain, ticker, ISIN, crypto symbol or brand ID.
* The [Brand Context API](/brand-context-api/overview) 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](/logo-api/overview) serves logos from a CDN by URL, without a request to the REST API.