Show a Real Company Logo from Just a Domain

Where this fits

You're building a lead list for your sales team. Each row has a company name, a domain, and a grey placeholder with the first letter. You want the actual logo—Stripe's stripe, Notion's N—without manually scraping websites or maintaining a logo database. This skill gives you a direct image URL from a domain, ready to drop into any UI or server response.

Why agents benefit

• Zero parsing overhead: Agents don't need to fetch HTML, parse og:image, or handle favicon fallbacks. One URL returns a clean logo.
• Dark‑mode safe: The returned logo is designed to be visible on both light and dark backgrounds, so agent‑generated interfaces don't break.
• Server‑ready JSON: For backend agents, a JSON endpoint provides metadata (logo URL, dimensions, format) without browser dependencies.
• No API key in client: Use a publishable key (hf_pk_) in browsers; server agents can use a secret key for higher rate limits.
• Consistent sizing: Request ?size=64 or any dimension—no more cropping or scaling surprises.

Practical scenarios

CRM record enrichment

An agent updating a CRM automatically fetches a logo for each new company account. It inserts the image URL into the record's avatar field, replacing the generic initial. No extra HTTP calls from the frontend.

Lead list generation

When an agent compiles a list of prospects for a campaign, it can embed logos directly into the output HTML or email template. The agent only needs the domain—no manual verification of logo quality.

Integration directory pages

A developer agent building a page that lists SaaS integrations uses this skill to render each partner's logo. The image URL is stable and cacheable, so page loads stay fast even with dozens of logos.

Add it to your agent workflow

Install the skill with:

npx skills add Hydrafetch/skills --skill show-a-company-logo

Then use it in a browser context:

<img src="https://img.hydrafetch.com/logo/stripe.com?token=hf_pk_...&size=64" alt="Stripe" width="32" height="32" />

Or fetch JSON from a server agent:

curl "https://api.hydrafetch.com/logo?domain=stripe.com&token=hf_sk_..."

Compare before adopting

• Quality signals: Test with a handful of well‑known domains—do you get the official logo or a favicon? Check edge cases like subdomains and non‑ASCII domains.
• Maintenance freshness: Look at the GitHub repo's last commit and issue responses. A dead repo means broken logos when domains change.
• Alternatives: Favicon services (e.g., Google's favicon API) are free but often return low‑res or missing icons. Compare reliability and whether they handle dark mode.
• Workflow fit: Does the skill integrate with your agent's existing HTTP stack? The URL‑only approach is trivial, but the JSON path might need a library.

Why it is worth tracking

This skill solves a mundane but persistent problem—company logos in data‑driven interfaces. It's currently at 0 stars on GitHub, but the approach is practical and the author (Hydrafetch) has a clear API design. Keep an eye on adoption: if the repo gains traction or the API shows uptime, it's a low‑effort win for any agent that touches company data. For more skills like this, browse the OpenAgentSkill directory. Evaluate it now, because the cost of switching later is just a URL change.