canonical: https://jentic.com/apis/logo.dev/logo-dev # Logo.dev API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Logo images** — CDN logos by domain, name, ticker, ISIN, crypto, exchange, or index - **Brands** — Brand profiles with logos and brandmarks, looked up or searched - **Subscriptions** — Per-brand subscriptions that drive brand.updated events - **Webhook endpoints** — Event receivers with signing secrets ## 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:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 83 / 100 - Developer Experience & Jentic Compatibility: 75 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 94 / 100 - Security: 45 / 100 - AI Discoverability: 79 / 100 - **View full report:** https://jentic.com/apis/logo.dev/logo-dev/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 ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Brandfetch API** — Brand logos, colors, and fonts by domain - **Clearbit API** — Company enrichment with firmographic data and logos - **BuiltWith API** — Technology stack data for websites - **People Data Labs API** — Person and company enrichment datasets ## FAQ ### 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.