# Databar vs ZeroBounce (slim)

> ZeroBounce scores 62.4 (B) to Databar's 53.8 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/databar-vs-zerobounce.md (~3,950 tokens) · this version ~1,780 tokens · JSON https://www.anchorterminal.com/compare/databar-vs-zerobounce.json · canonical https://www.anchorterminal.com/compare/databar-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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ZeroBounce scores 62.4 (B) on agent readiness against Databar's 53.8 (D), and leads in 4 of 7 scored categories. Databar leads on schema & documentation. Both do lead enrichment.

- Databar: D 53.8, rank #933 of 1486 · https://www.anchorterminal.com/tools/databar.min.md
- ZeroBounce: B 62.4, rank #559 of 1486 · https://www.anchorterminal.com/tools/zerobounce.min.md
- Databar, good for Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich. Ahead on Schema & documentation, 84 against 54. Also Free to start without a card.
- ZeroBounce, good for Email verification before outreach, the verification-first listing in lead-data. Ahead on Reliability, 75 against 28; Security & auth, 65 against 47; Transparency & trust, 63 against 55. Also Runs on your own machine.

| Category | Databar | ZeroBounce |
| --- | --- | --- |
| Reliability (16%) | 28 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 54 |
| Agent ergonomics (13%) | 66 | 69 |
| Security & auth (14%) | 47 | 65 |
| Payments & pricing (10%) | 35 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 70 |
| Transparency & trust (7%) | 55 | 63 |

| Fact (where they differ) | Databar | ZeroBounce |
| --- | --- | --- |
| Vendor | Databar, Inc. | Hertza L.L.C. (ZeroBounce) |
| Hosted endpoint | `https://mcp.databar.ai/mcp` | `https://api.zerobounce.net/v2` |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Licence | Proprietary, under Databar, Inc.'s terms of service | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |
| Tools exposed | 69 | 0 |
| Last release | 2026-10-30 | 2026-10-25 |
| Terms last updated | 2026-10-01 | 2026-05-05 |
| Privacy policy last updated | 2026-10-01 | 2026-06-30 |
| Terms or service can change without notice | not found in the text | yes |

Why the edge:
- Reliability, ZeroBounce +47: Databar 28 (Hosted lines. No status page linked from the site or docs (0). No incident history to read (5). The 20 August changelog says rate limits return 429, but no numbers were found in the docs read (5 of 15). The SDK backs off on 429 per the 28 September entry, tasks can be cancelled with a refund, and no Retry-After or idempotency key is documented (8 of 15). No SLA found (0). The MCP server left beta on 15 July 2026 and the API is generally available (10). 0+5+5+8+0+10 = 28.); 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, Databar +30: Databar 84 (Each API reference page embeds its OpenAPI 3.1 operation (spec version 0.1.2), with no downloadable file found (20 of 25). llms.txt with 79 API entries and Markdown twins (10). Descriptions say when to use each endpoint, such as headless runs against table runs, and what a delete leaves behind (16 of 20). Typed request bodies with required fields (12 of 15). An error envelope with stable codes and examples for 400, 406 and 422 (14 of 15). v1 paths and a dated changelog, though the API's own versioning isn't described (12 of 15). 20+10+16+12+14+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.)
- Security & auth, ZeroBounce +18: Databar 47 (A workspace API key in a header, never in the URL, and OAuth on the MCP with a Connected apps page to revoke access. No scopes found (20 of 30). No read-only key; MCP balance checks and confirmation above 50 credits, a 30-day trash for workbooks and tables, but row, column and table deletes through the tools (12 of 20). Enrichment results include web-scraped and AI researcher text, with no prompt-injection guidance (3 of 15). Credit usage charts, transaction logs and per-request data logs (12 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). 20+12+3+12+0 = 47.); 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.)
- Transparency & trust, ZeroBounce +8: Databar 55 (Closed service with terms effective 1 October 2026 naming Databar, Inc. of Delaware (15 of 30). The privacy policy keeps data 'for as long as needed' with no periods; the docs give 24 hours for task results; a DPA is part of the agreement but was not read (15 of 30). The changelog flagged breaking API and SDK changes on 20 August 2026, and the terms let Databar retire any form of programmatic access; no notice period stated (8 of 20). Sub-processors are disclosed under the DPA, which was not read; data is processed in the United States (5 of 20). 15+15+8+5 = 43.); 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.)