Clay vs ZeroBounce

Clay 40

Graded with the hosted lines on the Public API. status.clay.com is linked from every page footer but answered with a Cloudflare bot check on 14 October, and on 4 November its robots.txt answered the same check, so the host is treated as blocked and its components stay unconfirmed (10 of 20, per the 14 October check, not re-read on 4 November). No readable history (5). A per-workspace request limit with no number, and published search-result caps per plan (8 of 15). 429 with Retry-After and X-RateLimit headers, backoff with jitter, and retries of 5xx only when a request is safe to retry, re-read on 4 November. No idempotency keys (12 of 15). The terms of 1 November 2026 replaced the May 2024 version and no longer set the 99.0 per cent monthly uptime target with fee credits, and no other SLA was found (0). The API is v0, and Workflows and run search are labelled alpha or beta (5 of 10). 10 + 5 + 8 + 12 + 0 + 5 = 40.

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.

Clay 84

A public OpenAPI 3 spec, per the 14 October check (25). llms.txt and Markdown copies of every page, re-read on 4 November, with 18 API reference pages now that Audiences privacy deletion and its status call were added in the week of 26 October (10). Pages say when to use each primitive, and deprecated filters-mode endpoints name their replacement (16 of 20). Typed request bodies, with a query grammar fetched from a reference endpoint rather than enums (12 of 15). curl examples on every guide, but error bodies carry only a message, and the errors page says they don't include stable codes (9 of 15). v0 in the path and a weekly product changelog that names CLI, MCP and API changes, without an API-specific log (12 of 15). 25 + 10 + 16 + 12 + 9 + 12 = 84.

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.

Clay 48

A personal API key tied to the user's workspace access, with no scopes documented. The CLI uses OAuth per workspace (15 of 30). Functions need API or MCP access switched on one by one, workspace roles apply, and the changelog adds IP access restrictions (week of 21 September) and MCP client allowlisting (week of 26 October). CLI 1.14.0 (3 November) can hold commands that delete, send or run at scale for the user's approval, but the Claude Code plugin's hook still auto-approves most clay CLI commands, including ones that spend credits (8 of 20). Claygent web research returns untrusted text, and no injection guidance was found (3 of 15). Credit balances and a workflow-run query, with no per-call audit log found (6 of 15). security.txt valid to 31 July 2027 naming security@clay.com and trust.clay.com, re-read on 4 November, and SOC 2 Type II, ISO 27001 and ISO 42001 listed on the pricing page. No bug bounty found (16 of 20). 15 + 8 + 3 + 6 + 16 = 48.

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.

Clay 30

No x402, MPP or L402 (0). Data credits from $0.05 and plan prices public, though on 4 November the plan cards still say $167 and $446 a month for Launch and Growth while the FAQ says $185 and $495 (15 of 20). A free plan with 100 data credits and 500 actions a month, and a page footer saying no credit card is required, while the FAQ lists Clay API access under Enterprise (15 of 20). A person signs up in a browser, and CLI sign-in opens a browser or a device code (0). 0 + 15 + 15 + 0 = 30.

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.

Clay 75

clay plugin 2.35.0 on 4 November 2026, requiring CLI 1.14.0, whose tag sits on the 3 November release commit (30). 36 plugin releases from 7 August to 4 November, the last three (15 October, 3 and 4 November) changing skill content, plus weekly dated product roundups to the week of 26 October (20). Weekly dated product roundups and a support address, with the plugin's issue handling not visible (12 of 15). No official SDKs, the CLI is current (8 of 15). CLI binaries ship from GitHub releases, and the repository has no licence file (5 of 10). 30 + 20 + 12 + 8 + 5 = 75.

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.