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

# Discovery

> The machine-readable documents that let an agent find and understand Brandfetch on its own

Brandfetch publishes the standard discovery documents at their well-known locations, so that an agent, a crawler or an assistant can learn what exists, how to authenticate and where the APIs are without a person reading this site for it. Every document below is live and cacheable, needs no credential, and is served with permissive CORS.

## Documents

| What                                                                                                                           | URL                                                                                                                                                                                                             | Standard                                                         |
| ------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Overview for language models, including agent instructions and per-client MCP setup recipes                                    | [`brandfetch.com/llms.txt`](https://brandfetch.com/llms.txt)                                                                                                                                                    | [llms.txt](https://llmstxt.org)                                  |
| How to obtain credentials: OAuth for the MCP server, dashboard-issued keys and tokens, revocation                              | [`brandfetch.com/auth.md`](https://brandfetch.com/auth.md)                                                                                                                                                      | auth.md convention                                               |
| An agent skill that walks through picking an API, getting credentials and calling REST or MCP                                  | [`brandfetch.com/agent-onboarding/SKILL.md`](https://brandfetch.com/agent-onboarding/SKILL.md), indexed at [`/.well-known/agent-skills/index.json`](https://brandfetch.com/.well-known/agent-skills/index.json) | Agent Skills                                                     |
| Catalog of the APIs, each linked to its OpenAPI description, documentation and status page                                     | [`brandfetch.com/.well-known/api-catalog`](https://brandfetch.com/.well-known/api-catalog)                                                                                                                      | [RFC 9727](https://www.rfc-editor.org/rfc/rfc9727)               |
| Agent Resource Discovery manifest: the MCP server and its tools, the APIs, the skill and the docs, with representative queries | [`brandfetch.com/.well-known/ard.json`](https://brandfetch.com/.well-known/ard.json) (also served as `ai-catalog.json`)                                                                                         | ARD 1.0                                                          |
| MCP server card: the server's name, version, transport and repository                                                          | [`brandfetch.com/.well-known/mcp/server-card.json`](https://brandfetch.com/.well-known/mcp/server-card.json)                                                                                                    | MCP server card                                                  |
| OAuth protected resource metadata naming the authorization server and supported scopes                                         | [`brandfetch.com/.well-known/oauth-protected-resource`](https://brandfetch.com/.well-known/oauth-protected-resource)                                                                                            | [RFC 9728](https://www.rfc-editor.org/rfc/rfc9728)               |
| OAuth authorization server metadata: authorization, token and dynamic registration endpoints, PKCE                             | [`developers.brandfetch.com/.well-known/oauth-authorization-server`](https://developers.brandfetch.com/.well-known/oauth-authorization-server)                                                                  | [RFC 8414](https://www.rfc-editor.org/rfc/rfc8414)               |
| The OpenAPI description of the REST API, with each paid operation's MPP terms in `x-payment-info`                              | [`docs.brandfetch.com/openapi.json`](https://docs.brandfetch.com/openapi.json); `api.brandfetch.io/openapi.json` and `brandfetch.com/openapi.json` lead there too                                               | OpenAPI 3.0, [MPP discovery](https://mpp.dev/advanced/discovery) |

## Hints in every response

Pages on `brandfetch.com` carry an HTTP `Link` header pointing at the API catalog (`rel="api-catalog"`), the OpenAPI description (`rel="service-desc"`), this documentation (`rel="service-doc"`) and `llms.txt` (`rel="describedby"`), so a client that fetches any page learns where the rest is. Append `.md` to a page's path, `https://brandfetch.com/pricing.md` for example, to receive it as Markdown.

`robots.txt` declares the site's content signals, `search=yes, ai-input=yes, ai-train=no`: indexing and use as model input are welcome, training is not.

## Paying without an account

The Brand API and the Brand Context API describe their own price to anyone who asks without a credential: the `402` they answer with carries an [x402](https://x402.org) challenge and [MPP](https://mpp.dev) challenges in `WWW-Authenticate`. The [OpenAPI description](https://docs.brandfetch.com/openapi.json) states each paid operation's terms in MPP's `x-payment-info` extension (and the service in `x-service-info`), and the payment routes declare themselves to x402 discovery services. [Pay per request](/agents/pay-per-request) explains the flow; [standing access](/agents/overview#standing-access) is the same payment buying a prepaid API key.