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

> Brand context built for AI agents

[Brand Context API](https://brandfetch.com/developers/brand-context-api) returns a structured, narrative-rich profile of a brand for a given domain. The kind of context useful for grounding LLMs, generating on-brand content, and powering personalized experiences.

For each domain, the API returns:

* **Identity** — tagline, mission, description, and tags.
* **Positioning** — value proposition, target audience segments, and products & services.
* **Brand** — a summary of the brand's voice and visual style, with descriptive attributes.

Brand Context API works in real-time. If a brand is not part of our dataset, it will be resolved live, ensuring **global coverage** for businesses of all sizes, geographies, and industries.

## Implementation guide

<Steps>
  <Step title="Get your API key">
    You’ll need to create an account on our [Developer Portal](https://developers.brandfetch.com/register). Creating an account is quick and easy, and will give you access to your dashboard where you’ll find your API key.
  </Step>

  <Step title="Make your first API call">
    Implement or run the code below to make your first API request.

    <CodeGroup>
      ```curl curl theme={null}
      curl --request GET \
      --url https://api.brandfetch.io/v2/context/{domain} \
      --header 'Authorization: Bearer <token>' \
      --header 'Accept: application/json'
      ```
    </CodeGroup>

    Authentication is done by passing your API key as a [Bearer Authentication](https://swagger.io/docs/specification/authentication/bearer-authentication/), the same way as the [Brand API](/brand-api/overview).
  </Step>

  <Step title="Test and deploy">
    All requests for the domain <b>brandfetch.com</b> are free and will not count towards your usage/quotas. You can make as many requests to Brandfetch’s own brand as you need while you iterate on and test your integration.

    Once you are ready to go live, simply replace <b>brandfetch.com</b> with the domain name you want to look up.

    <Tip>
      If you have custom requirements, or any questions [contact
      us](https://brandfetch.com/developers/contact/sales).
    </Tip>
  </Step>
</Steps>

## Query by domain

The Brand Context API is queried by domain name:

<CodeGroup>
  ```curl Domain theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/context/brandfetch.com \
  --header 'Authorization: Bearer <token>' \
  --header 'Accept: application/json'
  ```
</CodeGroup>

If you only have company names, use the [Brand Search API](/brand-search-api/overview) to match brand names to the most likely domains first.

## Content negotiation

The Brand Context API supports content negotiation. Use the `Accept` request header to choose the format of the response:

* `application/json` (default) — returns the structured JSON object described below.
* `text/markdown` — returns the brand context as a Markdown document, ready to drop directly into an LLM prompt or a Markdown-aware surface.

<CodeGroup>
  ```curl JSON theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/context/brandfetch.com \
  --header 'Authorization: Bearer <token>' \
  --header 'Accept: application/json'
  ```

  ```curl Markdown theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/context/brandfetch.com \
  --header 'Authorization: Bearer <token>' \
  --header 'Accept: text/markdown'
  ```
</CodeGroup>

## Response shape

When requesting `text/markdown`, the response is a Markdown document covering the same information. When requesting `application/json`, the response is grouped into a few top-level objects:

## Quotas and usage

When you sign up for a free developer account, you get 100 free requests.

If you need to make more requests, please upgrade to a paid plan. When upgrading, you can confirm your quota by looking at the `x-api-key-quota` response header. To see your current month's usage, look for the `x-api-key-approximate-usage` response header.

We will also send you an email warning you upon reaching 80% of your quota. The API will return an HTTP status code 429 when the quota has been reached.

In addition to a usage quota we also apply a request throughput limit to protect our service from abuse. By default, throughput is limited to a sustained 100 requests/second with some flexibility to accommodate bursts (30,000 requests / rolling 5 minute hard limit). You'll receive an HTTP status code 429 when you exceed this limit.

If your use-case requires higher throughput limits, [contact us](https://brandfetch.com/developers/contact/sales).

## Overage billing

When you purchase a subscription plan, you are allotted a quota depending on the payment plan. When you make more API requests than your quota allows, rather than blocking requests which are over your quota, we apply overage billing. This means that you'll never have any unexpected downtime. Requests over your quota are charged at an overage-fee rate.

To set a spending limit, head to the [Developer Dashboard](https://developers.brandfetch.com/dashboard/billing) and set a hard spending limit. Set this to \$0 if you want to disable overage.

Overage billing is not available on the free plan. To start using overage, please upgrade first to one of the paid plans.

## API Reference

For more details, refer to our [API Reference](/reference/brand-context-api).