# Clearbit (HubSpot Breeze Intelligence)

> B2B person and company enrichment. Resolve an email to a person, a domain to a company, or an IP
> address to the business behind it. Acquired by HubSpot in December 2023 and now in publicly dated
> wind-down: the APIs below are live, but new API keys have not been issued since 2023 and the free
> tools and Logo API have been sunset. Only the Autocomplete API is callable without a credential.

This file was GENERATED by API Evangelist from the artifacts in the api-evangelist/clearbit repo.
Clearbit does not publish an llms.txt — probed https://clearbit.com/llms.txt and
https://dashboard.clearbit.com/llms.txt on 2026-08-13, both 404.

## Status (verified 2026-08-13)

- No OpenAPI, Swagger, AsyncAPI or GraphQL SDL is published anywhere on the Clearbit estate.
- The API reference at https://dashboard.clearbit.com/docs is a client-rendered SPA; the served
  HTML is an empty shell.
- New API key issuance is closed. Accounts created after 2023 cannot obtain a credential.
- `logo.clearbit.com` was sunset 2025-12-08 and no longer resolves in DNS.
- Every first-party SDK's last release predates the HubSpot acquisition.

## APIs

- [Enrichment (Person)](https://person.clearbit.com/v2/people/find): GET `?email=` — enriched
  person profile. Auth required. May return 202.
- [Enrichment (Company)](https://company.clearbit.com/v2/companies/find): GET `?domain=` —
  enriched firmographic record. Auth required.
- [Enrichment (Combined)](https://person.clearbit.com/v2/combined/find): GET `?email=` — person
  and company in one response. Auth required.
- [Streaming Enrichment](https://person-stream.clearbit.com/v2/combined/find): same contract, but
  holds the connection open up to 60s so a queued lookup resolves in-band instead of returning 202.
- [Reveal](https://reveal.clearbit.com/v1/companies/find): GET `?ip=` — company behind an IP.
- [Prospector](https://prospector.clearbit.com/v1/people/search): GET `?domain=` — people search.
- [Discovery](https://discovery.clearbit.com/v1/companies/search): GET `?query=` — company search.
- [Name to Domain](https://company.clearbit.com/v1/domains/find): GET `?name=` — company name to
  domain. Legacy, unsupported.
- [Risk](https://risk.clearbit.com/v1/calculate): GET `?email=` — fraud/abuse score. Legacy,
  unsupported.
- [Autocomplete](https://autocomplete.clearbit.com/v1/companies/suggest): GET `?query=` — company
  candidates. FREE, no API key, CORS-enabled. `logo` always returns null.

## Calling it

- Auth: one account secret API key, as HTTP Basic (key as username, empty password) or as
  `Authorization: Bearer <key>`. No OAuth, no scopes.
- Versioning: dated account versions, echoed on every response in `x-api-version`. Your version is
  pinned on first call and never changed without you.
- Errors: `{"error": {"type": "<slug>", "message": "<prose>"}}` as `application/json`. Not RFC 9457.
  Branch on `type`. Known types: `auth_required`, `invalid_api_key`, `unknown_route`.
- **202 is not an error.** It means the lookup is queued. Retry, use the streaming host, pass
  `cached=true`, or register a webhook. A client that treats 2xx as terminal success will silently
  record an empty result.
- Rate limits: 600 req/min per API (excluding Streaming and Reveal). Read `x-ratelimit-limit`,
  `x-ratelimit-remaining` and `x-ratelimit-reset` (unix epoch seconds). No `Retry-After`. 401s
  consume budget.
- No `Sunset` or `Deprecation` headers. Retirements are announced only in prose on the changelog.

## Docs

- [Developer docs (JS-rendered SPA)](https://dashboard.clearbit.com/docs)
- [Data attribute reference](https://clearbit.com/attributes) — server-rendered, the most complete
  machine-readable description of the response shapes still published.
- [Release notes / changelog](https://clearbit.com/changelog)
- [API version change log](https://help.clearbit.com/hc/en-us/articles/115015797408-Clearbit-API-Version-Change-Logs)
- [Help centre](https://help.clearbit.com/)
- [Status page](https://status.clearbit.com/)
- [Trust centre](https://clearbit.com/trust)
- [Terms of service](https://clearbit.com/legal)
- [Privacy policy](https://clearbit.com/privacy-policy)

## SDKs

All first-party. All last released before the HubSpot acquisition.

- [npm `clearbit`](https://www.npmjs.com/package/clearbit) — 1.3.5, 2020-06-04
- [gem `clearbit`](https://rubygems.org/gems/clearbit) — 0.3.3, 2020-08-03
- [PyPI `clearbit`](https://pypi.org/project/clearbit/) — 0.1.7, 2017-10-24
- [`github.com/clearbit/clearbit-go`](https://pkg.go.dev/github.com/clearbit/clearbit-go) — v1.1.0, 2021-11-12
- [GitHub organization](https://github.com/clearbit)

## Artifacts (API Evangelist)

- authentication/clearbit-authentication.yml
- conventions/clearbit-conventions.yml
- errors/clearbit-problem-types.yml
- lifecycle/clearbit-lifecycle.yml
- rate-limits/clearbit-rate-limits.yml
- changelog/clearbit-changelog.yml
- data-model/clearbit-data-model.yml
- conformance/clearbit-conformance.yml
- asyncapi/clearbit-webhooks.yml
- packages/clearbit-packages.yml
- components/clearbit-components.yml
- mcp/clearbit-mcp.yml
- plans/clearbit-plans-pricing.yml
- security/clearbit-trust-center.yml
- security/clearbit-vulnerability-disclosure.yml
- security/clearbit-domain-security.yml
- well-known/clearbit-well-known.yml
- graphql/clearbit-graphql-endpoint-probe.yml

## Not available

- No MCP server. Clearbit MCP listings on Zapier, viaSocket and Apify are third-party wrappers.
- No A2A agent card. `/.well-known/agent-card.json` and `/.well-known/agent.json` were probed on
  all eight hosts — 404 everywhere.
- No `/.well-known/security.txt`, no OAuth or OIDC discovery, no api-catalog.
- No CLI, no sandbox, no test credentials.
- No Agent Skills — there is no machine-readable spec to ground real operation identifiers in.