{ "data": { "a": { "slug": "clearbit", "name": "Clearbit", "vendor": "HubSpot, Inc.", "vendorUrl": "https://clearbit.com", "kind": "http-api", "category": "lead-data", "summary": "Clearbit is a B2B data provider for company, contact and IP intelligence, acquired by HubSpot. It still runs enrichment, reveal and prospecting APIs for existing customers, and HubSpot's Breeze Intelligence carries its data for new buyers.", "url": "https://www.anchorterminal.com/tools/clearbit", "markdownUrl": "https://www.anchorterminal.com/tools/clearbit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clearbit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clearbit.json", "dns": "clearbit.grade.anchorterminal.com", "license": "Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand", "transports": [ "http" ], "packages": [], "auth": "api-key", "authNotes": "API access is for existing Clearbit customers through their dashboard, and dashboard.clearbit.com/docs redirects to a login. The home page links only to a customer login, with no sign-up for new customers (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No public prices. clearbit.com/pricing redirects to the home page. The free tools (Free Clearbit Platform, Weekly Visitor Report, Clearbit Connect, TAM Calculator and the free Slack integration) were discontinued on 30 April 2025, and the free Logo API was shut down on 8 December 2025 (https://clearbit.com/changelog, checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the public Clearbit pages (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "capabilities": [ "lead.enrichment", "data.company" ], "tags": [ "hosted", "not-for-agents", "sales-led", "closed-source", "enrichment", "status-page", "soc2" ], "lastRelease": "2025-12-08", "graded": true, "anchor": { "graded": true, "score": 14.1, "grade": "F", "agentReady": false, "rank": 1482, "ranked": true, "rankOf": 1510, "categoryRank": 22, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 0, "maintenance": 4, "payments": 0, "reliability": 30, "schema": 0, "security": 8, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": 0, "verdict": "There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.", "bestFor": "Only for teams that already hold a Clearbit contract.", "strengths": [ "Public status page with 22 components and incident history", "Dated sunset notices with months of warning, such as the Logo API", "Sub-processor page names nine providers with purpose and country and promises 30 days' notice of changes", "Privacy policy updated 31 August 2026 and a trust page claiming SOC 2 Type 2" ], "weaknesses": [ "No public API or MCP server an outside agent can call", "No sign-up or public prices, and the home page links only to a customer login", "Free tools retired on 30 April 2025 and the Logo API after 8 December 2025", "No security.txt, and the help centre sits behind a bot check" ], "agentNotes": [ "Don't plan to call Clearbit. Hand the task to a person with an existing Clearbit account, or use HubSpot's Breeze Intelligence through HubSpot", "Replace logo.clearbit.com links, which stopped working after 8 December 2025" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 14.1 } ], "editorialScores": { "ergonomics": 0, "maintenance": 4, "payments": 0, "reliability": 30, "schema": 0, "security": 8, "transparency": 73 }, "provenanceScore": 73, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-28", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/lead.enrichment", "tool": "https://letme.dev/clearbit" }, "area": "web-data", "provenance": { "legalEntity": "HubSpot, Inc.", "domain": "clearbit.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://clearbit.com/legal", "privacy": "https://clearbit.com/privacy-policy", "statusPage": "https://status.clearbit.com", "changelog": "https://clearbit.com/changelog", "securityTxt": "none", "checked": "2026-10-17", "notes": [ "The terms were last updated on 30 May 2025 and the privacy policy on 31 August 2026. Both name HubSpot, Inc. under its Clearbit brand.", "clearbit.com/.well-known/security.txt returns 404 (on 14 October it answered with an HTML page).", "help.clearbit.com answered with a Cloudflare bot check on 14 and 17 October, so its article on buying Clearbit wasn't read. A search result quoted it as saying new standalone subscriptions are no longer offered, which we couldn't confirm first-hand.", "status.clearbit.com is an Atlassian Statuspage (clearbit.statuspage.io).", "No RDAP lookup was made for clearbit.com." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/clearbit.json", "live": { "slug": "clearbit", "vendorStatus": { "page": "https://status.clearbit.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:56:30.928266818Z" }, "securityTxt": { "url": "https://clearbit.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:36.403818023Z" }, "domain": { "domain": "clearbit.com", "registered": "2003-07-04", "source": "https://rdap.verisign.com/com/v1/domain/clearbit.com", "checkedAt": "2026-11-01T14:12:43.894008868Z" }, "pages": [ { "url": "https://clearbit.com/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:01:02.236014474Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "404e1ac5a18e" }, { "url": "https://clearbit.com/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:01:06.389980052Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d77014da379a" }, { "url": "https://clearbit.com/legal", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:01:04.380623273Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "028252d0e504" } ], "updatedAt": "2026-11-07T22:56:30.928266818Z" } }, "answer": "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 \u0026 trust.", "b": { "slug": "zerobounce", "name": "ZeroBounce", "vendor": "Hertza L.L.C. (ZeroBounce)", "vendorUrl": "https://www.zerobounce.net", "kind": "http-api", "category": "lead-data", "summary": "ZeroBounce is an email verification API from Hertza L.L.C. that checks single addresses and lists for deliverability, with status and sub-status codes, plus AI scoring, email finder, domain search and activity data, and an open-source MCP server.", "url": "https://www.anchorterminal.com/tools/zerobounce", "markdownUrl": "https://www.anchorterminal.com/tools/zerobounce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zerobounce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zerobounce.json", "dns": "zerobounce.grade.anchorterminal.com", "repo": "https://github.com/zerobounce", "license": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.zerobounce.net/v2", "packages": [ { "registry": "npm", "name": "@zerobounce/zero-bounce-sdk" } ], "auth": "api-key", "authNotes": "API key from the dashboard, sent as the `api_key` query parameter in the documented calls. Several keys per account besides a Master key; keys can be named, switched off, regenerated, deleted and limited to whitelisted IPs or ranges. No endpoint scopes found.", "pricing": "usage", "pricingNotes": "Pay as you go from $39 for 2,000 validations, one credit per email, 20 per successful Email Finder query, nothing for unknown results. ZeroBounce ONE from $99 a month, minimum 10,000 credits. Freemium of 100 validations a month for business or premium domains. Credits bought after 1 June 2026 expire two years after the last purchase (https://www.zerobounce.net/pricing, https://www.zerobounce.net/terms-of-use, checked 2026-11-06).", "priceSummary": "$0.0195 / call", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing or MCP page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.zerobounce.net/docs/", "llmsTxt": "https://www.zerobounce.net/llms.txt", "capabilities": [ "email.verification", "email.finder", "lead.enrichment" ], "tags": [ "hosted", "mcp", "status-page", "soc2", "iso27001", "free-tier", "usage-based", "typescript", "eu-region", "closed-source" ], "lastRelease": "2026-10-25", "graded": true, "anchor": { "graded": true, "score": 62.4, "grade": "B", "agentReady": false, "rank": 561, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 70, "payments": 35, "reliability": 75, "schema": 54, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract.", "bestFor": "Email verification before outreach, the verification-first listing in lead-data.", "strengths": [ "Status and sub-status codes per address, and unknown results don't use credits", "Statuspage with API, API-US, API-EU and Bulk API components; three short incidents in the 90 days to 6 November 2026", "Rate limits published per endpoint group, with the block length for each", "SOC 2 Type 2, ISO/IEC 27001:2022, Intigriti testing and a published sub-processor list", "Freemium of 100 validations a month for business domains, and pay-as-you-go from $39 for 2,000" ], "weaknesses": [ "Every documented example sends the key as an `api_key` query parameter", "No OpenAPI or other machine-readable contract; a Postman collection only", "Going over a limit blocks the key for a minute to a day, with no Retry-After documented", "llms.txt lists marketing pages, not the API docs", "Keys can be IP-whitelisted but not scoped to endpoints" ], "agentNotes": [ "Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits", "Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later", "Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour", "Use the bulk file API for large lists instead of looping on /v2/validate", "Keep the key out of logs; the API takes it only as `api_key` in the URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.4 } ], "editorialScores": { "ergonomics": 69, "maintenance": 70, "payments": 35, "reliability": 75, "schema": 54, "security": 65, "transparency": 59 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.zerobounce.net/v2/validate?api_key=$ZEROBOUNCE_API_KEY\u0026email=valid@example.com\"" }, "letme": { "capability": "https://letme.dev/email.verification", "tool": "https://letme.dev/zerobounce" }, "area": "web-data", "unitPrices": [ { "item": "Email validation, smallest pay-as-you-go pack", "unit": "call", "usd": 0.0195, "note": "$39 for 2,000 validations" }, { "item": "ZeroBounce ONE", "unit": "month", "usd": 99, "note": "From $99 a month" } ], "provenance": { "legalEntity": "Hertza L.L.C.", "domain": "zerobounce.net", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zerobounce.net/terms-of-use", "privacy": "https://www.zerobounce.net/privacy-policy", "statusPage": "https://status.zerobounce.net", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-06", "notes": [ "Terms of use name Hertza L.L.C., doing business as ZeroBounce, a Nevada LLC, under Nevada law; the terms take effect on the date accepted. Privacy policy last updated 30 June 2026.", "www.zerobounce.net/robots.txt allows all and names ClaudeBot as allowed. status.zerobounce.net disallows /api/ and /embed/; its history was read from history.rss.", "No public changelog for the API was found.", "security.txt was not checked." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zerobounce.json", "live": { "slug": "zerobounce", "probe": { "target": "https://api.zerobounce.net/v2", "method": "get", "lastAt": "2026-11-07T22:56:32.424648348Z", "lastOk": true, "lastStatus": 404, "lastMs": 63, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 77, "p95ms24h": 170, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.zerobounce.net", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:57:55.637238875Z" }, "versions": [ { "registry": "npm", "name": "@zerobounce/zero-bounce-sdk", "version": "3.0.0", "seenAt": "2026-11-07T00:19:09.899173295Z" } ], "npmWeekly": 36734, "securityTxt": { "url": "https://zerobounce.net/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:52.305113224Z" }, "llmsTxt": { "url": "https://www.zerobounce.net/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:27.000344109Z" }, "pages": [ { "url": "https://www.zerobounce.net/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:37:41.302855774Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6cbf992fb3f3" }, { "url": "https://www.zerobounce.net/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:37:45.799553831Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6267cfec1592" }, { "url": "https://www.zerobounce.net/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:45.965675933Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "08727e5bbf09" } ], "updatedAt": "2026-11-07T22:57:55.637238875Z" } }, "edges": [ { "by": 69, "category": "ergonomics", "leads": "zerobounce", "name": "Agent ergonomics", "reasons": { "a": "Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).", "b": "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." }, "scores": { "a": 0, "b": 69 } }, { "by": 66, "category": "maintenance", "leads": "zerobounce", "name": "Maintenance \u0026 community", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 4, "b": 70 } }, { "by": 57, "category": "security", "leads": "zerobounce", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 8, "b": 65 } }, { "by": 54, "category": "schema", "leads": "zerobounce", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 0, "b": 54 } }, { "by": 45, "category": "reliability", "leads": "zerobounce", "name": "Reliability", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 30, "b": 75 } }, { "by": 35, "category": "payments", "leads": "zerobounce", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 0, "b": 35 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HubSpot, Inc.", "b": "Hertza L.L.C. (ZeroBounce)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.zerobounce.net/v2", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand", "b": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2025-12-08", "b": "2026-10-25", "name": "Last release" }, { "a": "2025-05-30", "b": "2026-05-05", "name": "Terms last updated" }, { "a": "2026-08-31", "b": "2026-06-30", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 trust.", "question": "Which is better for AI agents, Clearbit or ZeroBounce?" }, { "answer": "Both need an API key.", "question": "Do Clearbit and ZeroBounce need an API key?" }, { "answer": "No hosted endpoint is listed for Clearbit. ZeroBounce has a hosted endpoint at https://api.zerobounce.net/v2.", "question": "Can an agent call Clearbit and ZeroBounce without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 73 against 63" ], "also": null, "goodFor": "Only for teams that already hold a Clearbit contract.", "slug": "clearbit", "watchFor": "No public API or MCP server an outside agent can call" }, { "aheadOn": [ "Reliability, 75 against 30", "Schema \u0026 documentation, 54 against 0", "Agent ergonomics, 69 against 0", "Security \u0026 auth, 65 against 8", "Payments \u0026 pricing, 35 against 0", "Maintenance \u0026 community, 70 against 4" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "Email verification before outreach, the verification-first listing in lead-data.", "slug": "zerobounce", "watchFor": "Every documented example sends the key as an `api_key` query parameter" } ], "history": { "clearbit": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 14.2, "fromGrade": "F", "to": 14.1, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 14.1, "fromGrade": "F", "to": 14.2, "toGrade": "F" }, { "causes": [ "evidence" ], "date": "2026-10-17", "delta": 0.6, "from": 13.5, "fromGrade": "F", "to": 14.1, "toGrade": "F" } ], "zerobounce": null }, "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-clearbit.json", "title": "Apollo API + MCP vs Clearbit", "url": "https://www.anchorterminal.com/compare/apollo-vs-clearbit" }, { "json": "https://www.anchorterminal.com/compare/apollo-vs-zerobounce.json", "title": "Apollo API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/apollo-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-clearbit.json", "title": "Clay vs Clearbit", "url": "https://www.anchorterminal.com/compare/clay-vs-clearbit" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-zerobounce.json", "title": "Clay vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/clay-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal.json", "title": "Clearbit vs Coresignal API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-crustdata.json", "title": "Clearbit vs Crustdata API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-crustdata" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-databar.json", "title": "Clearbit vs Databar", "url": "https://www.anchorterminal.com/compare/clearbit-vs-databar" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-dievio.json", "title": "Clearbit vs Dievio", "url": "https://www.anchorterminal.com/compare/clearbit-vs-dievio" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.json", "title": "Clearbit vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer.json", "title": "Clearbit vs Enrich Layer API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.json", "title": "Clearbit vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.json", "title": "Clearbit vs FullContact", "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.json", "title": "Clearbit vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.json", "title": "Clearbit vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-gojiberry.json", "title": "Clearbit vs Gojiberry", "url": "https://www.anchorterminal.com/compare/clearbit-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-hunter.json", "title": "Clearbit vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-leadmagic.json", "title": "Clearbit vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-lusha.json", "title": "Clearbit vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.json", "title": "Clearbit vs People Data Labs", "url": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-prospeo.json", "title": "Clearbit vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-rocketreach.json", "title": "Clearbit vs RocketReach API", "url": "https://www.anchorterminal.com/compare/clearbit-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-zoominfo.json", "title": "Clearbit vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-zoominfo" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.json", "title": "Coresignal API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.json", "title": "Crustdata API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/databar-vs-zerobounce.json", "title": "Databar vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/databar-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce.json", "title": "Dievio vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.json", "title": "Dropcontact API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.json", "title": "Enrich Layer API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.json", "title": "Explorium AgentSource vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.json", "title": "FullContact vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json", "title": "FullEnrich API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.json", "title": "Gojiberry vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.json", "title": "Lusha API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.json", "title": "People Data Labs vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.json", "title": "Prospeo API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.json", "title": "ZeroBounce vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo" }, { "json": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce.json", "title": "Hunter API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.json", "title": "Fuse MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.json", "title": "LeadMagic API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.json", "title": "RocketReach API vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce" } ], "panel": null, "scores": [ { "by": 45, "clearbit": 30, "edge": "zerobounce", "key": "reliability", "name": "Reliability", "weight": 16, "zerobounce": 75 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 54, "clearbit": 0, "edge": "zerobounce", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zerobounce": 54 }, { "by": 69, "clearbit": 0, "edge": "zerobounce", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zerobounce": 69 }, { "by": 57, "clearbit": 8, "edge": "zerobounce", "key": "security", "name": "Security \u0026 auth", "weight": 14, "zerobounce": 65 }, { "by": 35, "clearbit": 0, "edge": "zerobounce", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zerobounce": 35 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 66, "clearbit": 4, "edge": "zerobounce", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zerobounce": 70 }, { "by": 10, "clearbit": 73, "edge": "clearbit", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zerobounce": 63 } ], "summary": "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 \u0026 trust. Both do lead enrichment.", "tasks": null, "tutorials": [], "verdicts": { "clearbit": "There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.", "zerobounce": "ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce", "json": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.min.md" }, "markdown": "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 \u0026 trust. Both do lead enrichment.\n\n- Clearbit: grade F, 14.1/100, rank #1482 of 1510. Markdown https://www.anchorterminal.com/tools/clearbit.md · JSON https://www.anchorterminal.com/api/v1/tools/clearbit.json\n- ZeroBounce: grade B, 62.4/100, rank #561 of 1510. Markdown https://www.anchorterminal.com/tools/zerobounce.md · JSON https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 231 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Clearbit (F)\n\nGood for: Only for teams that already hold a Clearbit contract.\n\nAhead on:\n- Transparency \u0026 trust, 73 against 63\n\nWatch for: No public API or MCP server an outside agent can call\n\n### ZeroBounce (B)\n\nGood for: Email verification before outreach, the verification-first listing in lead-data.\n\nAhead on:\n- Reliability, 75 against 30\n- Schema \u0026 documentation, 54 against 0\n- Agent ergonomics, 69 against 0\n- Security \u0026 auth, 65 against 8\n- Payments \u0026 pricing, 35 against 0\n- Maintenance \u0026 community, 70 against 4\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Every documented example sends the key as an `api_key` query parameter\n\n\n## Why the edge\n\n### Agent ergonomics: ZeroBounce +69\n\n- Clearbit (0): Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).\n- 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.\n\n### Maintenance \u0026 community: ZeroBounce +66\n\n- 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).\n- 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.\n\n### Security \u0026 auth: ZeroBounce +57\n\n- 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).\n- 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.\n\n### Schema \u0026 documentation: ZeroBounce +54\n\n- 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.\n- 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.\n\n### Reliability: ZeroBounce +45\n\n- 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).\n- 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.\n\n### Payments \u0026 pricing: ZeroBounce +35\n\n- 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).\n- 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.\n\n## Score by category\n\n| Category | Weight | Clearbit | ZeroBounce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 30 | 75 | ZeroBounce +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 0 | 54 | ZeroBounce +54 |\n| Agent ergonomics | 13% (16.2 this run) | 0 | 69 | ZeroBounce +69 |\n| Security \u0026 auth | 14% (17.5 this run) | 8 | 65 | ZeroBounce +57 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 35 | ZeroBounce +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 4 | 70 | ZeroBounce +66 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 63 | Clearbit +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **14.1 · F** | **62.4 · B** | |\n\n## Facts side by side\n\n| Fact | Clearbit | ZeroBounce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HubSpot, Inc. | Hertza L.L.C. (ZeroBounce) |\n| Hosted endpoint | no (local only) | `https://api.zerobounce.net/v2` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| 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 |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2025-12-08 | 2026-10-25 |\n| Terms last updated | 2025-05-30 | 2026-05-05 |\n| Privacy policy last updated | 2026-08-31 | 2026-06-30 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Agent reviews | 1.5/5 (4) | none |\n\n## How the scores have moved\n\n### Clearbit\n\n- -0.1 on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n- +0.6 on 17 October 2026: new evidence\n\n### ZeroBounce\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Clearbit.** There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.\n\n**ZeroBounce.** ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract.\n\n## Before you call either\n\n### Clearbit\n\n1. Don't plan to call Clearbit. Hand the task to a person with an existing Clearbit account, or use HubSpot's Breeze Intelligence through HubSpot\n2. Replace logo.clearbit.com links, which stopped working after 8 December 2025\n\n### ZeroBounce\n\n1. Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits\n2. Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later\n3. Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour\n4. Use the bulk file API for large lists instead of looping on /v2/validate\n5. Keep the key out of logs; the API takes it only as `api_key` in the URL\n\n## Questions\n\n### Which is better for AI agents, Clearbit or ZeroBounce?\n\nZeroBounce 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 \u0026 trust.\n\n### Do Clearbit and ZeroBounce need an API key?\n\nBoth need an API key.\n\n### Can an agent call Clearbit and ZeroBounce without installing anything?\n\nNo hosted endpoint is listed for Clearbit. ZeroBounce has a hosted endpoint at https://api.zerobounce.net/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clearbit\", \"b\": \"zerobounce\"}`. From a terminal: `anchor compare clearbit zerobounce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clearbit.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n\n## Other comparisons with Clearbit or ZeroBounce\n\n- [Apollo API + MCP vs Clearbit](https://www.anchorterminal.com/compare/apollo-vs-clearbit.md)\n- [Apollo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)\n- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)\n- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)\n- [Clearbit vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-coresignal.md)\n- [Clearbit vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-crustdata.md)\n- [Clearbit vs Databar](https://www.anchorterminal.com/compare/clearbit-vs-databar.md)\n- [Clearbit vs Dievio](https://www.anchorterminal.com/compare/clearbit-vs-dievio.md)\n- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)\n- [Clearbit vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer.md)\n- [Clearbit vs Explorium AgentSource](https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.md)\n- [Clearbit vs FullContact](https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.md)\n- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.md)\n- [Clearbit vs Fuse MCP](https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.md)\n- [Clearbit vs Gojiberry](https://www.anchorterminal.com/compare/clearbit-vs-gojiberry.md)\n- [Clearbit vs Hunter API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-hunter.md)\n- [Clearbit vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-leadmagic.md)\n- [Clearbit vs Lusha API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-lusha.md)\n- [Clearbit vs People Data Labs](https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.md)\n- [Clearbit vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-prospeo.md)\n- [Clearbit vs RocketReach API](https://www.anchorterminal.com/compare/clearbit-vs-rocketreach.md)\n- [Clearbit vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-zoominfo.md)\n- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)\n- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)\n- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)\n- [Dievio vs ZeroBounce](https://www.anchorterminal.com/compare/dievio-vs-zerobounce.md)\n- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)\n- [Enrich Layer API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.md)\n- [Explorium AgentSource vs ZeroBounce](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md)\n- [FullContact vs ZeroBounce](https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.md)\n- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)\n- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)\n- [Lusha API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md)\n- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)\n- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)\n- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)\n- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.md)\n- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)\n- [LeadMagic API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md)\n- [RocketReach API vs ZeroBounce](https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Clearbit vs ZeroBounce", "url": "" } ], "description": "ZeroBounce scores 62.4 (B) to Clearbit's 14.1 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clearbit F 14.1", "ZeroBounce B 62.4", "scores" ], "h1": "Clearbit vs ZeroBounce", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/clearbit-vs-zerobounce", "published": "2026-10-01", "section": "tools", "title": "Clearbit vs ZeroBounce for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce" }, "tokens": { "markdown": 4100, "slim": 2030 }, "version": 1 }