Skip to content
J·BJon BishopFractional growth marketer

Marketing · llms.txt file breakdown

Brandfetch llms.txt

A directly retrieved Markdown index for Brandfetch's documentation, with 65 links across 2 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Complete saved Markdown shown below.

# Brandfetch

- [Getting started](https://docs.brandfetch.com/get-started.md): The brand layer for products and AI agents
- [Explore dataset](https://docs.brandfetch.com/playground/index.md): Try the Brandfetch APIs interactively in the Playground.
- [Overview](https://docs.brandfetch.com/logo-api/overview.md): Instantly add any company logos to your app or website
- [Parameters](https://docs.brandfetch.com/logo-api/parameters.md): Detailed reference of all Logo API parameters
- [Brand API](https://docs.brandfetch.com/brand-api/overview.md): The brand layer for modern products
- [Brand Context API](https://docs.brandfetch.com/brand-context-api/overview.md): Brand context built for AI agents
- [Brand Search API](https://docs.brandfetch.com/brand-search-api/overview.md): Match brand names to their domain and logo
- [Overview](https://docs.brandfetch.com/transaction-api/overview.md): Turn payment transactions into merchant data
- [Brandfetch MCP](https://docs.brandfetch.com/mcp/overview.md): Connect Brandfetch to AI assistants
- [Brandfetch for agents](https://docs.brandfetch.com/agents/overview.md): How an AI agent discovers Brandfetch, gets in, and pays — with or without a human in the loop
- [Pay per request](https://docs.brandfetch.com/agents/pay-per-request.md): Use the Brand API, the Brand Context API and the Transaction API without an account, one x402 or MPP payment at a time
- [Discovery](https://docs.brandfetch.com/agents/discovery.md): The machine-readable documents that let an agent find and understand Brandfetch on its own
- [Coverage and quality](https://docs.brandfetch.com/accuracy/coverage-and-quality.md)
- [Data ingestion & operationalization](https://docs.brandfetch.com/delivery-methods/data-ingestion.md)
- [REST API](https://docs.brandfetch.com/delivery-methods/rest-api.md): Fetch brand data on demand over HTTPS with a simple, typed REST interface.
- [Overview](https://docs.brandfetch.com/delivery-methods/webhooks/overview.md): Get notified of changes by receiving events at your webhook URL.
- [Setup a webhook](https://docs.brandfetch.com/delivery-methods/webhooks/setup.md): Start receiving event payloads
- [Delivery behaviors](https://docs.brandfetch.com/delivery-methods/webhooks/delivery-behaviors.md): This section helps you understand different behaviors to expect regarding how Brandfetch sends events to your webhook endpoint.
- [Best practices](https://docs.brandfetch.com/delivery-methods/webhooks/best-practices.md): Review these best practices to make sure your webhooks remain secure and function well with your integration.
- [Event types](https://docs.brandfetch.com/delivery-methods/webhooks/event-types.md): Overview of subscribable event types
- [GraphQL](https://docs.brandfetch.com/delivery-methods/graphql.md)
- [Getting help](https://docs.brandfetch.com/support/getting-help.md): Our support team is always available and willing to assist you.
- [Security & SOC2](https://docs.brandfetch.com/support/security-soc2.md): Our commitment to secure data handling and best-in-class practices.
- [Zero data retention](https://docs.brandfetch.com/support/zero-data-retention.md): An enterprise feature that keeps request metadata — the brands you query and the users behind the requests — out of Brandfetch's records.
- [Report inaccuracies](https://docs.brandfetch.com/support/report-inaccuracies.md): Report incorrect or missing brand info.
- [Terms and Conditions](https://docs.brandfetch.com/support/terms-and-conditions.md)
- [Service status](https://docs.brandfetch.com/support/service-status.md): Check the status of Brandfetch services.
- [Brand API by domain](https://docs.brandfetch.com/reference/brand-api-domain.md): Get brand data using a domain name. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Brand API by ticker](https://docs.brandfetch.com/reference/brand-api-ticker.md): Get brand data using a Stock or ETF ticker. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Brand API by ISIN](https://docs.brandfetch.com/reference/brand-api-isin.md): Get brand data using an ISIN code. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Brand API by crypto](https://docs.brandfetch.com/reference/brand-api-crypto.md): Get brand data using a crypto symbol. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Brand API (auto-detect)](https://docs.brandfetch.com/reference/brand-api.md): Get brand data using a Domain, Website URL, Email address, Brand ID, ISIN, Stock/ETF ticker, or Crypto symbol. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Brand API batch](https://docs.brandfetch.com/reference/brand-api-batch.md): Send up to 100 identifiers. Get one result per identifier, in the order you sent them. Each identifier is answered the way `GET /v2/brands/{identifier}` answers it.
- [Brand API prefetch (HEAD)](https://docs.brandfetch.com/reference/brand-api-prefetch.md)
- [Brand API prefetch by domain (HEAD)](https://docs.brandfetch.com/reference/brand-api-prefetch-domain.md)
- [Brand Context API](https://docs.brandfetch.com/reference/brand-context-api.md): Get a structured, narrative-rich brand context for a domain — including identity, positioning, products and services, voice, visual style, and competitors. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/…
- [Brand Search API](https://docs.brandfetch.com/reference/brand-search-api.md): Search for brands by name, login to get a clientId
- [Transaction API](https://docs.brandfetch.com/reference/transaction-api.md): Turn payment transactions into merchant data. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
- [Viewer API](https://docs.brandfetch.com/reference/viewer-api.md): Returns the identity of the credential used to authenticate the request: an API key or a user session token (JWT). Use it to verify a credential during integration setup (a `200` response means the credential is valid; `401`/`403` means it is missing, unknown, or revoked) and to display which API ke…
- [Agent access offer](https://docs.brandfetch.com/reference/agents-access-offer.md): What an agent can buy and how to pay for it: standing API access — an organization, an API key preloaded with prepaid credits and an MCP token — sold for one x402 or MPP payment. Needs no credential. Written for an agent that will act on it. See https://docs.brandfetch.com/agents/overview.
- [Buy agent access](https://docs.brandfetch.com/reference/agents-access-purchase.md): Pay a whole number of US dollars to receive a Brandfetch organization, an API key holding 20 prepaid API credits per dollar, and an MCP bearer token. One credit is one Brand API, Brand Context API or Transaction API request. Call once without a payment to receive the 402: its `PAYMENT-REQUIRED` head…
- [No-code integrations](https://docs.brandfetch.com/integrations/overview.md): Connect Brandfetch to Zapier, Make, and n8n without writing code
- [Use Brandfetch with Microsoft Excel](https://docs.brandfetch.com/integrations/microsoft-excel.md)
- [Use Brandfetch with Microsoft PowerPoint](https://docs.brandfetch.com/integrations/microsoft-powerpoint.md)
- [Use Brandfetch with Google Sheets](https://docs.brandfetch.com/integrations/google-sheets.md)
- [Use Brandfetch with Airtable](https://docs.brandfetch.com/integrations/airtable.md)
- [Firecrawl](https://docs.brandfetch.com/comparisons/firecrawl.md): How Firecrawl's branding extraction compares to Brandfetch's brand data APIs
- [Clearbit Logo API](https://docs.brandfetch.com/comparisons/clearbit.md): How Brandfetch's Logo API compares to Clearbit's discontinued Logo API
- [Logo.dev](https://docs.brandfetch.com/comparisons/logo-dev.md): How Logo.dev's Logo API compares to Brandfetch's Logo API
- [Google Favicon API](https://docs.brandfetch.com/comparisons/google-favicon-api.md): Why Google's unofficial favicon endpoint isn't a substitute for a real logo API
- [DuckDuckGo Favicon API](https://docs.brandfetch.com/comparisons/duckduckgo-favicon-api.md): Why DuckDuckGo's icon endpoint isn't a substitute for a real logo API
- [Migrating from Clearbit to Brandfetch Logo API](https://docs.brandfetch.com/guides/migrate-from-clearbit-logo-api.md): Complete guide to replacing Clearbit's deprecated Logo API with Brandfetch
- [Guide to Logo Fair use](https://docs.brandfetch.com/guides/logo-fair-use.md): Understanding fair use principles for logo usage
- [Overview](https://docs.brandfetch.com/use-cases/overview.md): Common use cases for brand data, each with a working example
- [Sales personalization](https://docs.brandfetch.com/use-cases/sales-personalization.md): Auto-brand decks, proposals, and emails with your prospect's logo and colors
- [Populate onboarding](https://docs.brandfetch.com/use-cases/populate-onboarding.md): Boost conversion and activation by personalizing your users' onboarding from their email domain
- [Company autocomplete](https://docs.brandfetch.com/use-cases/company-autocomplete.md): Find your company as you type, with a logo on every result, powered by the Brand Search API
- [Profiles & directory](https://docs.brandfetch.com/use-cases/profiles-and-directory.md): Put verified logos and brand data on every company record, in account lists, CRM contacts, job listings, and logo walls
- [Logo picker](https://docs.brandfetch.com/use-cases/logo-picker.md): Let users search a brand and drop the right logo asset into the document, powered by the Brand Search API and Brand API
- [Transaction enrichment](https://docs.brandfetch.com/use-cases/transaction-enrichment.md): Turn raw payment descriptors into clean merchant identity, category, and logo using the Transaction API
- [Stock ticker logos](https://docs.brandfetch.com/use-cases/stock-ticker-logos.md): Show company logos in stock watchlists and portfolio cards using the Logo API's ticker route
- [On-brand AI](https://docs.brandfetch.com/use-cases/on-brand-ai.md): Ground LLMs and agents with real brand context using the Brand Context API and Brandfetch MCP
- [Changelog](https://docs.brandfetch.com/changelog/overview.md): Follow along with updates across Brandfetch’s API.

## OpenAPI Specs

- [openapi](/openapi.json)


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

Measured from the saved file

Linked document

UTF-8 text size
10.8 KB11033 bytes
Token count
2534o200k_base encoding
Markdown links
6565 distinct URLs
Fenced code blocks
072 lines in the file

Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.

Project H1
Brandfetch

Context architecture

How the content is divided

1 H2 sections organize 65 parsed Markdown links. 63 links point to .md or .markdown paths; 1 link occurrences use another hostname. Linked destinations have not been recursively validated.

H2 sectionLinksUTF-8 bytesTokens
OpenAPI SpecsLine 67214133

Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.

Embedded material

Code, installation and API examples

Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels

Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.

Publisher prioritization

The Optional section

No H2 section named “Optional” was detected in this file.

The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.

Machine-readable routes

MCP references and configuration text

MCP-related text was detected in the captured file. 1 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.

These are text and link observations. No MCP server connection, authentication or tool call was tested.

Index and bundle

llms-full.txt companion

Verified text companion

Text companion verified

https://docs.brandfetch.com/llms-full.txt ↗
Discovery
Conventional sibling path checked
HTTP response
200 · text/plain; charset=utf-8
Text size
421.0 KB · 431106 bytes (measured)
Token count
102903 o200k_base tokens
Retrieval scope
Complete body retrieved

A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.

Change evidence

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

1 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.

File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.

Capture identity and measurement method
Requested endpoint
https://docs.brandfetch.com/llms.txt
Final endpoint
https://docs.brandfetch.com/llms.txt
HTTP status
200
Content type
text/plain; charset=utf-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
3e3bb1e7c2a8440019be4aae6a1e5b77f5072810fe041c3b1a372d8dea404249

Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.

Related tools and resources

Contact Jon