{ "data": { "a": { "slug": "explorium-agentsource", "name": "Explorium AgentSource", "vendor": "Explorium Ltd.", "vendorUrl": "https://www.explorium.ai", "kind": "http-api", "category": "lead-data", "summary": "Explorium's AgentSource is a B2B data service for matching, searching and enriching companies and prospects, with event signals and AI research tasks. Agents reach it through a REST API (v2) and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/explorium-agentsource", "markdownUrl": "https://www.anchorterminal.com/tools/explorium-agentsource.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/explorium-agentsource.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/explorium-agentsource.json", "dns": "explorium-agentsource.grade.anchorterminal.com", "repo": "https://github.com/explorium-ai/mcp-explorium", "license": "Proprietary service under the Explorium Terms of Use. The `mcp-explorium` repository of connection files is MIT", "transports": [ "http", "streamable-http", "sse" ], "remoteUrl": "https://api.explorium.ai", "packages": [], "auth": "api-key", "authNotes": "Self-serve API key from the admin console at admin.explorium.ai, sent in the `api_key` header. The docs say each company gets one key shared by all its users, with no scopes. The MCP v2 guide sends the same key as `Authorization: Bearer`. The older v1 MCP server at `mcp.explorium.ai` uses OAuth. The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint.", "pricing": "usage", "pricingNotes": "One-off credit packs, no subscription. The pricing page lists Lite $29.99 for 500 credits, Starter $149.99 for 5,000, Growth $749.99 for 30,000 and Scale $7,499.99 for 500,000, valid 12 months and non-refundable. A free trial gives 100 credits for 90 days, so an agent's owner can start without a contract. The site's `pricing.md` (dated 26 August 2026) lists Starter at $99.99 for 2,500 and Growth at 25,000 credits instead. Fetch costs 1 credit a result (2 with the Bombora intent filter), enrichments 1 to 5, and contact enrichment 2 for email or 5 with phone.", "priceSummary": "$0.06 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file, the pricing files or the terms of use (checked 2026-10-09).", "endpoints": [] }, "toolCount": 11, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://developers.explorium.ai", "llmsTxt": "https://developers.explorium.ai/llms.txt", "openapi": "https://developers.explorium.ai/openapi.json", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.company", "data.person" ], "tags": [ "lead-search", "enrichment", "hosted", "mcp", "openapi", "llms-txt", "webhooks", "async-jobs", "credits", "free-trial", "closed-source" ], "lastRelease": "2026-09-02", "graded": true, "anchor": { "graded": true, "score": 41.5, "grade": "E", "agentReady": false, "rank": 1299, "ranked": true, "rankOf": 1510, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 28, "payments": 40, "reliability": 42, "schema": 40, "security": 32, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -2, "negativeNotes": [ "On 9 October 2026 the site's machine-readable `pricing.md` (dated 26 August 2026) lists Starter at $99.99 for 2,500 credits and Growth at 25,000 credits, while the pricing page it names as canonical lists $149.99 for 5,000 and 30,000. The site's `auth.md` and server card also send agents to the MCP server the docs call deprecated. A misleading published claim, 2 points (https://www.explorium.ai/pricing.md, https://www.explorium.ai/pricing/). No link to `pricing.md` from a page was recorded. The term stands on the server card alone, a published discovery document that still names the v1 server, as does the README of the vendor's MCP repository (https://www.explorium.ai/.well-known/mcp/server-card.json)" ], "verdict": "AgentSource v2 has Markdown docs, a 200 queries a minute limit with `Retry-After`, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, no specification file is linked from the docs, and the vendor's two published price tables disagree.", "bestFor": "Agents that build prospect lists by filter and then enrich them, or that watch companies for events such as funding and role changes.", "strengths": [ "llms.txt and a Markdown twin of every docs page, with request and response examples", "Rate limit of 200 queries a minute per key, with `X-RateLimit-*` headers and `Retry-After` on 429", "Credit packs priced in public from $0.015 to $0.06 a credit, and a 100-credit free trial valid 90 days", "Statistics endpoints are free, and the `credit-usage: true` header returns the credits each call spent", "v1 retirement timeline published, with end of support about six months and retirement about twelve months after 2 September 2026" ], "weaknesses": [ "No status page was found, and no SLA is published", "One API key per company, shared by all users, with no scopes or read-only mode", "The site's `pricing.md` and its pricing page give different prices for the Starter and Growth packs", "The terms of use bar benchmarking, automated data collection and robots on the website, and allow service changes without notice", "No dated changelog, no official REST SDK and no linked specification file found in the docs" ], "agentNotes": [ "Send the key in the `api_key` header to `https://api.explorium.ai` and use `/v2` paths. v1 is deprecated", "Point MCP clients at `https://mcp-v2.explorium.ai/mcp`. The site's agent files still name the v1 server at `mcp.explorium.ai`", "Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50", "Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter", "Call `/v2/autocomplete` before filtering on category, tech stack or job title, and never mix two category types in one request" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.5 } ], "editorialScores": { "ergonomics": 63, "maintenance": 28, "payments": 40, "reliability": 42, "schema": 40, "security": 32, "transparency": 51 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl --request POST --url https://api.explorium.ai/v1/prospects --header 'accept: application/json' --header 'api_key: YOUR_API_KEY' --header 'content-type: application/json' --data '{\"mode\": \"full\", \"page\": 1}'" }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/explorium-agentsource" }, "area": "web-data", "unitPrices": [ { "item": "Lite credit pack", "unit": "credit", "usd": 0.06, "note": "$29.99 for 500 credits, valid 12 months" }, { "item": "Starter credit pack", "unit": "credit", "usd": 0.03, "note": "$149.99 for 5,000 credits on the pricing page. The site's pricing.md says $99.99 for 2,500" }, { "item": "Growth credit pack", "unit": "credit", "usd": 0.025, "note": "$749.99 for 30,000 credits on the pricing page. The site's pricing.md says 25,000" }, { "item": "Scale credit pack", "unit": "credit", "usd": 0.015, "note": "$7,499.99 for 500,000 credits" }, { "item": "Fetched business or prospect", "unit": "record", "usd": 0.03, "note": "1 credit a result at the Starter rate, 2 credits with the Bombora intent filter" }, { "item": "Contact enrichment, email and phone", "unit": "record", "usd": 0.15, "note": "5 credits at the Starter rate. Email only is 2 credits" } ], "provenance": { "legalEntity": "Explorium Ltd.", "domain": "explorium.ai", "domainRegistered": "2018-08-16", "endpointOnVendorDomain": true, "terms": "https://www.explorium.ai/explorium-website-terms-of-use/", "privacy": "https://www.explorium.ai/privacy-policy/", "statusPage": "", "changelog": "https://developers.explorium.ai/v2/whats-new", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The page at /explorium-website-terms-of-use/ is titled Explorium Terms of Use (updated 14 June 2026). It is a contract between Explorium Ltd. and its affiliates and the customer, and covers the Platform, the API and Platform Data, so it governs the product and not only the website.", "The privacy policy (updated 28 June 2026) names Explorium Ltd., 3 Daniel Frisch St., Tel-Aviv, Israel, and covers the Platform and its end users. The terms give a contact address for Explorium Inc., 400 Concar Drive, San Mateo, California.", "www.explorium.ai/.well-known/security.txt returns the site's page-not-found page.", "No status page is linked from the docs or the site files read. status.explorium.ai did not answer our request.", "The changelog link is the v2 change list. No dated changelog was found in the docs index.", "The API answers at api.explorium.ai and the MCP server at mcp-v2.explorium.ai.", "The Terms of Use bar robots and other automated means used to scrape the Explorium web site, Content and Services. On 4 November only the terms were re-read; other facts are per the 9 October check." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/explorium-agentsource.json", "live": { "slug": "explorium-agentsource", "probe": { "target": "https://api.explorium.ai", "method": "get", "lastAt": "2026-11-07T22:55:56.869716412Z", "lastOk": true, "lastStatus": 401, "lastMs": 440, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 411, "p95ms24h": 544, "samples24h": 244, "samples30d": 7251, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "versions": [ { "registry": "github", "name": "explorium-ai/mcp-explorium", "version": "1.0.0", "released": "2025-09-16", "seenAt": "2026-11-06T23:25:03.374778178Z" } ], "githubStars": 22, "securityTxt": { "url": "https://explorium.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:31.158102479Z" }, "llmsTxt": { "url": "https://developers.explorium.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:27.363632498Z" }, "domain": { "domain": "explorium.ai", "registered": "2018-08-16", "source": "https://rdap.identitydigital.services/rdap/domain/explorium.ai", "checkedAt": "2026-11-01T14:07:52.634282788Z" }, "pages": [ { "url": "https://developers.explorium.ai/v2/whats-new", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:03:49.599998547Z", "changedAt": "2026-10-27T03:42:20.226518954Z", "fingerprint": "c11a860257af" }, { "url": "https://www.explorium.ai/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:28:29.243551803Z", "changedAt": "2026-11-05T13:12:17.595425269Z", "fingerprint": "95b6ed8464c5" }, { "url": "https://www.explorium.ai/explorium-website-terms-of-use/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:28:26.803766243Z", "changedAt": "2026-11-05T13:12:14.352919326Z", "fingerprint": "13460fb62436" } ], "github": { "repo": "explorium-ai/mcp-explorium", "checkedAt": "2026-11-02T08:47:16.33000263Z", "stars": 22, "archived": false, "issuesEnabled": true, "pushedAt": "2026-03-03T15:32:02Z", "openIssues": 3, "openPRs": 4, "issuesOpened90d": 2, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 1, "success": 0, "failure": 1, "other": 0, "latest": "failure", "latestAt": "2026-10-18T11:50:02Z" }, "replies": { "sampled": 3, "unanswered": 3 } }, "updatedAt": "2026-11-07T22:55:56.869716412Z" } }, "answer": "ZeroBounce scores 62.4 (B) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments \u0026 pricing.", "b": { "slug": "zerobounce", "name": "ZeroBounce", "vendor": "Hertza L.L.C. (ZeroBounce)", "vendorUrl": "https://www.zerobounce.net", "kind": "http-api", "category": "lead-data", "summary": "ZeroBounce is an email verification API from Hertza L.L.C. that checks single addresses and lists for deliverability, with status and sub-status codes, plus AI scoring, email finder, domain search and activity data, and an open-source MCP server.", "url": "https://www.anchorterminal.com/tools/zerobounce", "markdownUrl": "https://www.anchorterminal.com/tools/zerobounce.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zerobounce.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zerobounce.json", "dns": "zerobounce.grade.anchorterminal.com", "repo": "https://github.com/zerobounce", "license": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.zerobounce.net/v2", "packages": [ { "registry": "npm", "name": "@zerobounce/zero-bounce-sdk" } ], "auth": "api-key", "authNotes": "API key from the dashboard, sent as the `api_key` query parameter in the documented calls. Several keys per account besides a Master key; keys can be named, switched off, regenerated, deleted and limited to whitelisted IPs or ranges. No endpoint scopes found.", "pricing": "usage", "pricingNotes": "Pay as you go from $39 for 2,000 validations, one credit per email, 20 per successful Email Finder query, nothing for unknown results. ZeroBounce ONE from $99 a month, minimum 10,000 credits. Freemium of 100 validations a month for business or premium domains. Credits bought after 1 June 2026 expire two years after the last purchase (https://www.zerobounce.net/pricing, https://www.zerobounce.net/terms-of-use, checked 2026-11-06).", "priceSummary": "$0.0195 / call", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing or MCP page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.zerobounce.net/docs/", "llmsTxt": "https://www.zerobounce.net/llms.txt", "capabilities": [ "email.verification", "email.finder", "lead.enrichment" ], "tags": [ "hosted", "mcp", "status-page", "soc2", "iso27001", "free-tier", "usage-based", "typescript", "eu-region", "closed-source" ], "lastRelease": "2026-10-25", "graded": true, "anchor": { "graded": true, "score": 62.4, "grade": "B", "agentReady": false, "rank": 561, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 70, "payments": 35, "reliability": 75, "schema": 54, "security": 65, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Email verification before outreach, the verification-first listing in lead-data.", "strengths": [ "Status and sub-status codes per address, and unknown results don't use credits", "Statuspage with API, API-US, API-EU and Bulk API components; three short incidents in the 90 days to 6 November 2026", "Rate limits published per endpoint group, with the block length for each", "SOC 2 Type 2, ISO/IEC 27001:2022, Intigriti testing and a published sub-processor list", "Freemium of 100 validations a month for business domains, and pay-as-you-go from $39 for 2,000" ], "weaknesses": [ "Every documented example sends the key as an `api_key` query parameter", "No OpenAPI or other machine-readable contract; a Postman collection only", "Going over a limit blocks the key for a minute to a day, with no Retry-After documented", "llms.txt lists marketing pages, not the API docs", "Keys can be IP-whitelisted but not scoped to endpoints" ], "agentNotes": [ "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_key` in the URL" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.4 } ], "editorialScores": { "ergonomics": 69, "maintenance": 70, "payments": 35, "reliability": 75, "schema": 54, "security": 65, "transparency": 59 }, "provenanceScore": 67, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.zerobounce.net/v2/validate?api_key=$ZEROBOUNCE_API_KEY\u0026email=valid@example.com\"" }, "letme": { "capability": "https://letme.dev/email.verification", "tool": "https://letme.dev/zerobounce" }, "area": "web-data", "unitPrices": [ { "item": "Email validation, smallest pay-as-you-go pack", "unit": "call", "usd": 0.0195, "note": "$39 for 2,000 validations" }, { "item": "ZeroBounce ONE", "unit": "month", "usd": 99, "note": "From $99 a month" } ], "provenance": { "legalEntity": "Hertza L.L.C.", "domain": "zerobounce.net", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zerobounce.net/terms-of-use", "privacy": "https://www.zerobounce.net/privacy-policy", "statusPage": "https://status.zerobounce.net", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-06", "notes": [ "Terms of use name Hertza L.L.C., doing business as ZeroBounce, a Nevada LLC, under Nevada law; the terms take effect on the date accepted. Privacy policy last updated 30 June 2026.", "www.zerobounce.net/robots.txt allows all and names ClaudeBot as allowed. status.zerobounce.net disallows /api/ and /embed/; its history was read from history.rss.", "No public changelog for the API was found.", "security.txt was not checked." ], "score": 67 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zerobounce.json", "live": { "slug": "zerobounce", "probe": { "target": "https://api.zerobounce.net/v2", "method": "get", "lastAt": "2026-11-07T22:56:32.424648348Z", "lastOk": true, "lastStatus": 404, "lastMs": 63, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 77, "p95ms24h": 170, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.zerobounce.net", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:57:55.637238875Z" }, "versions": [ { "registry": "npm", "name": "@zerobounce/zero-bounce-sdk", "version": "3.0.0", "seenAt": "2026-11-07T00:19:09.899173295Z" } ], "npmWeekly": 36734, "securityTxt": { "url": "https://zerobounce.net/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:52.305113224Z" }, "llmsTxt": { "url": "https://www.zerobounce.net/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:27.000344109Z" }, "pages": [ { "url": "https://www.zerobounce.net/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:37:41.302855774Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6cbf992fb3f3" }, { "url": "https://www.zerobounce.net/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:37:45.799553831Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6267cfec1592" }, { "url": "https://www.zerobounce.net/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:45.965675933Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "08727e5bbf09" } ], "updatedAt": "2026-11-07T22:57:55.637238875Z" } }, "edges": [ { "by": 42, "category": "maintenance", "leads": "zerobounce", "name": "Maintenance \u0026 community", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The last dated API change found is v2 general availability on 2 September 2026, 63 days before 4 November (20 of 30). No dated changelog, so three entries in 90 days could not be shown (0). Support by email and by a shared Slack channel for customers that have one, with no public changelog or forum (5 of 15). No official REST SDK found. The repository's `server.json` names `ai.explorium/mcp-explorium`, but no registry page could be read (0). The `mcp-explorium` repository is MIT, with its last commit on 22 January 2026 and only a publishing workflow, no CI (3 of 10). 20+0+5+0+3 = 28.", "b": "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." }, "scores": { "a": 28, "b": 70 } }, { "by": 33, "category": "reliability", "leads": "zerobounce", "name": "Reliability", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. Hosted lines. No status page found. The docs tell users to subscribe to status updates and link no page, and status.explorium.ai did not answer (0). No readable incident history (5). Rate limit published, 200 queries a minute per key over a 60-second sliding window, with each batch entity counted as a query (15). 429s carry `Retry-After` and `X-RateLimit-*` headers and the docs ask for exponential backoff. No idempotency keys were found for the webhook and enrolment writes, so safe-retry guidance without keys takes 12 (12). No SLA is published. The migration guide implies one exists by saying v1 loses its SLA at end of support (0). v2 reached general availability on 2 September 2026, though the conventions page still says request and response schemas are being finalised (10). 0+5+15+12+0+10 = 42.", "b": "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." }, "scores": { "a": 42, "b": 75 } }, { "by": 33, "category": "security", "leads": "zerobounce", "name": "Security \u0026 auth", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The docs say each company gets a single API key shared by all its users, sent in a header. The site's `auth.md` says a key can be deleted in the console, and the key page says to ask an administrator for a reset. No scopes (12 of 30). No read-only mode or per-key limits. The API mostly reads, writes are limited to webhooks and event enrolments, and auto-refill has an optional cap (5 of 20). Research scrapes web pages and the LinkedIn post enrichments return third-party text. No prompt-injection guidance was found in the docs (2 of 15). Balance and aggregation endpoints, per-call credit reporting, correlation IDs and last-active times for users. No per-call log was found (8 of 15). The privacy policy states SOC 2, ISO 27001 and ISO 27701, with no report, security.txt, disclosure policy or bug bounty found. A certification claim with no report or reporting route takes 5, as settled in this run (5 of 20). No GitHub-reviewed advisory names Explorium in the 12 months to 4 November. 12+5+2+8+5 = 32.", "b": "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." }, "scores": { "a": 32, "b": 65 } }, { "by": 14, "category": "schema", "leads": "zerobounce", "name": "Schema \u0026 documentation", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The OpenAPI 3.1 file read on 9 October has no recorded visible link from a docs page, and the host can't be re-read to find one, so it no longer counts as a published contract (0 of 25). llms.txt and a Markdown twin of every docs page (10). The docs pages and the 11 MCP tool descriptions say what each call is for and what to call first (12 of 20). The typed schemas, enums and item limits were read from that file, so they no longer count (0 of 15). Docs pages have request and response examples, and the error guide lists Partner ID header messages that don't match the `api_key` scheme (10 of 15). Versions live in the path with a migration guide and a full v2 change list. No dated changelog was found (8 of 15). 0+10+12+0+10+8 = 40.", "b": "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." }, "scores": { "a": 40, "b": 54 } }, { "by": 6, "category": "ergonomics", "leads": "zerobounce", "name": "Agent ergonomics", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The MCP v2 server has 11 tools (15), and the statistics tools are free for sizing an audience before a paid fetch (2 added back), 17 of 25. `page` and `page_size` up to 500, a `next_cursor` mode with no limit, and filters with autocomplete (20). Errors carry a `correlation_id`, 422 names the failing field, and Research returns failed rows with an `_error` field. Error bodies have no stable code (15 of 20). No idempotency keys. Retry guidance covers 429 and 500. MCP tool annotations were not read because we did not connect (6 of 20). No official REST SDK found in the docs index. Enrichment needs a match or fetch call first, and five filters need an autocomplete call first (5 of 15). 17+20+15+6+5 = 63.", "b": "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." }, "scores": { "a": 63, "b": 69 } }, { "by": 5, "category": "payments", "leads": "explorium-agentsource", "name": "Payments \u0026 pricing", "reasons": { "a": "Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. No x402, MPP or L402 (0). Credit pack prices and per-operation credit costs are public without a login (20). The pricing page and the site's own `pricing.md` disagree on two packs, which is recorded as a deduction and not here. Free trial of 100 credits for 90 days. No page read asks for a card at sign-up, and the auto-refill guide treats a payment method as something added later (20). The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint (0). Total 40.", "b": "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." }, "scores": { "a": 40, "b": 35 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Explorium Ltd.", "b": "Hertza L.L.C. (ZeroBounce)", "name": "Vendor" }, { "a": "https://api.explorium.ai", "b": "https://api.zerobounce.net/v2", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, SSE (legacy)", "b": "HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.15 per record", "b": "not published", "name": "Price for lead enrichment" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Explorium Terms of Use. The `mcp-explorium` repository of connection files is MIT", "b": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "name": "Licence" }, { "a": "11", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-02", "b": "2026-10-25", "name": "Last release" }, { "a": "2026-06-14", "b": "2026-05-05", "name": "Terms last updated" }, { "a": "2026-06-28", "b": "2026-06-30", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "ZeroBounce scores 62.4 (B) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Explorium AgentSource or ZeroBounce?" }, { "answer": "Both need an API key.", "question": "Do Explorium AgentSource and ZeroBounce need an API key?" }, { "answer": "Yes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and ZeroBounce at https://api.zerobounce.net/v2.", "question": "Can an agent call Explorium AgentSource and ZeroBounce without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 35" ], "also": null, "goodFor": "Agents that build prospect lists by filter and then enrich them, or that watch companies for events such as funding and role changes.", "slug": "explorium-agentsource", "watchFor": "No status page was found, and no SLA is published" }, { "aheadOn": [ "Reliability, 75 against 42", "Schema \u0026 documentation, 54 against 40", "Agent ergonomics, 69 against 63", "Security \u0026 auth, 65 against 32", "Maintenance \u0026 community, 70 against 28" ], "also": [ "Runs on your own machine" ], "goodFor": "Email verification before outreach, the verification-first listing in lead-data.", "slug": "zerobounce", "watchFor": "Every documented example sends the key as an `api_key` query parameter" } ], "history": { "explorium-agentsource": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-04", "delta": -6.7, "from": 48.2, "fromGrade": "D", "to": 41.5, "toGrade": "E" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 48.3, "fromGrade": "D", "to": 48.2, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 48.1, "fromGrade": "D", "to": 48.3, "toGrade": "D" } ], "zerobounce": null }, "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-explorium-agentsource.json", "title": "Apollo API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/apollo-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.json", "title": "Clay vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.json", "title": "Coresignal API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-explorium-agentsource.json", "title": "Crustdata API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/crustdata-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/dievio-vs-explorium-agentsource.json", "title": "Dievio vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/dievio-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-explorium-agentsource.json", "title": "Enrich Layer API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.json", "title": "Explorium AgentSource vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp.json", "title": "Explorium AgentSource vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-gojiberry.json", "title": "Explorium AgentSource vs Gojiberry", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter.json", "title": "Explorium AgentSource vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadmagic.json", "title": "Explorium AgentSource vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha.json", "title": "Explorium AgentSource vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs.json", "title": "Explorium AgentSource vs People Data Labs", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo.json", "title": "Explorium AgentSource vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach.json", "title": "Explorium AgentSource vs RocketReach API", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zoominfo.json", "title": "Explorium AgentSource vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zoominfo" }, { "json": "https://www.anchorterminal.com/compare/apollo-vs-zerobounce.json", "title": "Apollo API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/apollo-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-zerobounce.json", "title": "Clay vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/clay-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.json", "title": "Clearbit vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.json", "title": "Clearbit vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.json", "title": "Coresignal API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.json", "title": "Crustdata API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource.json", "title": "Databar vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/databar-vs-zerobounce.json", "title": "Databar vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/databar-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce.json", "title": "Dievio vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.json", "title": "Dropcontact API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.json", "title": "Dropcontact API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.json", "title": "Enrich Layer API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact.json", "title": "Explorium AgentSource vs FullContact", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.json", "title": "FullContact vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json", "title": "FullEnrich API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.json", "title": "Gojiberry vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.json", "title": "Lusha API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.json", "title": "People Data Labs vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.json", "title": "Prospeo API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.json", "title": "ZeroBounce vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo" }, { "json": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce.json", "title": "Hunter API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.json", "title": "Fuse MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.json", "title": "LeadMagic API + MCP vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.json", "title": "RocketReach API vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce" } ], "panel": null, "scores": [ { "by": 33, "edge": "zerobounce", "explorium-agentsource": 42, "key": "reliability", "name": "Reliability", "weight": 16, "zerobounce": 75 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "zerobounce", "explorium-agentsource": 40, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zerobounce": 54 }, { "by": 6, "edge": "zerobounce", "explorium-agentsource": 63, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zerobounce": 69 }, { "by": 33, "edge": "zerobounce", "explorium-agentsource": 32, "key": "security", "name": "Security \u0026 auth", "weight": 14, "zerobounce": 65 }, { "by": 5, "edge": "explorium-agentsource", "explorium-agentsource": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zerobounce": 35 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 42, "edge": "zerobounce", "explorium-agentsource": 28, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zerobounce": 70 }, { "by": 2, "edge": "zerobounce", "explorium-agentsource": 61, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zerobounce": 63 } ], "summary": "ZeroBounce scores 62.4 (B) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments \u0026 pricing. Both do lead enrichment.", "tasks": null, "tutorials": [], "verdicts": { "explorium-agentsource": "AgentSource v2 has Markdown docs, a 200 queries a minute limit with `Retry-After`, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, no specification file is linked from the docs, and the vendor's two published price tables disagree.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce", "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.min.md" }, "markdown": "ZeroBounce scores 62.4 (B) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments \u0026 pricing. Both do lead enrichment.\n\n- Explorium AgentSource: grade E, 41.5/100, rank #1299 of 1510. Markdown https://www.anchorterminal.com/tools/explorium-agentsource.md · JSON https://www.anchorterminal.com/api/v1/tools/explorium-agentsource.json\n- 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\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 231 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Explorium AgentSource (E)\n\nGood for: Agents that build prospect lists by filter and then enrich them, or that watch companies for events such as funding and role changes.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n\nWatch for: No status page was found, and no SLA is published\n\n### ZeroBounce (B)\n\nGood for: Email verification before outreach, the verification-first listing in lead-data.\n\nAhead on:\n- Reliability, 75 against 42\n- Schema \u0026 documentation, 54 against 40\n- Agent ergonomics, 69 against 63\n- Security \u0026 auth, 65 against 32\n- Maintenance \u0026 community, 70 against 28\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Every documented example sends the key as an `api_key` query parameter\n\n\n## Why the edge\n\n### Maintenance \u0026 community: ZeroBounce +42\n\n- Explorium AgentSource (28): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The last dated API change found is v2 general availability on 2 September 2026, 63 days before 4 November (20 of 30). No dated changelog, so three entries in 90 days could not be shown (0). Support by email and by a shared Slack channel for customers that have one, with no public changelog or forum (5 of 15). No official REST SDK found. The repository's `server.json` names `ai.explorium/mcp-explorium`, but no registry page could be read (0). The `mcp-explorium` repository is MIT, with its last commit on 22 January 2026 and only a publishing workflow, no CI (3 of 10). 20+0+5+0+3 = 28.\n- 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.\n\n### Reliability: ZeroBounce +33\n\n- Explorium AgentSource (42): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. Hosted lines. No status page found. The docs tell users to subscribe to status updates and link no page, and status.explorium.ai did not answer (0). No readable incident history (5). Rate limit published, 200 queries a minute per key over a 60-second sliding window, with each batch entity counted as a query (15). 429s carry `Retry-After` and `X-RateLimit-*` headers and the docs ask for exponential backoff. No idempotency keys were found for the webhook and enrolment writes, so safe-retry guidance without keys takes 12 (12). No SLA is published. The migration guide implies one exists by saying v1 loses its SLA at end of support (0). v2 reached general availability on 2 September 2026, though the conventions page still says request and response schemas are being finalised (10). 0+5+15+12+0+10 = 42.\n- 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.\n\n### Security \u0026 auth: ZeroBounce +33\n\n- Explorium AgentSource (32): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The docs say each company gets a single API key shared by all its users, sent in a header. The site's `auth.md` says a key can be deleted in the console, and the key page says to ask an administrator for a reset. No scopes (12 of 30). No read-only mode or per-key limits. The API mostly reads, writes are limited to webhooks and event enrolments, and auto-refill has an optional cap (5 of 20). Research scrapes web pages and the LinkedIn post enrichments return third-party text. No prompt-injection guidance was found in the docs (2 of 15). Balance and aggregation endpoints, per-call credit reporting, correlation IDs and last-active times for users. No per-call log was found (8 of 15). The privacy policy states SOC 2, ISO 27001 and ISO 27701, with no report, security.txt, disclosure policy or bug bounty found. A certification claim with no report or reporting route takes 5, as settled in this run (5 of 20). No GitHub-reviewed advisory names Explorium in the 12 months to 4 November. 12+5+2+8+5 = 32.\n- 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.\n\n### Schema \u0026 documentation: ZeroBounce +14\n\n- Explorium AgentSource (40): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The OpenAPI 3.1 file read on 9 October has no recorded visible link from a docs page, and the host can't be re-read to find one, so it no longer counts as a published contract (0 of 25). llms.txt and a Markdown twin of every docs page (10). The docs pages and the 11 MCP tool descriptions say what each call is for and what to call first (12 of 20). The typed schemas, enums and item limits were read from that file, so they no longer count (0 of 15). Docs pages have request and response examples, and the error guide lists Partner ID header messages that don't match the `api_key` scheme (10 of 15). Versions live in the path with a migration guide and a full v2 change list. No dated changelog was found (8 of 15). 0+10+12+0+10+8 = 40.\n- 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.\n\n### Agent ergonomics: ZeroBounce +6\n\n- Explorium AgentSource (63): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The MCP v2 server has 11 tools (15), and the statistics tools are free for sizing an audience before a paid fetch (2 added back), 17 of 25. `page` and `page_size` up to 500, a `next_cursor` mode with no limit, and filters with autocomplete (20). Errors carry a `correlation_id`, 422 names the failing field, and Research returns failed rows with an `_error` field. Error bodies have no stable code (15 of 20). No idempotency keys. Retry guidance covers 429 and 500. MCP tool annotations were not read because we did not connect (6 of 20). No official REST SDK found in the docs index. Enrichment needs a match or fetch call first, and five filters need an autocomplete call first (5 of 15). 17+20+15+6+5 = 63.\n- 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.\n\n### Payments \u0026 pricing: Explorium AgentSource +5\n\n- Explorium AgentSource (40): Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. No x402, MPP or L402 (0). Credit pack prices and per-operation credit costs are public without a login (20). The pricing page and the site's own `pricing.md` disagree on two packs, which is recorded as a deduction and not here. Free trial of 100 credits for 90 days. No page read asks for a card at sign-up, and the auto-refill guide treats a payment method as something added later (20). The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint (0). Total 40.\n- 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.\n\n## Score by category\n\n| Category | Weight | Explorium AgentSource | ZeroBounce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 42 | 75 | ZeroBounce +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 54 | ZeroBounce +14 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 69 | ZeroBounce +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 32 | 65 | ZeroBounce +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Explorium AgentSource +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 70 | ZeroBounce +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 63 | ZeroBounce +2 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **41.5 · E** | **62.4 · B** | |\n\n## Facts side by side\n\n| Fact | Explorium AgentSource | ZeroBounce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Explorium Ltd. | Hertza L.L.C. (ZeroBounce) |\n| Hosted endpoint | `https://api.explorium.ai` | `https://api.zerobounce.net/v2` |\n| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, stdio |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for lead enrichment | $0.15 per record | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the Explorium Terms of Use. The `mcp-explorium` repository of connection files is MIT | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |\n| Tools exposed | 11 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-02 | 2026-10-25 |\n| Terms last updated | 2026-06-14 | 2026-05-05 |\n| Privacy policy last updated | 2026-06-28 | 2026-06-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## How the scores have moved\n\n### Explorium AgentSource\n\n- -6.7 on 4 November 2026 (D to E): new evidence, correction\n- -0.1 on 28 October 2026: correction\n- +0.2 on 27 October 2026: checklist\n\n### ZeroBounce\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Explorium AgentSource.** AgentSource v2 has Markdown docs, a 200 queries a minute limit with `Retry-After`, public credit prices and a 100-credit trial. No status page or published SLA was found, each company shares one API key with no scopes, no specification file is linked from the docs, and the vendor's two published price tables disagree.\n\n**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.\n\n## Before you call either\n\n### Explorium AgentSource\n\n1. Send the key in the `api_key` header to `https://api.explorium.ai` and use `/v2` paths. v1 is deprecated\n2. Point MCP clients at `https://mcp-v2.explorium.ai/mcp`. The site's agent files still name the v1 server at `mcp.explorium.ai`\n3. Count each entity in a batch as one query against the 200 a minute limit, so 50 IDs in one call spend 50\n4. Call the statistics endpoint first to size an audience for free. Fetch costs 1 credit a result, or 2 with the Bombora intent filter\n5. Call `/v2/autocomplete` before filtering on category, tech stack or job title, and never mix two category types in one request\n\n### ZeroBounce\n\n1. Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits\n2. Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later\n3. Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour\n4. Use the bulk file API for large lists instead of looping on /v2/validate\n5. Keep the key out of logs; the API takes it only as `api_key` in the URL\n\n## Questions\n\n### Which is better for AI agents, Explorium AgentSource or ZeroBounce?\n\nZeroBounce scores 62.4 (B) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 6 of 7 scored categories. Explorium AgentSource leads on payments \u0026 pricing.\n\n### Do Explorium AgentSource and ZeroBounce need an API key?\n\nBoth need an API key.\n\n### Can an agent call Explorium AgentSource and ZeroBounce without installing anything?\n\nYes. Explorium AgentSource has a hosted endpoint at https://api.explorium.ai and ZeroBounce at https://api.zerobounce.net/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"explorium-agentsource\", \"b\": \"zerobounce\"}`. From a terminal: `anchor compare explorium-agentsource zerobounce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/explorium-agentsource.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n\n## Other comparisons with Explorium AgentSource or ZeroBounce\n\n- [Apollo API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/apollo-vs-explorium-agentsource.md)\n- [Clay vs Explorium AgentSource](https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.md)\n- [Coresignal API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.md)\n- [Crustdata API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/crustdata-vs-explorium-agentsource.md)\n- [Dievio vs Explorium AgentSource](https://www.anchorterminal.com/compare/dievio-vs-explorium-agentsource.md)\n- [Enrich Layer API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/enrich-layer-vs-explorium-agentsource.md)\n- [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md)\n- [Explorium AgentSource vs Fuse MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fuse-mcp.md)\n- [Explorium AgentSource vs Gojiberry](https://www.anchorterminal.com/compare/explorium-agentsource-vs-gojiberry.md)\n- [Explorium AgentSource vs Hunter API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter.md)\n- [Explorium AgentSource vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadmagic.md)\n- [Explorium AgentSource vs Lusha API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-lusha.md)\n- [Explorium AgentSource vs People Data Labs](https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs.md)\n- [Explorium AgentSource vs Prospeo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo.md)\n- [Explorium AgentSource vs RocketReach API](https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach.md)\n- [Explorium AgentSource vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zoominfo.md)\n- [Apollo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)\n- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)\n- [Clearbit vs Explorium AgentSource](https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.md)\n- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md)\n- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)\n- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)\n- [Databar vs Explorium AgentSource](https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource.md)\n- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)\n- [Dievio vs ZeroBounce](https://www.anchorterminal.com/compare/dievio-vs-zerobounce.md)\n- [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md)\n- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)\n- [Enrich Layer API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.md)\n- [Explorium AgentSource vs FullContact](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact.md)\n- [FullContact vs ZeroBounce](https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.md)\n- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)\n- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)\n- [Lusha API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md)\n- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)\n- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)\n- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)\n- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.md)\n- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)\n- [LeadMagic API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md)\n- [RocketReach API vs ZeroBounce](https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Explorium AgentSource vs ZeroBounce", "url": "" } ], "description": "ZeroBounce scores 62.4 (B) to Explorium AgentSource's 41.5 (E) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Explorium AgentSource E 41.5", "ZeroBounce B 62.4", "scores" ], "h1": "Explorium AgentSource vs ZeroBounce", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/explorium-agentsource-vs-zerobounce", "published": "2026-10-01", "section": "tools", "title": "Explorium AgentSource vs ZeroBounce for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce" }, "tokens": { "markdown": 5250, "slim": 2880 }, "version": 1 }