> ## 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. # Brand Context API > Get a structured, narrative-rich brand context for a domain — including identity, positioning, voice, and visual style. Authenticate with an API key sent as `Authorization: Bearer `, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request. ## OpenAPI ````yaml GET /v2/context/{domain} openapi: 3.0.1 info: title: Brandfetch API description: >- Our APIs help you personalize your customer journey through unique branded experiences. license: name: MIT version: 1.0.0 contact: name: Brandfetch Support url: https://brandfetch.com email: support@brandfetch.io servers: - url: https://api.brandfetch.io security: [] paths: /v2/context/{domain}: get: tags: - context summary: Get brand context by domain description: >- Get a structured, narrative-rich brand context for a domain — including identity, positioning, voice, and visual style. Authenticate with an API key sent as `Authorization: Bearer `, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request. operationId: getBrandContext parameters: - name: domain in: path description: >- Domain name (`brandfetch.com`), a website URL on the domain (`https://www.brandfetch.com/developers/pricing`), or an email address on the domain (`john@example.brandfetch.com`). The API resolves a website URL or an email address to its registrable domain before the lookup. It does not store the URL or the address. Your request logs show only the domain. A URL whose host is not a domain name returns `400`. A malformed address also returns `400`. The API does not bill these requests. required: true schema: type: string examples: domain: summary: Domain value: brandfetch.com email: summary: Email address value: john@example.brandfetch.com url: summary: Website URL value: https://www.brandfetch.com/developers/pricing - name: cachedOnly in: query description: >- When `true`, return a brand context only if one is already cached, responding instantly without crawling the domain. If no cached context exists, the API responds with `204 No Content` instead of resolving the domain live (which can take several seconds). Useful for latency-sensitive use cases. Any value other than `true` (including omitting the parameter) keeps the default behaviour of resolving the domain live on a cache miss. Defaults to `false`. required: false schema: type: boolean default: false examples: cachedOnly: summary: Cached only (skip crawling) value: true responses: '200': headers: PAYMENT-RESPONSE: description: >- Present on responses paid with x402: the base64-encoded settlement receipt (`success`, `transaction`, `network`, `payer`). schema: type: string Payment-Receipt: description: >- Present on responses paid with MPP: the base64url-encoded receipt (`method`, `reference`, `status`, `timestamp`). Such responses also carry `Cache-Control: private`. schema: type: string description: >- Successful request. The response format is determined by the `Accept` header: `application/json` returns a structured JSON object, while `text/markdown` returns the brand context as Markdown. A request paid with MPP whose response was lost can be retried with the same credential for two minutes: it is served from the payment already taken and not charged again. content: application/json: schema: $ref: '#/components/schemas/BrandContextResponse' text/markdown: schema: type: string description: The brand context rendered as Markdown. '204': description: >- Returned when `cachedOnly=true` and no brand context is currently cached for the domain. The response body is empty. Because crawling is disabled there is nothing to return. Retry without `cachedOnly` to resolve the domain live. '400': description: Bad Request content: application/json: schema: type: object properties: message: type: string enum: - Bad Request '401': description: >- Unauthorized. Returned when the `Authorization` header is present but malformed. A request with no credential at all receives a `402` with a payment challenge instead. content: application/json: schema: type: object properties: message: type: string enum: - Unauthorized '402': description: >- Payment required. Returned when the request carries no credential: no API key, no x402 payment, no MPP credential. The `PAYMENT-REQUIRED` header prices this request at $0.10 in USDC on Base, and each `WWW-Authenticate: Payment` challenge quotes the same price over MPP. Pay either way, or send an API key. Also returned, with a `reason`, when a `PAYMENT-SIGNATURE` or an `Authorization: Payment …` credential was presented but the payment was not accepted or could not be settled. Nothing is charged in that case. See https://docs.brandfetch.com/agents/pay-per-request. headers: PAYMENT-REQUIRED: description: >- The x402 v2 payment challenge: base64-encoded JSON whose `accepts` array lists how to pay (scheme `exact`, network `eip155:8453`, the USDC asset, the `amount` in USDC's six decimals and the receiving `payTo` address). Sign the payment with an x402 client and retry with the result in a `PAYMENT-SIGNATURE` header. See https://docs.brandfetch.com/agents/pay-per-request. schema: type: string Cache-Control: description: >- `no-store` — a challenge is issued for one request and must not be cached. schema: type: string WWW-Authenticate: description: >- The MPP challenge: one `Payment` challenge for USDC.e on Tempo, which settles from a cent. Answer it with an `Authorization: Payment …` credential. Cards start at $0.50, above this price, so no card challenge is issued here; a card can pay for standing access on `POST /v2/agents/access`. schema: type: string content: application/json: schema: oneOf: - $ref: '#/components/schemas/PaymentChallenge' - $ref: '#/components/schemas/PaymentRejected' '404': description: >- Returned when the brand context could not be resolved. This may mean the domain was not found or is invalid, or that we were unable to crawl the domain (e.g. due to DNS resolution issues, anti-botting protections, or because the request could not be processed in the allotted time). content: application/json: schema: type: object properties: message: type: string enum: - or '429': description: API key quota exceeded content: application/json: schema: type: object properties: message: type: string enum: - API key quota exceeded security: - bearerAuth: [] - x402Payment: [] - mppPayment: [] components: schemas: BrandContextResponse: type: object description: >- Full brand context returned by the Brand Context API. Note: unlike other endpoints in this API which use camelCase, the Brand Context endpoint intentionally returns field names in `snake_case` (e.g., `canonical_name`, `resolved_at`, `value_proposition`, `target_audience`, `products_and_services`) to align with conventions commonly used by LLM tooling that consumes this data. properties: meta: $ref: '#/components/schemas/BrandContextMeta' identity: $ref: '#/components/schemas/BrandContextIdentity' positioning: $ref: '#/components/schemas/BrandContextPositioning' brand: $ref: '#/components/schemas/BrandContextBrand' PaymentChallenge: type: object description: >- Body of the 402 an unauthenticated request receives when the route can be paid for per request. The machine-readable challenges are in the `PAYMENT-REQUIRED` header for x402 and the `WWW-Authenticate: Payment` header for MPP; this body says the same in prose. properties: message: type: string example: >- Payment required. Either authenticate with a Brandfetch API key (Authorization: Bearer ) or pay for this request with x402: sign the payment described in the PAYMENT-REQUIRED header and retry with a PAYMENT-SIGNATURE header. documentation: type: string example: https://docs.brandfetch.com/agents/pay-per-request pricing: type: object properties: route: type: string example: GET /v2/brands/* price: type: string example: $0.10 resource: type: string description: The URL the payment is for. example: https://api.brandfetch.io/v2/brands/nike.com standingAccess: type: string example: >- For many requests, POST /v2/agents/access (paid the same way) provisions an API key preloaded with prepaid credits. PaymentRejected: type: object description: >- Body of the 402 a request carrying a `PAYMENT-SIGNATURE`, or an `Authorization: Payment …` credential, receives when the payment was not accepted or could not be settled. The resource was not served. Nothing was charged, so pay afresh and retry, unless the `message` says to retry the exact request first (a refused settlement of a standing-access purchase). properties: message: type: string example: >- The payment was not accepted, so the request was not served and nothing was charged. Sign a new payment for the PAYMENT-REQUIRED header and retry. reason: type: string description: >- The payment service's reason code, e.g. `insufficient_funds`. An MPP credential adds `credential_spent` (it already paid for a request), `credential_in_use` (another request is settling it; retry this exact request in a moment) `credential_malformed` (it could not be read) and `challenge_invalid` (it answers a challenge this API did not issue; answer a fresh one). A Tempo transaction that cannot complete adds `nonce_already_used`, `transaction_rejected`, `transaction_reverted` and `transaction_expired`: the transfer did not happen, so answer a fresh challenge. example: insufficient_funds documentation: type: string example: https://docs.brandfetch.com/agents/pay-per-request BrandContextMeta: type: object description: Metadata about the resolved brand context. required: - domain - canonical_name - resolved_at properties: domain: type: string description: The resolved domain name. example: brandfetch.com nullable: false canonical_name: type: string description: The canonical brand name. example: Brandfetch nullable: false resolved_at: type: string format: date-time description: Timestamp (ISO 8601) at which the context was resolved. example: '2026-05-25T08:48:36.843440+00:00' nullable: false BrandContextIdentity: type: object description: Core identity of the brand. properties: tagline: type: string description: A short tagline summarizing the brand. nullable: true mission: type: string description: The brand's mission statement. nullable: true description: type: string description: >- A descriptive paragraph about the brand, its products, and how it differentiates. nullable: true tags: type: array items: type: string description: A list of tags that characterize the brand. nullable: true BrandContextPositioning: type: object description: How the brand positions itself in the market. properties: value_proposition: type: string description: The brand's value proposition. nullable: true target_audience: type: array items: $ref: '#/components/schemas/BrandContextTargetAudience' description: Target audience segments for the brand. nullable: true products_and_services: type: array items: $ref: '#/components/schemas/BrandContextProductOrService' description: Products and services offered by the brand. nullable: true BrandContextBrand: type: object description: The brand's voice and visual style. properties: voice: $ref: '#/components/schemas/BrandContextVoice' style: $ref: '#/components/schemas/BrandContextStyle' BrandContextTargetAudience: type: object description: A single target audience segment for the brand. properties: segment: type: string description: Short label describing the audience segment. nullable: false description: type: string description: >- What this segment needs from the brand and how the brand serves them. nullable: false BrandContextProductOrService: type: object description: A product or service offered by the brand. properties: name: type: string description: Name of the product or service. nullable: false type: type: string description: Whether the offering is a `product` or a `service`. enum: - product - service example: product nullable: false description: type: string description: Description of the product or service. nullable: false BrandContextVoice: type: object description: The brand's voice — how it communicates. properties: summary: type: string description: A narrative summary of the brand's voice. nullable: true attributes: type: array items: type: string description: >- Short adjectives describing the voice (e.g., `confident`, `reassuring`). nullable: true avoid: type: array items: type: string description: Things the brand should avoid in its voice. nullable: true BrandContextStyle: type: object description: The brand's visual style. properties: summary: type: string description: A narrative summary of the brand's visual identity. nullable: true attributes: type: array items: type: string description: >- Short adjectives describing the visual style (e.g., `minimal`, `high-contrast`). nullable: true securitySchemes: bearerAuth: type: http scheme: bearer x402Payment: type: apiKey in: header name: PAYMENT-SIGNATURE description: >- An x402 payment for this one request: the signed payment for the challenge a bare request receives in its `PAYMENT-REQUIRED` header. Alternative to the bearer API key. See https://docs.brandfetch.com/agents/pay-per-request. mppPayment: type: http scheme: Payment description: >- An MPP (Machine Payments Protocol) payment, settled through Stripe: the credential answering one of the `WWW-Authenticate: Payment` challenges a bare request receives. Alternative to the bearer API key. See https://docs.brandfetch.com/agents/pay-per-request#paying-with-mpp. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.