CLEARBIT LOGO API ALTERNATIVE
Move off the Clearbit Logo API without rebuilding the UI.
For the basic domain-to-image pattern the change is one hostname: a Clearbit Logo API lookup such as https://logo.clearbit.com/stripe.com becomes https://img.replynodes.com/stripe.com. No account, no API key and no ReplyNodes credits on the new endpoint.
- Free
- No API key
- No account required
GET https://img.replynodes.com/{domain}
The smallest useful change
Find the host. Replace the host. Test the result.
This page documents the verified domain-to-image URL pattern only. It does not claim coverage, uptime, latency, image formats or usage promises for either endpoint, and it does not claim that every Clearbit feature has an equivalent here.
https://logo.clearbit.com/stripe.comChecked from this network on 2026-09-26 and it did not resolve, so for anyone still holding that URL the migration is also a repair. Verify the host your own code calls before you assume the old lookup still answers.
https://img.replynodes.com/stripe.com<img src="https://logo.clearbit.com/stripe.com" alt="Stripe logo" />The legacy host this page migrates away from — it did not resolve when this page was last built
<img src="https://img.replynodes.com/stripe.com" alt="Stripe logo" />One hostname changed — the rest of the template is untouched
Migration checklist
Keep the change easy to review.
The implementation is small; the validation is yours. Work through the list with the domains and fallback states your application actually relies on.
Find every old reference
Search code, templates and stored content for logo.clearbit.com — including rows saved in your own database.
Replace the hostname
Use https://img.replynodes.com/{domain} for a basic domain-to-image URL. The path shape is the same, so the surrounding template does not change.
Test the domains your UI depends on
Request the new URL for the domains you actually render and check the status, the content type and your own fallback state.
Check your query parameters
Do not assume legacy Clearbit query parameters are supported. If you relied on size, format or other options, verify them explicitly or drop them.
What stays true
A public image URL, and nothing more implied.
Both columns exist so the migration is reviewable: the left one holds what the new endpoint actually promises, the right one holds what it deliberately does not.
True after the switch
- A direct image URL built from a bare public domain
- Works anywhere an image tag works — no SDK and no client library
- No account, no API key and no ReplyNodes credits
- Deterministic fallback when no brand mark can be resolved
- The same 24-hour cache directive the host is captured returning
Not claimed
- Legacy Clearbit query parameters, sizes or formats
- Coverage, uptime, latency or image-format guarantees
- A usage-limit or fair-use promise for either endpoint
- Full feature parity with any commercial brand-data vendor
- A public SLA or support commitment for the free endpoint
Discover more
One hostname is one migration.
The logo endpoint is one capability of a read-only public-data gateway. Each capability has its own free endpoint and a guide on docs.replynodes.com.
Logo API
The endpoint this page migrates to: one domain in, one image URL out, no key and no account.
Open the Logo API →Brand API
Migrating more than an image? The free Brand API returns a JSON brand kit for a domain — name, description, logo, colors and fonts.
Open the Brand API →Context APIs
Web search, Reddit, YouTube, App Store, Google Play and more — one read-only gateway for public data.
Explore all APIs →
FAQ
Migration questions.
Is this a drop-in replacement for the Clearbit Logo API?
For a basic domain-to-image URL it is: you replace the hostname and the template keeps working. Nothing beyond that is implied — do not assume legacy Clearbit query parameters are supported, and test the domains your interface actually depends on.
Do I need a Clearbit account or an API key on the new endpoint?
No. https://img.replynodes.com/{domain} is a public image endpoint: there is no key to migrate, no account to create and no token to rotate.
What happens when a domain cannot be resolved?
The endpoint uses the same fallback contract as the free logo host: it answers 200 with a neutral placeholder image, and the x-replynodes-logo-fallback header states which you got — logo for a resolved brand mark, placeholder when there is none. A placeholder is served with cache-control public, max-age=600 where a real mark is served with max-age=86400, so read the header or the cache directive instead of treating a 200 as proof that a mark exists. Keep a neutral state in your own interface so a missing mark never breaks a row or a card.
How should I test the migration?
Request the new URL for the domains your product actually renders, check the status and content type you get back, and look at your own fallback path. The Logo API page shows a captured response so you know what a real one looks like before you ship.
Does the logo endpoint cost anything?
No. The public logo image endpoint is free, does not use ReplyNodes credits and is not tied to a billing account.
Where do I go when I need brand data rather than one image?
The free Brand API returns a JSON brand kit for the same domain: company name and description, logo and other public image assets, colour palette, fonts and style signals.
Replace one hostname.
Request the domains you actually render, check the response, keep a neutral fallback — then ship the change.