Clearbit Logo API

Name: Clearbit Logo API
Brand: Clearbit Logo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey1 EndpointsREST

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

Install Jentic One Beta

Connect the Clearbit Logo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clearbit Logo 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Clearbit Logo API.

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

GET STARTED

Start building with Clearbit Logo API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Clearbit Logo API for, with concrete tasks.

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

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.

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.

Fetch the 400px JPG logo for 'shopify.com' to display as a hero image on a partner directory page

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for clearbit logo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/{domain}

Retrieve a company logo by domain name

GET

/{domain}

Retrieve a company logo by domain name

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Clearbit Logo API through Jentic.

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.