Head to head · Lead enrichment · October 2026 research run
Retriever vs ZeroBounce
ZeroBounce scores 64.6 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema & documentation and agent ergonomics. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.
Ahead on
- Schema & documentation, 82 against 54
- Agent ergonomics, 75 against 69
Watch for
Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted
Best for Email verification before outreach, the verification-first listing in lead-data.
Ahead on
- Reliability, 75 against 45
- Security & auth, 65 against 23
- Payments & pricing, 53 against 30
- Maintenance & community, 70 against 5
- Transparency & trust, 63 against 49
Also in its favour
- Runs on your own machine
- No incidents deducted, where Retriever loses 15 points for them
Watch for
Every documented example sends the key as an api_key query parameter
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community ZeroBounce +65
Retriever 5
No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.
ZeroBounce 70
Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70.
Security & auth ZeroBounce +42
Retriever 23
The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).
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.
Reliability ZeroBounce +30
Retriever 45
No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).
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.
Schema & documentation Retriever +28
Retriever 82
OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).
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.
Payments & pricing ZeroBounce +23
Retriever 30
No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).
ZeroBounce 53
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Transparency & trust ZeroBounce +14
Retriever 49
Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).
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.
Score by category
| Category | Weight | Retriever | ZeroBounce | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 75 | ZeroBounce +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 54 | Retriever +28 |
| Agent ergonomics | 13% | 75 | 69 | Retriever +6 |
| Security & auth | 14% | 23 | 65 | ZeroBounce +42 |
| Payments & pricing | 10% | 30 | 53 | ZeroBounce +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 70 | ZeroBounce +65 |
| Transparency & trust | 7% | 49 | 63 | ZeroBounce +14 |
| Negative events | ≤15 | -15 | 0 | |
| Total | F 32/100 | B 64.6/100 |
Facts side by side
| Fact | Retriever | ZeroBounce |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Retriever | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | https://api.retriever.run/mcp | https://api.zerobounce.net/v2 |
| Transports | Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | none | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | 67 | 0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | none | 2026-10-25 |
| Terms last updated | 2026-08-30 | 2026-05-05 |
| Privacy policy last updated | 2026-08-30 | 2026-06-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
How the scores have moved
Retriever
No score change since it was listed.
Verdicts
Retriever
Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.
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.
Before you call either
Retriever
- Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
- Send an
Idempotency-Keywith each run and replay with the same key after a timeout, so a retry doesn't start a second billed run - Run
getEmail,getPhoneNumberandwebResearchthroughservice_batch_execute, even for one person;service_executerefuses them - Check
creditsbefore a paid run, and callservice_inspectfor a service'sthingsToKnowand credit cost before executing it - On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again
ZeroBounce
- 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_keyin the URL
Questions
Which is better for AI agents, Retriever or ZeroBounce?
ZeroBounce scores 64.6 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema & documentation and agent ergonomics.
Do Retriever and ZeroBounce need an API key?
Retriever takes an API key or an OAuth sign-in. ZeroBounce needs an API key.
Can an agent call Retriever and ZeroBounce without installing anything?
Yes. Retriever has a hosted endpoint at https://api.retriever.run/mcp and ZeroBounce at https://api.zerobounce.net/v2.
Other comparisons with Retriever or ZeroBounce
- Apollo API + MCP vs Retriever
- Clay vs Retriever
- Coresignal API + MCP vs Retriever
- Crustdata API + MCP vs Retriever
- Dievio vs Retriever
- Enrich Layer API + MCP vs Retriever
- Explorium AgentSource vs Retriever
- FullEnrich API + MCP vs Retriever
- Fuse MCP vs Retriever
- Gojiberry vs Retriever
- LeadMagic API + MCP vs Retriever
- Lusha API + MCP vs Retriever
- People Data Labs vs Retriever
- Prospeo API + MCP vs Retriever
- Retriever vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- Apollo API + MCP vs ZeroBounce
- Clay vs ZeroBounce
- Clearbit vs Retriever
- Clearbit vs ZeroBounce
- Coresignal API + MCP vs ZeroBounce
- Crustdata API + MCP vs ZeroBounce
- Databar vs Retriever
- Databar vs ZeroBounce
- Dievio vs ZeroBounce
- Dropcontact API + MCP vs Retriever
- Dropcontact API + MCP vs ZeroBounce
- Enrich Layer API + MCP vs ZeroBounce
- Explorium AgentSource vs ZeroBounce
- FullContact vs Retriever
- FullContact vs ZeroBounce
- FullEnrich API + MCP vs ZeroBounce
- Gojiberry vs ZeroBounce
- Lusha API + MCP vs ZeroBounce
- People Data Labs vs ZeroBounce
- Prospeo API + MCP vs ZeroBounce
- ZeroBounce vs ZoomInfo API + MCP
- Hunter API + MCP vs Retriever
- Hunter API + MCP vs ZeroBounce
- Fuse MCP vs ZeroBounce
- LeadMagic API + MCP vs ZeroBounce
- RocketReach API vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/retriever-vs-zerobounce.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/retriever.json·/api/v1/tools/zerobounce.json - From a terminal
anchor compare retriever zerobounce(the CLI) - Over MCP
compare_tools {"a": "retriever", "b": "zerobounce"}at/mcp, no key