# Retriever vs ZeroBounce (slim)

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

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

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.

- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- ZeroBounce: B 64.6, rank #582 of 1557 · https://www.anchorterminal.com/tools/zerobounce.min.md
- Retriever, good 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.
- ZeroBounce, good 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 Runs on your own machine; No incidents deducted, where Retriever loses 15 points for them.

| Category | Retriever | ZeroBounce |
| --- | --- | --- |
| Reliability (16%) | 45 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 54 |
| Agent ergonomics (13%) | 75 | 69 |
| Security & auth (14%) | 23 | 65 |
| Payments & pricing (10%) | 30 | 53 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 5 | 70 |
| Transparency & trust (7%) | 49 | 63 |

| Fact (where they differ) | Retriever | ZeroBounce |
| --- | --- | --- |
| 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 |
| 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 |
| 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 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

Why the edge:
- 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).); ZeroBounce 70 (Closed service.)
- 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 (2…); 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`…)
- 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).); ZeroBounce 75 (Hosted lines.)
- Schema & documentation, Retriever +28: Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).); ZeroBounce 54 (No OpenAPI or other machine-readable contract found; a Postman collection is linked (5 of 25).)
- Payments & pricing, ZeroBounce +23: Retriever 30 (No x402, MPP or L402 (0).); ZeroBounce 53 (No x402, MPP or L402 (0).)
- Transparency & trust, ZeroBounce +14: Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).); ZeroBounce 63 (Closed service under terms naming Hertza L.L.C. (ZeroBounce) of Nevada; SDKs and MCP server open source (15 of 30).)
