Head to head · Lead enrichment · October 2026 research run
Gojiberry vs ZeroBounce
ZeroBounce scores 62.4 (B) on agent readiness against Gojiberry's 48.2 (D), and leads in 6 of 7 scored categories. Gojiberry leads on schema & documentation. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 231 leads comparisons
Which one, for what
Best for A founder or small sales team that wants an agent to pull scored, signal-based B2B leads and run LinkedIn and email outreach from one paid workspace.
Ahead on
- Schema & documentation, 71 against 54
Watch for
API keys carry no scopes or read-only mode, and an organisation owner's key can act as any member through x-impersonate-user-id
Best for Email verification before outreach, the verification-first listing in lead-data.
Ahead on
- Reliability, 75 against 70
- Agent ergonomics, 69 against 55
- Security & auth, 65 against 31
- Payments & pricing, 35 against 10
- Maintenance & community, 70 against 20
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
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 +50
Gojiberry 20
No changelog or dated API release was found. The developer docs carry no dates, and their sitemap stamps record no change. The newest dated evidence is help-centre editing. The MCP article is dated 29 September 2026 and the API article 21 August 2026, so the partial credit for activity inside 90 days is kept (15 of 30). No dated releases to count (0). Live chat and hello@gojiberry.ai for support, not tested, and no public changelog (5 of 15). No readable registry page names the server and no official SDKs exist (0). Package health 5 to 0, an in-between value with no package behind it. 15 + 0 + 5 + 0 + 0 = 20.
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 +34
Gojiberry 31
Credential line 18 to 20. Bearer API keys created in the app and shown once, now with a documented way to revoke them (deleting a key in Settings, API cuts its access at once). No scopes, and an organisation owner's key can act as any member through x-impersonate-user-id. The MCP server signs users in with OAuth and creates a key named after the client app (20 of 30). No read-only mode on the API. The MCP page says tools that change data are flagged so clients can ask first, and warns that send_unibox_message and the deletes can't be undone, but the server enforces nothing (3 of 20). Results carry LinkedIn profile text and inbound messages, with no prompt-injection guidance found (2 of 15). Campaign and agent logs and team activity through the API, a credit usage history in the app, no per-key call log found (6 of 15). No security.txt (404 on 4 November), disclosure policy, bounty or certification found. The privacy policy states encryption in transit and at rest, which is none of the programme line's items, so the line is 0 (was 3, a value with no programme evidence behind it). 20 + 3 + 2 + 6 + 0 = 31.
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.
Payments & pricing ZeroBounce +25
Gojiberry 10
No x402, MPP or L402 (0). The Pro plan is public at $99 a month, and credit costs per action are published, but no dollar price per credit was found (10). There's a free trial, and the help centre says the subscription then starts on the saved payment method, so we read it as needing a card. We didn't open the signup form (0). A person signs up in a browser and the terms forbid account creation by bots (0). 0 + 10 + 0 + 0 = 10.
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.
Schema & documentation Gojiberry +17
Gojiberry 71
Gojiberry moved its developer docs to dev.gojiberry.ai (Mintlify), and ext.gojiberry.ai/documentation now redirects there. Public OpenAPI 3.0.0 file, version 1.0, with 56 operations on 45 paths, linked from the docs' llms.txt under OpenAPI Specs (25). llms.txt 0 to 10. dev.gojiberry.ai serves llms.txt and every page as Markdown. 47 of 56 operations carry a description, and many say when to use them, such as the async enrichment routes for MCP clients and free search before paid reveal (15 of 20). 25 enums, 23 required lists and 50 required parameters, but search results are untyped objects and only four length bounds appear (9 of 15). 73 examples and curl samples. Error responses are a status code and a sentence, none of the 53 error responses has a body schema (8 of 15). A /v1 path and version 1.0, with no changelog found (4 of 15). 25 + 10 + 15 + 9 + 8 + 4 = 71.
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.
Agent ergonomics ZeroBounce +14
Gojiberry 55
On the API, search returns masked rows until revealed, but a Contact has 75 fields and no field selection (14 of 25). page and limit on lists, eleven filters on contacts and fifteen on lead search (17 of 20). Status codes are documented per operation, with 402 for credits, 409 and 422. Bodies are {message, statusCode} and there's no error catalogue (11 of 20). No idempotency keys. Search is deterministic, a deleted contact can't be created again, and failed enrichments cost nothing. The MCP page says tools that change data are flagged, which we couldn't read from the server (7 of 20). Few required parameters and stated defaults, no official SDKs (6 of 15). 14 + 17 + 11 + 7 + 6 = 55.
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.
Reliability ZeroBounce +5
Gojiberry 70
Graded with the hosted lines. Status page at status.gojiberry.ai on Better Stack with two components, gojiberry.ai and api.gojiberry.ai, and 90-day bars. Neither names ext.gojiberry.ai or mcp.gojiberry.ai, the hosts an agent calls, so the page has no component for the product (15, was 20). Both show 100 per cent, and the incident history lists none for September, October or November 2026 (August per the 8 October check). The page has not been shown to post any incident, so 20 rather than a clean record (was 22, an in-between value; tldv, zamp). The quickstart and the OpenAPI file state 100 requests a minute and 100,000 a day per account, shared by all keys and MCP connections, with lower limits on some endpoints (15). 429 line 7 to 10. Requests over a limit now get 429 Too Many Requests with a Retry-After header and the instruction to wait that long before retrying. No idempotency keys or safe-retry guidance for writes, so Retry-After alone (10). No SLA found, and the terms say the service is supplied as is (0). API version 1.0 with no beta label (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.
Score by category
| Category | Weight this run | Gojiberry | ZeroBounce | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 75 | ZeroBounce +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 71 | 54 | Gojiberry +17 |
| Agent ergonomics | 13%16.2 | 55 | 69 | ZeroBounce +14 |
| Security & auth | 14%17.5 | 31 | 65 | ZeroBounce +34 |
| Payments & pricing | 10%12.5 | 10 | 35 | ZeroBounce +25 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 20 | 70 | ZeroBounce +50 |
| Transparency & trust | 7%8.8 | 61 | 63 | ZeroBounce +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 48.2/100 | B 62.4/100 |
Facts side by side
| Fact | Gojiberry | ZeroBounce |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SUPERFRUITS SAS (Gojiberry AI) | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | https://ext.gojiberry.ai | https://api.zerobounce.net/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Gojiberry's General Terms | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-10-25 |
| Terms last updated | no date given | 2026-05-05 |
| Privacy policy last updated | no date given | 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 | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
How the scores have moved
ZeroBounce
No score change since it was listed.
Verdicts
Gojiberry
A public OpenAPI file with 56 operations linked from the developer docs' llms.txt, a free masked lead search and published limits of 100 requests a minute with Retry-After make the API easy to plan against. Keys have no scopes, an owner's key can act as any member, and writes can start LinkedIn and email outreach from connected accounts.
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
Gojiberry
- Connect MCP clients to https://mcp.gojiberry.ai/mcp and sign in to Gojiberry. Custom clients must send a
User-Agentheader or get a 403 - Create resources in the order list, source agent, campaign. A source agent with no campaign only finds leads
- Adding a contact to a list enrols it in the linked campaign, which sends LinkedIn or email messages. Ask the user before list writes
- Search with POST /v1/directory/leads/search for free, then reveal only the ids you need at 0.5 credit each
- On a 429, wait for the
Retry-Afterseconds before retrying. Limits are shared by every key and MCP connection of the account
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, Gojiberry or ZeroBounce?
ZeroBounce scores 62.4 (B) on agent readiness against Gojiberry's 48.2 (D), and leads in 6 of 7 scored categories. Gojiberry leads on schema & documentation.
Do Gojiberry and ZeroBounce need an API key?
Gojiberry takes an API key or an OAuth sign-in. ZeroBounce needs an API key.
Can an agent call Gojiberry and ZeroBounce without installing anything?
Yes. Gojiberry has a hosted endpoint at https://ext.gojiberry.ai and ZeroBounce at https://api.zerobounce.net/v2.
Other comparisons with Gojiberry or ZeroBounce
- Apollo API + MCP vs Gojiberry
- Clay vs Gojiberry
- Coresignal API + MCP vs Gojiberry
- Crustdata API + MCP vs Gojiberry
- Dievio vs Gojiberry
- Enrich Layer API + MCP vs Gojiberry
- Explorium AgentSource vs Gojiberry
- FullEnrich API + MCP vs Gojiberry
- Fuse MCP vs Gojiberry
- Gojiberry vs Hunter API + MCP
- Gojiberry vs LeadMagic API + MCP
- Gojiberry vs Lusha API + MCP
- Gojiberry vs People Data Labs
- Gojiberry vs Prospeo API + MCP
- Gojiberry vs RocketReach API
- Gojiberry vs ZoomInfo API + MCP
- Apollo API + MCP vs ZeroBounce
- Clay vs ZeroBounce
- Clearbit vs Gojiberry
- Clearbit vs ZeroBounce
- Coresignal API + MCP vs ZeroBounce
- Crustdata API + MCP vs ZeroBounce
- Databar vs Gojiberry
- Databar vs ZeroBounce
- Dievio vs ZeroBounce
- Dropcontact API + MCP vs Gojiberry
- Dropcontact API + MCP vs ZeroBounce
- Enrich Layer API + MCP vs ZeroBounce
- Explorium AgentSource vs ZeroBounce
- FullContact vs Gojiberry
- FullContact vs ZeroBounce
- FullEnrich API + MCP 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 ZeroBounce
- Fuse MCP vs ZeroBounce
- LeadMagic API + MCP vs ZeroBounce
- RocketReach API vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/gojiberry-vs-zerobounce.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gojiberry.json·/api/v1/tools/zerobounce.json - From a terminal
anchor compare gojiberry zerobounce(the CLI) - Over MCP
compare_tools {"a": "gojiberry", "b": "zerobounce"}at/mcp, no key