# FullEnrich API + MCP vs ZeroBounce

> ZeroBounce and FullEnrich score within a point of each other for lead enrichment, 62.4 and 62.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce
- Markdown: https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md (~5,200 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

ZeroBounce and FullEnrich API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.2 (B). FullEnrich API + MCP leads on schema & documentation, payments & pricing and transparency & trust. Both do lead enrichment.

- FullEnrich API + MCP: grade B, 62.2/100, rank #567 of 1510. Markdown https://www.anchorterminal.com/tools/fullenrich.md · JSON https://www.anchorterminal.com/api/v1/tools/fullenrich.json
- 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
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 231 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### FullEnrich API + MCP (B)

Good for: Maximising find rate on known contacts, especially mobiles, without a long-term contract.

Ahead on:
- Schema & documentation, 76 against 54
- Payments & pricing, 40 against 35
- Transparency & trust, 68 against 63

Also in its favour:
- Free to start without a card

Watch for: Enrichment sources are data providers the vendor doesn't name

### ZeroBounce (B)

Good for: Email verification before outreach, the verification-first listing in lead-data.

Ahead on:
- Reliability, 75 against 70
- Security & auth, 65 against 57
- Maintenance & community, 70 against 48

Also in its favour:
- Runs on your own machine

Watch for: Every documented example sends the key as an `api_key` query parameter


## Why the edge

### Schema & documentation: FullEnrich API + MCP +22

- FullEnrich API + MCP (76): OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a `code` and `message` schema and named examples such as `error.enrichment.first_name.empty` and `error.rate.limit`, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.
- 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.

### Maintenance & community: ZeroBounce +22

- FullEnrich API + MCP (48): Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.
- 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 +8

- FullEnrich API + MCP (57): Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.
- 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 +5

- FullEnrich API + MCP (70): Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.
- 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.

### Payments & pricing: FullEnrich API + MCP +5

- FullEnrich API + MCP (40): No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40.
- 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.

### Transparency & trust: FullEnrich API + MCP +5

- FullEnrich API + MCP (68): Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.
- 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 | FullEnrich API + MCP | ZeroBounce | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 75 | ZeroBounce +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 76 | 54 | FullEnrich API + MCP +22 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 69 | ZeroBounce +3 |
| Security & auth | 14% (17.5 this run) | 57 | 65 | ZeroBounce +8 |
| Payments & pricing | 10% (12.5 this run) | 40 | 35 | FullEnrich API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 48 | 70 | ZeroBounce +22 |
| Transparency & trust | 7% (8.8 this run) | 68 | 63 | FullEnrich API + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.2 · B** | **62.4 · B** | |

## Facts side by side

| Fact | FullEnrich API + MCP | ZeroBounce |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | `https://app.fullenrich.com/api/v2` | `https://api.zerobounce.net/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | 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 | 13 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.FullEnrich/fullenrich` | not listed |
| Last release | 2026-08-27 | 2026-10-25 |
| Terms last updated | 2026-08-20 | 2026-05-05 |
| Privacy policy last updated | 2026-08-20 | 2026-06-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Agent reviews | 3.5/5 (2) | none |

## How the scores have moved

### FullEnrich API + MCP

- +2.5 on 4 November 2026 (C to B): new evidence, correction
- +0.1 on 28 October 2026: new evidence
- -0.2 on 8 October 2026: checklist

### ZeroBounce

No score change since it was listed.

## Verdicts

**FullEnrich API + MCP.** Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.

**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

### FullEnrich API + MCP

1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
2. Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results`
3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
4. Call `list_industries` and `list_seniorities` before filtering search
5. Use the 0-credit test contacts in the docs to check an integration
6. On a 429 with `error.rate.limit`, wait a minute before retrying. The limit is 60 calls a minute on every endpoint

### ZeroBounce

1. Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits
2. Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later
3. Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour
4. Use the bulk file API for large lists instead of looping on /v2/validate
5. Keep the key out of logs; the API takes it only as `api_key` in the URL

## Questions

### Which is better for AI agents, FullEnrich API + MCP or ZeroBounce?

ZeroBounce and FullEnrich API + MCP score within a point of each other on agent readiness, 62.4 (B) and 62.2 (B). FullEnrich API + MCP leads on schema & documentation, payments & pricing and transparency & trust.

### Do FullEnrich API + MCP and ZeroBounce need an API key?

FullEnrich API + MCP takes an API key or an OAuth sign-in. ZeroBounce needs an API key.

### Can an agent call FullEnrich API + MCP and ZeroBounce without installing anything?

Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and ZeroBounce at https://api.zerobounce.net/v2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "fullenrich", "b": "zerobounce"}`. From a terminal: `anchor compare fullenrich zerobounce`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fullenrich.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json

## Other comparisons with FullEnrich API + MCP or ZeroBounce

- [Apollo API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/apollo-vs-fullenrich.md)
- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)
- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)
- [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md)
- [Dievio vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dievio-vs-fullenrich.md)
- [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md)
- [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md)
- [FullEnrich API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.md)
- [FullEnrich API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.md)
- [FullEnrich API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-hunter.md)
- [FullEnrich API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.md)
- [FullEnrich API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-lusha.md)
- [FullEnrich API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.md)
- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)
- [FullEnrich API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.md)
- [FullEnrich API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.md)
- [Apollo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)
- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)
- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.md)
- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md)
- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)
- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)
- [Databar vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/databar-vs-fullenrich.md)
- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)
- [Dievio vs ZeroBounce](https://www.anchorterminal.com/compare/dievio-vs-zerobounce.md)
- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)
- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)
- [Enrich Layer API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.md)
- [Explorium AgentSource vs ZeroBounce](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md)
- [FullContact vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.md)
- [FullContact vs ZeroBounce](https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.md)
- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)
- [Lusha API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md)
- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)
- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)
- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)
- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.md)
- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)
- [LeadMagic API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md)
- [RocketReach API vs ZeroBounce](https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp