# Clearbit vs ZeroBounce (slim)

> ZeroBounce scores 62.4 (B) to Clearbit's 14.1 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md (~4,100 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.json · canonical https://www.anchorterminal.com/compare/clearbit-vs-zerobounce
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ZeroBounce scores 62.4 (B) on agent readiness against Clearbit's 14.1 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency & trust. Both do lead enrichment.

- Clearbit: F 14.1, rank #1458 of 1486 · https://www.anchorterminal.com/tools/clearbit.min.md
- ZeroBounce: B 62.4, rank #559 of 1486 · https://www.anchorterminal.com/tools/zerobounce.min.md
- Clearbit, good for Only for teams that already hold a Clearbit contract. Ahead on Transparency & trust, 73 against 63.
- ZeroBounce, good for Email verification before outreach, the verification-first listing in lead-data. Ahead on Reliability, 75 against 30; Schema & documentation, 54 against 0; Agent ergonomics, 69 against 0; Security & auth, 65 against 8; Payments & pricing, 35 against 0; Maintenance & community, 70 against 4. Also A hosted endpoint, with nothing to install; Runs on your own machine.

| Category | Clearbit | ZeroBounce |
| --- | --- | --- |
| Reliability (16%) | 30 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 0 | 54 |
| Agent ergonomics (13%) | 0 | 69 |
| Security & auth (14%) | 8 | 65 |
| Payments & pricing (10%) | 0 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 4 | 70 |
| Transparency & trust (7%) | 73 | 63 |

| Fact (where they differ) | Clearbit | ZeroBounce |
| --- | --- | --- |
| Vendor | HubSpot, Inc. | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | no (local only) | `https://api.zerobounce.net/v2` |
| Transports | HTTP | HTTP, stdio |
| Pricing | Paid | Pay per use |
| Licence | Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | none | 0 |
| llms.txt | no | yes |
| Last release | 2025-12-08 | 2026-10-25 |
| Terms last updated | 2025-05-30 | 2026-05-05 |
| Privacy policy last updated | 2026-08-31 | 2026-06-30 |
| Customer content may train models | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 1.5/5 (4) | none |

Why the edge:
- Agent ergonomics, ZeroBounce +69: Clearbit 0 (Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).); ZeroBounce 69 (A compact JSON result per address, batch validation and a file API for lists (18 of 25). Little to paginate; file status and results by file id (10 of 20). Status and sub-status codes say why an address failed, and the error page explains 400, 404 and 429 (14 of 20). Unknown results are free and safe to retry; repeated validations are charged again (12 of 20). Many official SDK wrappers and an MCP server, with few required parameters (15). 18+10+14+12+15 = 69.)
- Maintenance & community, ZeroBounce +66: Clearbit 4 (Read for a closed service. The latest changelog entry is still the Logo API shutdown notice of 24 November 2025, for 8 December 2025, more than 180 days ago (0). No dated entries in the last 90 days (0). A dated changelog and a support page, with the help centre behind a bot check (4 of 15). No current SDK or MCP server, and a search of the official MCP registry returned none (0). No package to judge (0).); ZeroBounce 70 (Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70.)
- Security & auth, ZeroBounce +57: Clearbit 8 (Graded on the interface an outside agent can use, so the credential, least-privilege, injection and audit lines score nothing (0). The trust page says Clearbit is SOC 2 Type 2 compliant and runs annual penetration tests. No security.txt (clearbit.com/.well-known/security.txt returns 404), bug bounty or disclosure policy was found (8 of 20).); ZeroBounce 65 (Several named keys besides a Master key, regeneration, deactivation and IP whitelists (25), less 10 because the documented calls carry the key in the `api_key` query string (15 of 30). Validation only reads, though file and list endpoints can delete uploads (12 of 20). Results are structured status codes with little free text (10 of 15). API usage and dashboard statistics endpoints (10 of 15). SOC 2 Type 2, ISO/IEC 27001:2022, continuous testing with Intigriti and penetration testing with BitSentinel; no public disclosure policy found (18 of 20). 15+12+10+10+18 = 65.)
- Schema & documentation, ZeroBounce +54: Clearbit 0 (Graded on the interface an outside agent can use. The API docs sit behind the customer login and there is no sign-up, so the contract, description, typed-input, example and versioning lines score nothing. clearbit.com/llms.txt returns 404 (0). This says nothing about the service for existing customers.); ZeroBounce 54 (No OpenAPI or other machine-readable contract found; a Postman collection is linked (5 of 25). llms.txt lists marketing pages, and the docs have no Markdown twins (5 of 10). Endpoint pages explain timing, credits and when to use batch or file APIs (14 of 20). Parameter tables and listed status and sub-status values, including the ai_agent_mailbox sub-status added in July 2026 (10 of 15). Examples per endpoint, a sandbox and an error-code page (12 of 15). v2 paths, an API migration page and dated maintenance notices on the status page, with no API changelog (8 of 15). 5+5+14+10+12+8 = 54.)
- Reliability, ZeroBounce +45: Clearbit 30 (Read with the hosted lines. An Atlassian Statuspage with 22 components and incident history (20). Its feed shows a minor Salesforce synchronisation incident from 18 to 23 September and authentication errors on 31 August marked no impact, with nothing since, re-read on 17 October, so minor only. These affect existing customers, since no outside agent can reach the APIs (10 of 30, reduced from 20 because the history covers a service closed to new users). No published limits for an outside agent (0). No overload or retry guidance on a public page (0). No SLA found (0). The standalone service is closed to new sign-ups, so the general-availability line scores nothing (0).); ZeroBounce 75 (Hosted lines. Statuspage at status.zerobounce.net with API, API-US, API-EU, Bulk API, website and Cloudflare components (20). The incident feed for 8 August to 6 November shows a 6-minute members platform disruption on 9 September, about 3 minutes of reduced EU API availability on 1 October, and a file upload issue on 26 October resolved within 6 minutes, all minor (20). Limits published per endpoint group with numbers and block lengths (15). 429 is documented with advice to throttle, but no Retry-After, and a block can last an hour or a day (10 of 15). No SLA found (0). Generally available (10). 20+20+15+10+0+10 = 75.)
- Payments & pricing, ZeroBounce +35: Clearbit 0 (No x402, MPP or L402 (0). No public prices, and /pricing redirects to the home page (0). The free tools ended on 30 April 2025 (0). No sign-up route at all (0).); ZeroBounce 35 (No x402, MPP or L402 (0). Per-credit prices public, from $39 for 2,000 validations (20). Freemium of 100 validations a month for business or premium domains; a card requirement isn't stated, and free webmail addresses don't qualify (15 of 20). A person signs up in a browser (0). 0+20+15+0 = 35.)