{ "data": { "a": { "slug": "lusha", "name": "Lusha API + MCP", "vendor": "Lusha", "vendorUrl": "https://www.lusha.com", "kind": "http-api", "category": "lead-data", "summary": "Contact and company enrichment, filter-based prospecting, lookalikes, job-change and company signals, and webhooks over a versioned REST API with OpenAPI files.", "url": "https://www.anchorterminal.com/tools/lusha", "markdownUrl": "https://www.anchorterminal.com/tools/lusha.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lusha.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lusha.json", "dns": "lusha.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.lusha.com", "packages": [], "auth": "mixed", "authNotes": "REST calls take an `api_key` header (lowercase, underscore). Keys belong to users and can carry per-key credit caps set by admins. The hosted MCP server at https://mcp.lusha.com takes OAuth in chat clients or an x-api-key header elsewhere. Webhooks are signed with HMAC-SHA256.", "pricing": "freemium", "pricingNotes": "Free plan with 40 credits a month. Starter $49.90 a month for 400 credits, Pro $69.90 for 600, Premium $399.90 for 3,400, with about 25 per cent off billed yearly, and Scale on quote. An email costs 1 credit, a phone 5 and company data 1, plus 1 credit per request (per 25 results in bulk), charged even when nothing matches (https://www.lusha.com/pricing/).", "priceSummary": "$49.90 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 50, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.lusha.com", "llmsTxt": "https://docs.lusha.com/llms.txt", "openapi": "https://docs.lusha.com/openapi.json", "registryName": "com.lusha.mcp/mcp", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.person", "data.company" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "webhooks", "closed-source", "enterprise", "lead-search", "enrichment" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 62.3, "grade": "B", "agentReady": false, "rank": 565, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 51, "maintenance": 82, "payments": 40, "reliability": 85, "schema": 83, "security": 59, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -6, "negativeNotes": [ "On 2026-09-04 version 2.8.0 retired the Decision Makers API, launched on 2026-06-08 in 2.4.0, and removed it from the reference in a minor version with no notice period found; on 2026-03-10 version 2.2.0 renamed Contact Lookalikes V3 result fields (`id` to `contactId` and `companyId`) in a minor version. Breaking changes in minor versions without notice, folded into one term, -3 (https://docs.lusha.com/changelog/overview)", "On 2026-10-05 version 2.17.0 changed `POST /v3/contacts/enrich` for accounts with Data Waterfall on. A slower provider no longer holds the request open, and the response returns what is known plus a `job` to poll for the rest. Existing callers that don't poll receive less in the enrich answer. Announced the day it took effect, -3 (https://docs.lusha.com/changelog/overview)" ], "verdict": "API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.", "bestFor": "Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.", "strengths": [ "API key on every plan, including Free with 40 credits a month", "Admins can cap each key's monthly credits", "Fourteen dated releases between 5 August and 29 October 2026", "Privacy notice names sources, a DPO and an EU representative, with a removal page and subprocessor list", "SOC 2 Type II and a 99.95 per cent uptime SLA stated in the trust centre" ], "weaknesses": [ "At least 1 credit per request even when nothing matches", "Decision Makers API removed 88 days after launch and Contact Lookalikes fields renamed, both in minor versions, and the October 2026 async enrich change was announced the day it shipped", "50 MCP tools with no toolsets or read-only mode, including table writes and CRM export", "Free plan capped at 100 requests a day", "Contact data partly comes from members' shared CRM, email and calendar data" ], "agentNotes": [ "Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact", "Ask for phones only when needed. A phone is 5 credits against 1 for an email", "Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04", "When Enrich Contacts returns a `job`, poll `GET /v3/contacts/jobs/{jobId}` every `retryAfter` seconds until `complete`, `expired` or `failed`. Polling costs no credits", "Back off exponentially on 429. Free keys stop at 100 requests a day" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "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.3 } ], "editorialScores": { "ergonomics": 51, "maintenance": 82, "payments": 40, "reliability": 85, "schema": 83, "security": 59, "transparency": 67 }, "provenanceScore": 93, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.lusha.com/account/usage -H \"api_key: $LUSHA_API_KEY\"", "claudeCode": "claude mcp add --transport http lusha https://mcp.lusha.com", "config": { "mcpServers": { "lusha": { "headers": { "x-api-key": "${LUSHA_API_KEY}" }, "url": "https://mcp.lusha.com" } } } }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/lusha" }, "area": "web-data", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 49.9, "note": "400 credits" }, { "item": "Pro", "unit": "month", "usd": 69.9, "note": "600 credits" }, { "item": "Premium", "unit": "month", "usd": 399.9, "note": "3,400 credits" } ], "provenance": { "legalEntity": "Lusha Systems Inc.", "domain": "lusha.com", "domainRegistered": "1999-07-09", "endpointOnVendorDomain": true, "terms": "https://www.lusha.com/legal/terms_and_conditions-2/", "privacy": "https://www.lusha.com/legal/privacy_policy/", "statusPage": "https://status.lusha.com", "changelog": "https://docs.lusha.com/changelog/overview", "securityTxt": "valid", "checked": "2026-11-02", "notes": [ "lusha.com was registered in 1999, long before Lusha was founded. The Delaware entity works with its Israeli affiliate Lusha Systems Ltd.", "The privacy notice now lives at /legal/privacy-notice/; the recorded /legal/privacy_policy/ address reaches it through same-host redirects, and it says it was last updated in September 2026.", "www.lusha.com/.well-known/security.txt names security@lusha.com and expires on 2027-05-01.", "www.lusha.com's robots.txt carries `Content-Signal: ai-train=no, search=yes, ai-input=yes`; docs.lusha.com's carries `ai-train=yes, search=yes, ai-input=yes`." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lusha.json", "live": { "slug": "lusha", "probe": { "target": "https://api.lusha.com", "method": "get", "lastAt": "2026-11-07T19:22:17.487480857Z", "lastOk": true, "lastStatus": 404, "lastMs": 554, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 389, "p95ms24h": 500, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.lusha.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:26.833835792Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.lusha.mcp/mcp", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "securityTxt": { "url": "https://lusha.com/.well-known/security.txt", "state": "valid", "expires": "2027-05-01T14:48:00Z", "checkedAt": "2026-11-07T16:00:38.106845604Z" }, "llmsTxt": { "url": "https://docs.lusha.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:56.919729379Z" }, "domain": { "domain": "lusha.com", "registered": "1999-07-09", "source": "https://rdap.verisign.com/com/v1/domain/lusha.com", "checkedAt": "2026-11-01T14:08:50.198673442Z" }, "pages": [ { "url": "https://docs.lusha.com/changelog/overview", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:54.444588923Z", "changedAt": "2026-11-06T13:29:16.229341386Z", "fingerprint": "15894316186d" }, { "url": "https://www.lusha.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:31:06.951465621Z", "changedAt": "2026-10-31T06:29:24.45606821Z", "fingerprint": "9cc9d38d4fe9" }, { "url": "https://www.lusha.com/legal/privacy_policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:02.501465802Z", "changedAt": "2026-10-31T06:29:19.935209508Z", "fingerprint": "d8c3dca889ee" }, { "url": "https://www.lusha.com/legal/terms_and_conditions-2/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:05.276784613Z", "changedAt": "2026-11-05T13:14:38.066932319Z", "fingerprint": "59a6baefa29a" } ], "mcpTools": { "url": "https://mcp.lusha.com", "checkedAt": "2026-11-07T01:46:03.635166165Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:03.635166165Z" }, "updatedAt": "2026-11-07T19:22:17.487480857Z" } }, "answer": "ZeroBounce and Lusha API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.3 (B). Lusha API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and 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-07T19:22:46.255334057Z", "lastOk": true, "lastStatus": 404, "lastMs": 94, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 70, "p95ms24h": 170, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.zerobounce.net", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:24:02.77448048Z" }, "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-07T19:24:02.77448048Z" } }, "edges": [ { "by": 29, "category": "schema", "leads": "lusha", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI files per the 30 September check (25). llms.txt (10). Reference pages explain credit use per call with worked examples (15 of 20). Typed inputs (12 of 15). Standard HTTP codes and examples, no error catalogue found (10 of 15). Semantic versioning with a support matrix and a dated changelog. Version numbers run out of order (2.8.0 dated after 2.12.0), and breaking changes shipped in minor versions (11 of 15).", "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": 83, "b": 54 } }, { "by": 18, "category": "ergonomics", "leads": "zerobounce", "name": "Agent ergonomics", "reasons": { "a": "The hosted MCP has 50 tools across enrichment, prospecting, signals, lookalikes, buying groups, tables, CRM export and account, with no toolsets found (5). Bulk calls take up to 25 records (8 of 25). Prospecting filters with a per-company cap and exact totals (18 of 20). Standard codes and back-off advice for 429 (12 of 20). Every request costs at least 1 credit even with no match, so retries aren't free, and the MCP writes to tables and CRM exports with no annotations found (6 of 20). No official SDKs found (7 of 15).", "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": 51, "b": 69 } }, { "by": 17, "category": "transparency", "leads": "lusha", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with terms naming Lusha Systems Inc. (15). The privacy notice (September 2026) covers people in the database, names its sources, including a community programme in which members share contacts from their CRM, email headers and calendars, plus data brokers and public APIs, relies on legitimate interest, names a DPO and an EU and UK representative, and takes removal requests at `lusha.com/privacy-center/request-removal`. Retention for contacts has no period (24 of 30). A support matrix exists, but the Decision Makers API was removed 88 days after launch with no notice period found (8 of 20). Subprocessor list published and data stored on AWS in the US (20).", "b": "Closed service under terms naming Hertza L.L.C. (ZeroBounce) of Nevada; SDKs and MCP server open source (15 of 30). The data protection page says uploaded data is never kept more than 30 days, the privacy policy of 30 June 2026 keeps account data 'as long as needed', and EU and UK DPAs are published (22 of 30). An API migration page, with no dated deprecation policy (6 of 20). A sub-processor list naming each provider and the data exchanged (16 of 20). 15+22+6+16 = 59." }, "scores": { "a": 80, "b": 63 } }, { "by": 12, "category": "maintenance", "leads": "lusha", "name": "Maintenance \u0026 community", "reasons": { "a": "Version 2.20.1 on 2026-10-29 (30). Fourteen dated versions from 2.7.0 on 5 August to 2.20.1 on 29 October 2026 (20). Detailed public changelog and support, issue handling not visible (12 of 15). Listed in the official MCP registry as com.lusha.mcp/mcp 1.0.0, a domain-verified namespace, active since 18 June 2026 (15). No packages to judge (5 of 10). 30+20+12+15+5 = 82.", "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": 82, "b": 70 } }, { "by": 10, "category": "reliability", "leads": "lusha", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status.lusha.com with a Lusha API component and AWS us-east-1 components (20). The history feed (history.atom) lists one incident from 4 August to 2 November 2026, errors and incomplete results in Prospecting company search for some users on 7 August (20:44 to 21:33 IDT), partial and so minor; the 3 August API error incident falls just outside the window (20). Limits per plan, from 40 a minute and 100 a day on Free to 300 a minute and 50,000 a day on Scale (15). 429 documented with advice to back off exponentially, no Retry-After mentioned (10 of 15). The trust centre states a 99.95 per cent uptime SLA (10). Generally available (10). 20+20+15+10+10+10 = 85.", "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": 85, "b": 75 } }, { "by": 6, "category": "security", "leads": "zerobounce", "name": "Security \u0026 auth", "reasons": { "a": "REST takes an `api_key` header. Every user gets a key, admins can mint more and cap each one's monthly credits, and a key a user makes for themselves has no cap of its own. OAuth for the MCP in Claude, ChatGPT and Codex, `x-api-key` elsewhere. No endpoint scopes found (22 of 30). Credit caps limit damage, but the MCP isn't read-only and writes to workspace tables and CRM exports (8 of 20). Signals and conversation data carry some free text, no injection guidance found (5 of 15). Usage endpoint, no per-call log found (8 of 15). SOC 2 Type II and five ISO certifications claimed in the trust centre, ISO 27701 named in the privacy notice, security.txt valid (Expires 1 May 2027, read on 2 November), no bug bounty found (16 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": 59, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Lusha", "b": "Hertza L.L.C. (ZeroBounce)", "name": "Vendor" }, { "a": "https://api.lusha.com", "b": "https://api.zerobounce.net/v2", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "name": "Licence" }, { "a": "50", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.lusha.mcp/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-29", "b": "2026-10-25", "name": "Last release" }, { "a": "no date given", "b": "2026-05-05", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-06-30", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "ZeroBounce and Lusha API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.3 (B). Lusha API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Lusha API + MCP or ZeroBounce?" }, { "answer": "Lusha API + MCP takes an API key or an OAuth sign-in. ZeroBounce needs an API key.", "question": "Do Lusha API + MCP and ZeroBounce need an API key?" }, { "answer": "Yes. Lusha API + MCP has a hosted endpoint at https://api.lusha.com and ZeroBounce at https://api.zerobounce.net/v2.", "question": "Can an agent call Lusha API + MCP and ZeroBounce without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 75", "Schema \u0026 documentation, 83 against 54", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 82 against 70", "Transparency \u0026 trust, 80 against 63" ], "also": null, "goodFor": "Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.", "slug": "lusha", "watchFor": "At least 1 credit per request even when nothing matches" }, { "aheadOn": [ "Agent ergonomics, 69 against 51", "Security \u0026 auth, 65 against 59" ], "also": [ "Runs on your own machine", "No incidents deducted, where Lusha API + MCP loses 6 points for them" ], "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": { "lusha": [ { "causes": [ "evidence", "event" ], "date": "2026-11-02", "delta": 0, "from": 62.3, "fromGrade": "B", "to": 62.3, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 62.6, "fromGrade": "B", "to": 62.3, "toGrade": "B" } ], "zerobounce": null }, "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-lusha.json", "title": "Apollo API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/apollo-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-lusha.json", "title": "Clay vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-lusha.json", "title": "Coresignal API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-lusha.json", "title": "Crustdata API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/crustdata-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/dievio-vs-lusha.json", "title": "Dievio vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/dievio-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-lusha.json", "title": "Enrich Layer API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha.json", "title": "Explorium AgentSource vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha.json", "title": "FullEnrich API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha.json", "title": "Fuse MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/gojiberry-vs-lusha.json", "title": "Gojiberry vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/gojiberry-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/leadmagic-vs-lusha.json", "title": "LeadMagic API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/leadmagic-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-people-data-labs.json", "title": "Lusha API + MCP vs People Data Labs", "url": "https://www.anchorterminal.com/compare/lusha-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-prospeo.json", "title": "Lusha API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/lusha-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-rocketreach.json", "title": "Lusha API + MCP vs RocketReach API", "url": "https://www.anchorterminal.com/compare/lusha-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-zoominfo.json", "title": "Lusha API + MCP vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/lusha-vs-zoominfo" }, { "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-zerobounce.json", "title": "Clay vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/clay-vs-zerobounce" }, { "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-zerobounce.json", "title": "Clearbit vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce" }, { "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-lusha.json", "title": "Databar vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/databar-vs-lusha" }, { "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-lusha.json", "title": "Dropcontact API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha" }, { "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-lusha.json", "title": "FullContact vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-lusha" }, { "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/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-lusha.json", "title": "Hunter API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/hunter-vs-lusha" }, { "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": 10, "edge": "lusha", "key": "reliability", "lusha": 85, "name": "Reliability", "weight": 16, "zerobounce": 75 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 29, "edge": "lusha", "key": "schema", "lusha": 83, "name": "Schema \u0026 documentation", "weight": 13, "zerobounce": 54 }, { "by": 18, "edge": "zerobounce", "key": "ergonomics", "lusha": 51, "name": "Agent ergonomics", "weight": 13, "zerobounce": 69 }, { "by": 6, "edge": "zerobounce", "key": "security", "lusha": 59, "name": "Security \u0026 auth", "weight": 14, "zerobounce": 65 }, { "by": 5, "edge": "lusha", "key": "payments", "lusha": 40, "name": "Payments \u0026 pricing", "weight": 10, "zerobounce": 35 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "lusha", "key": "maintenance", "lusha": 82, "name": "Maintenance \u0026 community", "weight": 7, "zerobounce": 70 }, { "by": 17, "edge": "lusha", "key": "transparency", "lusha": 80, "name": "Transparency \u0026 trust", "weight": 7, "zerobounce": 63 } ], "summary": "ZeroBounce and Lusha API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.3 (B). Lusha API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do lead enrichment.", "tasks": null, "tutorials": [], "verdicts": { "lusha": "API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.", "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/lusha-vs-zerobounce", "json": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.min.md" }, "markdown": "ZeroBounce and Lusha API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.3 (B). Lusha API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust. Both do lead enrichment.\n\n- Lusha API + MCP: grade B, 62.3/100, rank #565 of 1510. Markdown https://www.anchorterminal.com/tools/lusha.md · JSON https://www.anchorterminal.com/api/v1/tools/lusha.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### Lusha API + MCP (B)\n\nGood for: Sales teams that want contact and company enrichment, signals and prospecting from one vendor, with a free plan to start.\n\nAhead on:\n- Reliability, 85 against 75\n- Schema \u0026 documentation, 83 against 54\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 82 against 70\n- Transparency \u0026 trust, 80 against 63\n\nWatch for: At least 1 credit per request even when nothing matches\n\n### ZeroBounce (B)\n\nGood for: Email verification before outreach, the verification-first listing in lead-data.\n\nAhead on:\n- Agent ergonomics, 69 against 51\n- Security \u0026 auth, 65 against 59\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Lusha API + MCP loses 6 points for them\n\nWatch for: Every documented example sends the key as an `api_key` query parameter\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Lusha API + MCP +29\n\n- Lusha API + MCP (83): OpenAPI files per the 30 September check (25). llms.txt (10). Reference pages explain credit use per call with worked examples (15 of 20). Typed inputs (12 of 15). Standard HTTP codes and examples, no error catalogue found (10 of 15). Semantic versioning with a support matrix and a dated changelog. Version numbers run out of order (2.8.0 dated after 2.12.0), and breaking changes shipped in minor versions (11 of 15).\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### Agent ergonomics: ZeroBounce +18\n\n- Lusha API + MCP (51): The hosted MCP has 50 tools across enrichment, prospecting, signals, lookalikes, buying groups, tables, CRM export and account, with no toolsets found (5). Bulk calls take up to 25 records (8 of 25). Prospecting filters with a per-company cap and exact totals (18 of 20). Standard codes and back-off advice for 429 (12 of 20). Every request costs at least 1 credit even with no match, so retries aren't free, and the MCP writes to tables and CRM exports with no annotations found (6 of 20). No official SDKs found (7 of 15).\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### Transparency \u0026 trust: Lusha API + MCP +17\n\n- Lusha API + MCP (80): Closed service with terms naming Lusha Systems Inc. (15). The privacy notice (September 2026) covers people in the database, names its sources, including a community programme in which members share contacts from their CRM, email headers and calendars, plus data brokers and public APIs, relies on legitimate interest, names a DPO and an EU and UK representative, and takes removal requests at `lusha.com/privacy-center/request-removal`. Retention for contacts has no period (24 of 30). A support matrix exists, but the Decision Makers API was removed 88 days after launch with no notice period found (8 of 20). Subprocessor list published and data stored on AWS in the US (20).\n- ZeroBounce (63): Closed service under terms naming Hertza L.L.C. (ZeroBounce) of Nevada; SDKs and MCP server open source (15 of 30). The data protection page says uploaded data is never kept more than 30 days, the privacy policy of 30 June 2026 keeps account data 'as long as needed', and EU and UK DPAs are published (22 of 30). An API migration page, with no dated deprecation policy (6 of 20). A sub-processor list naming each provider and the data exchanged (16 of 20). 15+22+6+16 = 59.\n\n### Maintenance \u0026 community: Lusha API + MCP +12\n\n- Lusha API + MCP (82): Version 2.20.1 on 2026-10-29 (30). Fourteen dated versions from 2.7.0 on 5 August to 2.20.1 on 29 October 2026 (20). Detailed public changelog and support, issue handling not visible (12 of 15). Listed in the official MCP registry as com.lusha.mcp/mcp 1.0.0, a domain-verified namespace, active since 18 June 2026 (15). No packages to judge (5 of 10). 30+20+12+15+5 = 82.\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### Reliability: Lusha API + MCP +10\n\n- Lusha API + MCP (85): Atlassian Statuspage at status.lusha.com with a Lusha API component and AWS us-east-1 components (20). The history feed (history.atom) lists one incident from 4 August to 2 November 2026, errors and incomplete results in Prospecting company search for some users on 7 August (20:44 to 21:33 IDT), partial and so minor; the 3 August API error incident falls just outside the window (20). Limits per plan, from 40 a minute and 100 a day on Free to 300 a minute and 50,000 a day on Scale (15). 429 documented with advice to back off exponentially, no Retry-After mentioned (10 of 15). The trust centre states a 99.95 per cent uptime SLA (10). Generally available (10). 20+20+15+10+10+10 = 85.\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### Security \u0026 auth: ZeroBounce +6\n\n- Lusha API + MCP (59): REST takes an `api_key` header. Every user gets a key, admins can mint more and cap each one's monthly credits, and a key a user makes for themselves has no cap of its own. OAuth for the MCP in Claude, ChatGPT and Codex, `x-api-key` elsewhere. No endpoint scopes found (22 of 30). Credit caps limit damage, but the MCP isn't read-only and writes to workspace tables and CRM exports (8 of 20). Signals and conversation data carry some free text, no injection guidance found (5 of 15). Usage endpoint, no per-call log found (8 of 15). SOC 2 Type II and five ISO certifications claimed in the trust centre, ISO 27701 named in the privacy notice, security.txt valid (Expires 1 May 2027, read on 2 November), no bug bounty found (16 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## Score by category\n\n| Category | Weight | Lusha API + MCP | ZeroBounce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 75 | Lusha API + MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 54 | Lusha API + MCP +29 |\n| Agent ergonomics | 13% (16.2 this run) | 51 | 69 | ZeroBounce +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 59 | 65 | ZeroBounce +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Lusha API + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 70 | Lusha API + MCP +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 63 | Lusha API + MCP +17 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **62.3 · B** | **62.4 · B** | |\n\n## Facts side by side\n\n| Fact | Lusha API + MCP | ZeroBounce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lusha | Hertza L.L.C. (ZeroBounce) |\n| Hosted endpoint | `https://api.lusha.com` | `https://api.zerobounce.net/v2` |\n| Transports | HTTP, Streamable HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |\n| Tools exposed | 50 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.lusha.mcp/mcp` | not listed |\n| Last release | 2026-10-29 | 2026-10-25 |\n| Terms last updated | no date given | 2026-05-05 |\n| Privacy policy last updated | 2026-09-01 | 2026-06-30 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Lusha API + MCP\n\n- no change on 2 November 2026: new evidence, negative event\n- -0.3 on 8 October 2026: checklist\n\n### ZeroBounce\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Lusha API + MCP.** API key on every plan, including Free with 40 credits a month, and a semantic-versioned changelog with frequent dated releases. At least 1 credit is charged per request even when nothing matches, and since 5 October 2026 Enrich Contacts can return partial waterfall results with a job to poll, a change announced the day it shipped.\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### Lusha API + MCP\n\n1. Batch up to 25 contacts a request. A single bulk request costs 1 credit, not 1 per contact\n2. Ask for phones only when needed. A phone is 5 credits against 1 for an email\n3. Use the Buying Group endpoint. Decision Makers was retired on 2026-09-04\n4. When Enrich Contacts returns a `job`, poll `GET /v3/contacts/jobs/{jobId}` every `retryAfter` seconds until `complete`, `expired` or `failed`. Polling costs no credits\n5. Back off exponentially on 429. Free keys stop at 100 requests a day\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, Lusha API + MCP or ZeroBounce?\n\nZeroBounce and Lusha API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.3 (B). Lusha API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Lusha API + MCP and ZeroBounce need an API key?\n\nLusha API + MCP takes an API key or an OAuth sign-in. ZeroBounce needs an API key.\n\n### Can an agent call Lusha API + MCP and ZeroBounce without installing anything?\n\nYes. Lusha API + MCP has a hosted endpoint at https://api.lusha.com and ZeroBounce at https://api.zerobounce.net/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lusha-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lusha-vs-zerobounce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lusha\", \"b\": \"zerobounce\"}`. From a terminal: `anchor compare lusha zerobounce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lusha.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n\n## Other comparisons with Lusha API + MCP or ZeroBounce\n\n- [Apollo API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/apollo-vs-lusha.md)\n- [Clay vs Lusha API + MCP](https://www.anchorterminal.com/compare/clay-vs-lusha.md)\n- [Coresignal API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-lusha.md)\n- [Crustdata API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-lusha.md)\n- [Dievio vs Lusha API + MCP](https://www.anchorterminal.com/compare/dievio-vs-lusha.md)\n- [Enrich Layer API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-lusha.md)\n- [Explorium AgentSource vs Lusha API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha.md)\n- [FullEnrich API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-lusha.md)\n- [Fuse MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-lusha.md)\n- [Gojiberry vs Lusha API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-lusha.md)\n- [LeadMagic API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/leadmagic-vs-lusha.md)\n- [Lusha API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/lusha-vs-people-data-labs.md)\n- [Lusha API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-prospeo.md)\n- [Lusha API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/lusha-vs-rocketreach.md)\n- [Lusha API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-zoominfo.md)\n- [Apollo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)\n- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)\n- [Clearbit vs Lusha API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-lusha.md)\n- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.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 Lusha API + MCP](https://www.anchorterminal.com/compare/databar-vs-lusha.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 Lusha API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-lusha.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 Lusha API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-lusha.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- [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 Lusha API + MCP](https://www.anchorterminal.com/compare/hunter-vs-lusha.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": "Lusha API + MCP vs ZeroBounce", "url": "" } ], "description": "ZeroBounce and Lusha score within a point of each other for lead enrichment, 62.4 and 62.3 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Lusha API + MCP B 62.3", "ZeroBounce B 62.4", "scores" ], "h1": "Lusha API + MCP vs ZeroBounce", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/lusha-vs-zerobounce", "published": "2026-10-01", "section": "tools", "title": "Lusha vs ZeroBounce for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce" }, "tokens": { "markdown": 4700, "slim": 2480 }, "version": 1 }