Install Jentic One Beta

Connect the Brandfetch API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brandfetch API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrandfetch.io%2Fbrandfetch" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrandfetch.io%2Fbrandfetch" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Brandfetch API.

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

GET STARTED

Start building with Brandfetch API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Brandfetch API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

14 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Brandfetch API through Jentic.

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.

Brandfetch API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer, apiKey, payment14 EndpointsREST

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

Use for: Get the logo and brand colors for a company domain, Look up brand data by stock ticker, Search for a brand by name, Find the fonts a brand uses

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

10%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

68%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

78%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

31%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Brandfetch API to your agent

Capabilities

Start building with Brandfetch API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Brandfetch API

Jentic AI Readiness Score

Brandfetch API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness