canonical: https://jentic.com/apis/brandfetch.io/brandfetch

# Brandfetch API

The Brandfetch API returns a company's brand data: its logos, colors, fonts, and identifiers, resolved from a domain, company name, stock ticker, ISIN, or crypto symbol. You can fetch a single brand, pull a compact brand context for a domain, or resolve up to 100 brands in one batch request. A search operation locates brands by name, and an agent-access offer lets a caller buy standing access with a per-request payment.

## For AI agents

Resolve a company's logos, colors, fonts, and brand identity from a domain, name, ticker, ISIN, or crypto symbol. Authenticates with a bearer token in the Authorization header.

## Scope

Does not handle company financials, contact enrichment, or logo editing. Use for resolving brand assets and brand identity data only.

## Capabilities

- Resolve a brand's logos, colors, and fonts from a domain or identifier
- Look up brand data by stock ticker, ISIN, or crypto symbol
- Search for brands by name
- Fetch a compact brand context for a domain
- Resolve up to 100 brands in a single batch request
- Buy standing agent access with a per-request payment

## Use cases

### Agent Brand Lookup

An AI agent connected through Jentic resolves a company's brand from its domain and reads back the logos, colors, and fonts, so the agent can brand an email, slide, or landing page without a person sourcing assets. The structured response lets the agent pick the right logo variant and color directly.

Example prompt: Resolve the brand for stripe.com and return its primary logo URL and brand color palette

### Ticker and Symbol Brand Enrichment

A finance or research tool enriches holdings by resolving each brand from its stock ticker, ISIN, or crypto symbol, so a portfolio view shows the correct logo beside each position. The identifier-specific operations resolve a brand straight from the market symbol with no separate name match.

Example prompt: Resolve the brand for crypto symbol BTC and return its logo and official brand colors

### Batch Brand Resolution

A directory or CRM enriches many records at once by sending up to 100 domains in one batch request and reading back each brand, so a large refresh runs as a single managed call instead of hundreds. A name search covers the records where only a brand name is known.

Example prompt: Submit a batch of 50 customer domains and return each one's brand logo and colors

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/brands/{identifier}` | Get brand data by identifier |
| GET | `/v2/brands/domain/{domain}` | Get brand data by domain |
| GET | `/v2/brands/ticker/{ticker}` | Get brand data by stock or ETF ticker |
| GET | `/v2/context/{domain}` | Get brand context by domain |
| POST | `/v2/brands/batch` | Get up to 100 brands in one request |
| POST | `/v2/brands/transaction` | Get brand data from a transaction |

## Key resources

- **Brands** — Resolve a brand by domain, identifier, ticker, ISIN, or crypto symbol, singly or in batches
- **Search** — Find brands by name using a client ID
- **Context** — Fetch a compact brand context for a domain
- **Agent access** — Describe and buy standing agent access with a per-request payment

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 51 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 60 / 100
  - Agent Usability: 94 / 100
  - Security: 31 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/brandfetch.io/brandfetch/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Brandfetch API by hand means handling its bearer token auth, choosing between domain, identifier, ticker, ISIN, and crypto lookups, and deciding when to batch. Through Jentic you install once, import Brandfetch from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Brandfetch is read-first: you choose which operations your agent may call, so you can allow the brand-lookup and search operations and leave the agent-access purchase operation out. Because the brand lookups carry the domain or identifier in the URL path, rules bound which operations run rather than which brand is requested.
- **Credential handling:** Your Brandfetch token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a company logo' or 'look up brand colors', and Jentic returns the matching Brandfetch operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Clearbit API** — Company and brand enrichment including logos resolved from a domain
- **People Data Labs API** — Company and person data enrichment from a domain or identifier
- **Apollo API** — Sales intelligence with company and contact records keyed by domain

## FAQ

### Is there a Brandfetch MCP server?

You don't need an MCP server to give your agent the Brandfetch API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can resolve brands and read their logos and colors straight away, with no extra server to run and no tool definitions loaded into the agent's context.

### Can I limit what my agent is allowed to do with the Brandfetch API?

Yes. You choose which operations your agent may call, so you can allow the brand-lookup and search operations while leaving the agent-access purchase operation out, and every call the agent makes is logged. That keeps a read-only enrichment agent from ever triggering a payment.

### What authentication does the Brandfetch API use?

The Brandfetch API authenticates brand lookups with a bearer token passed in the Authorization header per its OpenAPI spec. It also offers per-request payment-based access through x402 and the Machine Payments Protocol, and a client ID query parameter for brand search. Through Jentic the token is stored encrypted by your own instance and added to each request at call time.

### Can I look up a brand by its stock ticker with the Brandfetch API?

Yes. Alongside domain and free-form identifier lookups, the API has dedicated operations to resolve a brand by stock or ETF ticker, by ISIN, and by crypto symbol, so an agent can enrich a market symbol with the right logo and colors without a name-matching step.

### What are the rate limits for the Brandfetch API?

The OpenAPI spec does not specify rate limits for the Brandfetch API. For current limits and fair-use guidance, see the Brandfetch documentation at https://docs.brandfetch.com.

### How do I enrich a company's brand through Jentic?

Import the Brandfetch API from the Jentic API Directory, then have your agent issue a request such as 'resolve the brand for this domain'. Jentic matches the intent to the brand-lookup operation and returns its input schema so the agent builds a valid request, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.