Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey (publishable key in token query, CDN); http bearer (secret key, Brand API; separate transaction beta key)23 EndpointsREST
For Agents
Fetch a company's logo by domain, name, ticker, ISIN, or crypto symbol, look up or search brand profiles, subscribe to brand.updated webhooks, and identify merchants from card descriptors.
Use for: Get the logo for stripe.com as a 256 pixel PNG, Find the logo for ticker AAPL, Look up the brand profile for a company domain, Search brands matching 'blue bottle'
Not supported: Does not generate or design new logos, return firmographic data such as revenue or headcount, or host your own brand assets. Use for fetching existing company logos and brand profiles only.
The Logo.dev API returns company logos and brand data from two hosts. The image CDN at img.logo.dev serves a logo by domain, brand name, stock ticker, ISIN, crypto symbol, stock exchange, or market index, with size, format, theme, greyscale, retina, and fallback options. The JSON API at api.logo.dev looks up a full brand profile from one identifier, returns its logo or brandmark, and searches brands by query. Accounts on a paid plan can subscribe to brands and receive brand.updated webhook events, and a private transaction beta identifies the merchant behind a card descriptor.
Install Jentic One Beta
Connect the Logo.dev API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Logo.dev 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.
1
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%2Flogo.dev%2Flogo-dev" | sh2
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%2Flogo.dev%2Flogo-dev" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Logo.dev API.
Fetch a logo image by domain from the img.logo.dev CDN with size, format (jpg, png, webp), theme, greyscale, and retina options
Get a logo by brand name, stock ticker, ISIN, crypto symbol, stock exchange, or market index
Look up a brand profile from exactly one of domain, ticker, isin, crypto, or name with v2GetBrand
Search brands by a q query and return matching profiles with v2SearchBrands
Subscribe the account to brand.updated events for a brand and manage webhook endpoints and their signing secrets
Identify the merchant behind a card descriptor such as 'SQ *BLUE BOTTLE COFFEE' with identifyMerchant (private beta)
Use Cases
Patterns agents use Logo.dev API for, with concrete tasks.
★ Agent-enriched company records through Jentic
An agent cleaning a CRM export asks Jentic for the Logo.dev brand lookup, calls v2GetBrand with each account's domain, and writes the returned brand profile and logo back to the record. The secret key stays in your self-hosted Jentic One instance, which matters because Logo.dev says the secret key should be called only from a server.
Search Jentic for 'look up a brand by domain', call v2GetBrand with domain 'stripe.com', and return the brand name and logo URL
Logos in product UIs
Front-end apps render company logos directly from the CDN with GET /{domain} and a publishable key in the token query parameter, which Logo.dev marks safe for client-side code. Options cover size, width and height up to 800, jpg, png, or webp format, light, dark, or auto theme, greyscale, retina, and a monogram or 404 fallback.
Build a CDN request for getLogo with domain 'shopify.com', size 128, format 'png', and theme 'dark'
Financial and crypto logos
Investing and portfolio apps fetch logos with getLogoByTicker, getLogoByIsin, getLogoByCrypto, getLogoByExchange, and getLogoByIndex, so a holding list can show the right mark from a ticker such as aapl, an ISIN such as US0378331005, or a crypto symbol such as BTC.
Call getLogoByTicker with ticker 'aapl' and getLogoByCrypto with symbol 'BTC', both at size 64
Brand change notifications
Create a webhook endpoint with v2CreateWebhookEndpoint using a url and filter_types such as brand.updated, then subscribe to individual brands with v2SubscribeToBrand. Signing secrets can be read and rotated per endpoint, and subscriptions need a paid plan.
Call v2CreateWebhookEndpoint with url 'https://hooks.example.com/logo-dev' and filter_types ['brand.updated'], then call v2SubscribeToBrand for brand id 'brand_4x0wr3g0000g00400000000004'
Key Endpoints
23 endpoints — the logo.
METHOD
PATH
DESCRIPTION
GET
/{domain}
Get a logo by domain (CDN)
GET
/ticker/{ticker}
Get a logo by stock ticker
GET
/v2/brands
Look up a brand
GET
/v2/search
Search brands
GET
/v2/brands/logo
Get a brand logo
PUT
/v2/brands/{id}/subscription
Subscribe to a brand
POST
/v2/webhook_endpoints
Create a webhook endpoint
GET
/{domain}
Get a logo by domain (CDN)
GET
/ticker/{ticker}
Get a logo by stock ticker
GET
/v2/brands
Look up a brand
GET
/v2/search
Search brands
GET
/v2/brands/logo
Get a brand logo
PUT
/v2/brands/{id}/subscription
Subscribe to a brand
POST
/v2/webhook_endpoints
Create a webhook endpoint
Jentic AI Readiness Score
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.
L
Logo.dev API
- AI-Aware (B)66/100
83
Foundational Compliance75
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability45
Security79
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
83
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
75
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
24%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
69%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
34%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
45
Security
Trust, risk posture, and security compliance.
Grade: DSignals: 1
45%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
79
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
79%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Logo.dev by hand means juggling three keys across hosts: a publishable key in the token query for the CDN, a secret bearer key for api.logo.dev, and a separate transaction beta key, plus retrying 202 responses for brands still being indexed. Through Jentic you install once, import Logo.dev from the API Directory, store the keys once, and your agent calls it.
Permission scoping
Logo.dev puts the brand id in the URL path for subscriptions and the endpoint id for webhook endpoints, so a rule can pin your agent to one webhook endpoint or one brand subscription. Brand lookups take their identifier as a query parameter, so for those, rules bound which operations your agent may call. You choose the operations it may call, so destructive ones like v2DeleteWebhookEndpoint are not included unless you add them.
Credential isolation
Your Logo.dev keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a company logo' or 'look up a brand by ticker', and Jentic returns the matching Logo.dev operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Logo.dev API through Jentic.
What authentication does the Logo.dev API use?
Per its OpenAPI spec, Logo.dev uses different keys per host. The img.logo.dev CDN takes a publishable key (pk_) as an apiKey in the token query parameter. The api.logo.dev brand endpoints take a secret key (sk_) as an HTTP bearer token, and the transaction beta uses its own tx_beta_ bearer key. Through Jentic each key is stored encrypted by your own Jentic One instance and injected at call time.
Can I get a logo from a stock ticker with the Logo.dev API?
Yes. GET /ticker/{ticker} on the img.logo.dev CDN returns the logo for a ticker such as aapl, and GET /isin/{isin}, GET /crypto/{symbol}, GET /exchange/{exchange}, and GET /index/{symbol} cover ISINs, cryptocurrencies, exchanges, and market indexes.
What are the rate limits for the Logo.dev API?
The OpenAPI spec does not specify rate limits. Brand lookups cost API credits per request, and a brand Logo.dev has not indexed returns a 202 while it is fetched; check the Logo.dev documentation for current credit costs and limits.
How do I look up a brand by domain with the Logo.dev API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add the Logo.dev API from the Jentic API Directory, and have your agent search for 'look up a brand by domain'. Jentic returns v2GetBrand (GET /v2/brands) with its schema, and the agent sends exactly one identifier such as domain 'stripe.com'. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Logo.dev MCP server?
You don't need an MCP server to give your agent the Logo.dev API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with operations discovered on demand instead of loading extra tool definitions into its context.
Can I limit what my agent is allowed to do with the Logo.dev API?
Yes. For an enrichment agent, write a rule that allows only v2GetBrand, v2SearchBrands, and the CDN logo lookups. The agent can fetch logos and brand profiles, while v2DeleteWebhookEndpoint, v2RotateWebhookEndpointSecret, and brand subscriptions are outside the allowed set, and every call it makes is logged.
What image options does the Logo.dev CDN support?
The logo endpoints accept size, width and height (up to 800), format of jpg, png, or webp, theme of auto, light, or dark, greyscale, retina, a fallback of monogram or 404, and a redirect option.
GET STARTED