canonical: https://jentic.com/apis/clearbit.com/clearbit # Clearbit Logo API Jentic publishes the only available OpenAPI specification for Clearbit Logo API, keeping it validated and agent-ready. Retrieve high-quality company logos by domain name with configurable size (32px to 400px), format (PNG or JPG), and greyscale options. The API resolves any company domain to its official logo image, making it ideal for dynamically populating business directories, CRM interfaces, and email signatures with brand-accurate visual assets. ## For AI agents Retrieve company logos by domain name with configurable size and format. Returns PNG or JPG images from 32px to 400px for any company with a web presence. ## Scope Does not handle contact enrichment, company firmographics, or person lookup - use for company logo retrieval only. ## Capabilities - Fetch a company logo in PNG or JPG format given its domain name - Resize logos to 32, 64, 128, 256, or 400 pixel dimensions on the fly - Convert colour logos to greyscale for consistent UI themes - Populate CRM contact cards with company brand assets automatically - Enrich business directory listings with verified company logos ## Use cases ### AI Agent Logo Retrieval via Jentic AI agents building dynamic dashboards or reports can fetch company logos on the fly by searching Jentic for logo retrieval operations. The agent passes a company domain and receives the logo image URL, which it inserts into generated reports, emails, or UI components without manual asset management. Example prompt: Search Jentic for 'get company logo', load the Clearbit Logo operation schema, and retrieve the 128px PNG logo for 'github.com' ### CRM Contact Enrichment with Brand Logos Sales and marketing platforms enrich contact records by pulling the company logo associated with each lead's email domain. The Clearbit Logo API returns production-ready images at configurable sizes, so CRM cards, email templates, and deal pipelines display recognisable brand assets without manual uploads. Example prompt: Retrieve the 64px PNG logo for 'salesforce.com' and attach it to the corresponding CRM contact record ### Business Directory and Marketplace Branding Online directories, app marketplaces, and partner portals display company logos alongside listings. The API serves correctly sized images (32px for favicons up to 400px for hero banners) in both PNG and JPG, eliminating the need to store or resize logos locally. Example prompt: Fetch the 400px JPG logo for 'shopify.com' to display as a hero image on a partner directory page ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /{domain} | Retrieve a company logo by domain name | ## Key resources - **Logos** — Retrieve company logo images by domain with size, format, and greyscale options ## Why Jentic - **Setup:** Wiring the Clearbit Logo API by hand means passing your API key in the Authorization header and building requests against logo.clearbit.com for each domain lookup. Through Jentic you install once, import the Clearbit Logo API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** This API exposes a single read operation that fetches a logo by domain, so the agent's reach is bounded to that lookup, and you choose to include it in the allowed set. - **Credential handling:** Your Clearbit API key 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 'fetch a company logo by domain', and Jentic returns the matching Clearbit operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **FullContact Enrich API** — Enriches contact records with demographics, employment, and social profiles beyond just logos - **People Data Labs API** — Large-scale person and company enrichment with firmographic, demographic, and contact data - **Hunter API** — Finds professional email addresses associated with a domain ## FAQ ### Why is there no official OpenAPI spec for Clearbit Logo API? Clearbit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clearbit Logo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Clearbit Logo API use? The Clearbit Logo API uses an API key passed in the Authorization header. Through Jentic, this key is stored encrypted in the credential vault and agents receive scoped access without handling raw keys directly. ### Can I retrieve a logo in a specific size with the Clearbit Logo API? Yes. The API accepts a size query parameter with supported values of 32, 64, 128, 256, and 400 pixels. The default size is 128px if no size parameter is provided. ### What image formats does the Clearbit Logo API support? The API returns logos in PNG (default) or JPG format. Specify the format query parameter to choose between them. A greyscale parameter is also available to return a monochrome version of the logo. ### How do I fetch a company logo through Jentic? Install the Jentic SDK with pip install jentic, then search for 'get company logo by domain'. Jentic returns the Clearbit Logo operation schema including the GET /{domain} endpoint. Pass the target company domain and optional size/format parameters to execute the call. ### What happens if a company domain has no logo in the Clearbit database? The API returns a 404 response with an error object containing a message and type field. Your integration should handle this case by falling back to a placeholder image or skipping the logo display. ### Can I limit what my agent is allowed to do with the Clearbit Logo API? Yes. Jentic One runs self-hosted on your own infrastructure, and your own rules decide which operations and credentials the agent may use. The Clearbit Logo API exposes a single read operation that fetches a company logo by domain, so you scope the agent by choosing whether to include that lookup in its allowed set. Because it is the only operation, granting it bounds the agent to logo retrieval and nothing more, and your stored API key is injected at execution time rather than exposed to the agent.