{ "data": { "a": { "slug": "prospeo", "name": "Prospeo API + MCP", "vendor": "Prospeo", "vendorUrl": "https://prospeo.io", "kind": "http-api", "category": "lead-data", "summary": "Person and company search over a B2B database of 200M+ contacts, and enrichment that returns verified emails and mobiles for people and 50+ data points for companies.", "url": "https://www.anchorterminal.com/tools/prospeo", "markdownUrl": "https://www.anchorterminal.com/tools/prospeo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/prospeo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/prospeo.json", "dns": "prospeo.grade.anchorterminal.com", "repo": "https://github.com/prospeo-v2/prospeo-mcp-server", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.prospeo.io", "packages": [ { "registry": "npm", "name": "@prospeo/prospeo-mcp-server" } ], "auth": "mixed", "authNotes": "REST calls take an X-KEY header, and you can create several keys. The hosted MCP server at https://mcp.prospeo.io accepts OAuth or the same X-KEY header. The local npm server reads PROSPEO_API_KEY.", "pricing": "freemium", "pricingNotes": "Free plan with 100 credits a month. Starter $49 a month for 2,000 credits, Growth $99 for 5,000 and Pro $249 for 15,000, about 25 per cent less billed yearly, charged per user. Credits reset each cycle. Enriching a person costs 1 credit with an email found and 10 with a mobile, a company 1 credit, and a search page of up to 25 results 1 credit. Re-enriching within 90 days is free (https://prospeo.io/pricing).", "priceSummary": "$49 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": 8, "popularity": { "githubStars": 0, "npmWeekly": 641, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://prospeo.io/api-docs", "registryName": "io.prospeo/prospeo-mcp-server", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.person", "data.company" ], "tags": [ "hosted", "freemium", "mcp", "local", "typescript", "closed-source", "lead-search", "enrichment" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 51.1, "grade": "D", "agentReady": false, "rank": 1040, "ranked": true, "rankOf": 1510, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 19, "payments": 40, "reliability": 35, "schema": 61, "security": 54, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.", "bestFor": "An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.", "strengths": [ "MCP tool descriptions say when to use each tool, its credit cost and the next call", "All 8 MCP tools in release 1.1.1 annotated readOnlyHint true and destructiveHint false", "Repeat searches within 30 days and re-enrichment within 90 days are free", "Terms promise at least 90 days' notice of breaking changes to public API endpoints", "Free plan with 100 credits a month and API access" ], "weaknesses": [ "No status page, SLA or changelog", "Most errors, including internal ones, return HTTP 400", "No OpenAPI file or llms.txt for the REST API", "No MCP code release since 1.1.0 on 1 June 2026. 1.1.1 on 13 October changed packaging only", "Terms take a perpetual, irrevocable licence to uploaded contact data, kept after an account closes" ], "agentNotes": [ "Call `search_suggestions` before using location, technology or industry filters, or the search returns nothing", "Pass `person_id` values from search into `bulk_enrich_person`, 25 at a time", "Branch on the body `error_code`, not the HTTP status, which is 400 for most failures", "Set `enrich_mobile` only when needed. A mobile costs 10 credits against 1 for an email", "Use Enrich Person. The old Email Finder endpoint was removed in March 2026" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.1 } ], "editorialScores": { "ergonomics": 79, "maintenance": 19, "payments": 40, "reliability": 35, "schema": 61, "security": 54, "transparency": 66 }, "provenanceScore": 53, "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 https://api.prospeo.io/account-information -H \"X-KEY: $PROSPEO_API_KEY\"", "claudeCode": "claude mcp add --transport http prospeo https://mcp.prospeo.io", "config": { "mcpServers": { "prospeo": { "args": [ "-y", "@prospeo/prospeo-mcp-server" ], "command": "npx", "env": { "PROSPEO_API_KEY": "${PROSPEO_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/prospeo" }, "area": "web-data", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 49, "note": "2,000 credits, per user" }, { "item": "Growth", "unit": "month", "usd": 99, "note": "5,000 credits, per user" }, { "item": "Pro", "unit": "month", "usd": 249, "note": "15,000 credits, per user" } ], "provenance": { "legalEntity": "Defastra Tech Inc.", "domain": "prospeo.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://prospeo.io/terms-of-service", "privacy": "https://prospeo.io/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "Prospeo is a trading name of Defastra Tech Inc. per the privacy policy. RDAP has no record for .io domains.", "status.prospeo.io doesn't resolve, and the API docs link no status page (2 October 2026).", "The terms render by script, but their text is in the page's own data, read on 4 November 2026. They carry no date, say Prospeo is a Canadian company with primary hosting on AWS us-east-1, and bar robots and other automated means outside the public API, so nothing else on prospeo.io was requested that day." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/prospeo.json", "live": { "slug": "prospeo", "probe": { "target": "https://api.prospeo.io", "method": "get", "lastAt": "2026-11-07T19:22:28.03339578Z", "lastOk": true, "lastStatus": 429, "lastMs": 31, "lastNote": "rate limited", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 29, "p95ms24h": 101, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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": 197, "ok": 197 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.prospeo/prospeo-mcp-server", "version": "1.1.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@prospeo/prospeo-mcp-server", "version": "1.1.1", "seenAt": "2026-11-06T23:58:47.079705095Z" } ], "githubStars": 0, "npmWeekly": 453, "securityTxt": { "url": "https://prospeo.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:52.067461965Z" }, "domain": { "domain": "prospeo.io", "checkedAt": "2026-11-01T14:19:02.125335796Z" }, "pages": [ { "url": "https://prospeo.io/api-docs/email-finder", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:17:32.331211529Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "31857220e7cb" }, { "url": "https://prospeo.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:17:35.486155819Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7a2b15d0bd55" }, { "url": "https://prospeo.io/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:17:36.553063089Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "474d26a8c22c" }, { "url": "https://prospeo.io/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:17:38.353340341Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "65c942c41696" } ], "mcpTools": { "url": "https://mcp.prospeo.io", "checkedAt": "2026-11-07T01:46:55.545200197Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:55.545200197Z" }, "github": { "repo": "prospeo-v2/prospeo-mcp-server", "checkedAt": "2026-11-02T09:18:48.032139922Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-18T19:04:57Z", "openIssues": 2, "openPRs": 0, "issuesOpened90d": 2, "issuesClosed90d": 0, "prsMerged90d": 2, "replies": { "sampled": 2, "unanswered": 2 } }, "updatedAt": "2026-11-07T19:22:28.03339578Z" } }, "answer": "ZeroBounce scores 62.4 (B) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on schema \u0026 documentation, agent ergonomics and 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-07T19:22:46.255334057Z", "lastOk": true, "lastStatus": 404, "lastMs": 94, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 70, "p95ms24h": 170, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.zerobounce.net", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:24:02.77448048Z" }, "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-07T19:24:02.77448048Z" } }, "edges": [ { "by": 51, "category": "maintenance", "leads": "zerobounce", "name": "Maintenance \u0026 community", "reasons": { "a": "The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow, so it is a packaging release that counts half and can't set recency. Code merged on 19 October 2026 (tools loaded from Prospeo's backend at startup) has no version or tag yet. The newest release that changes code is 1.1.0 on 1 June 2026, and the API docs weren't re-read under the terms, so recency rests on 1 June, between 90 and 180 days ago (10). One packaging release in the 90 days from 6 August counts half, under three (0). No changelog, and the MCP repo's commits are all from staff. We couldn't see issue handling from git (5 of 25). server.json names io.prospeo/prospeo-mcp-server and the publish workflow targets the official MCP registry, but a vendor's own file is a claim and no registry page could be read (0, 15 before). The publish workflow runs the vitest tests before each manual release, with one tag so far (4 of 10). 10 + 0 + 5 + 0 + 4 = 19.", "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": 19, "b": 70 } }, { "by": 40, "category": "reliability", "leads": "zerobounce", "name": "Reliability", "reasons": { "a": "Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with `x-daily-request-left` and `x-minute-request-left` headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).", "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": 35, "b": 75 } }, { "by": 11, "category": "security", "leads": "zerobounce", "name": "Security \u0026 auth", "reasons": { "a": "Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. Keys in the `X-KEY` header, several keys per account. The hosted MCP takes OAuth or the same header (22 of 30). Every tool reads, and the MCP marks them so (16 of 20). Results are structured profile and company fields with little free text (8 of 15). Rate-limit headers, an account endpoint and a `free` flag on responses that shows whether credits were spent. No per-call log found (8 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). No 2025 or 2026 record in the CVE list names Prospeo. 22 + 16 + 8 + 8 + 0 = 54.", "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": 54, "b": 65 } }, { "by": 10, "category": "ergonomics", "leads": "prospeo", "name": "Agent ergonomics", "reasons": { "a": "Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free `search_suggestions` tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).", "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": 79, "b": 69 } }, { "by": 7, "category": "schema", "leads": "prospeo", "name": "Schema \u0026 documentation", "reasons": { "a": "Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body `error_code` values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).", "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": 61, "b": 54 } }, { "by": 5, "category": "payments", "leads": "prospeo", "name": "Payments \u0026 pricing", "reasons": { "a": "Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No x402, MPP or L402 (0). Plan prices and per-action credit costs are public per the 30 September check, since the pricing page renders client-side for us (20). Free plan with 100 credits a month, and the docs say API access is free for all users (20). A person signs up in a browser (0).", "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": "Prospeo", "b": "Hertza L.L.C. (ZeroBounce)", "name": "Vendor" }, { "a": "https://api.prospeo.io", "b": "https://api.zerobounce.net/v2", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source", "name": "Licence" }, { "a": "8", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "io.prospeo/prospeo-mcp-server", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-13", "b": "2026-10-25", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-05-05", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-06-30", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "0 stars, 641 npm/wk", "b": "none", "name": "Popularity" }, { "a": "3.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "ZeroBounce scores 62.4 (B) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Prospeo API + MCP or ZeroBounce?" }, { "answer": "Prospeo API + MCP takes an API key or an OAuth sign-in. ZeroBounce needs an API key.", "question": "Do Prospeo API + MCP and ZeroBounce need an API key?" }, { "answer": "Yes. Prospeo API + MCP has a hosted endpoint at https://api.prospeo.io and ZeroBounce at https://api.zerobounce.net/v2.", "question": "Can an agent call Prospeo API + MCP and ZeroBounce without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 61 against 54", "Agent ergonomics, 79 against 69", "Payments \u0026 pricing, 40 against 35" ], "also": null, "goodFor": "An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.", "slug": "prospeo", "watchFor": "No status page, SLA or changelog" }, { "aheadOn": [ "Reliability, 75 against 35", "Security \u0026 auth, 65 against 54", "Maintenance \u0026 community, 70 against 19" ], "also": null, "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": { "prospeo": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-04", "delta": 0.1, "from": 51, "fromGrade": "D", "to": 51.1, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50.9, "fromGrade": "D", "to": 51, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 51.1, "fromGrade": "D", "to": 50.9, "toGrade": "D" } ], "zerobounce": null }, "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-prospeo.json", "title": "Apollo API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/apollo-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-prospeo.json", "title": "Clay vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-prospeo.json", "title": "Coresignal API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-prospeo.json", "title": "Crustdata API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/crustdata-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/dievio-vs-prospeo.json", "title": "Dievio vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/dievio-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo.json", "title": "Enrich Layer API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo" }, { "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/fullenrich-vs-prospeo.json", "title": "FullEnrich API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo.json", "title": "Fuse MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/gojiberry-vs-prospeo.json", "title": "Gojiberry vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/gojiberry-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/leadmagic-vs-prospeo.json", "title": "LeadMagic API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/leadmagic-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/lusha-vs-prospeo.json", "title": "Lusha API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/lusha-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.json", "title": "People Data Labs vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/prospeo-vs-rocketreach.json", "title": "Prospeo API + MCP vs RocketReach API", "url": "https://www.anchorterminal.com/compare/prospeo-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/prospeo-vs-zoominfo.json", "title": "Prospeo API + MCP vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/prospeo-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-prospeo.json", "title": "Clearbit vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-prospeo" }, { "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-prospeo.json", "title": "Databar vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/databar-vs-prospeo" }, { "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-prospeo.json", "title": "Dropcontact API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-prospeo" }, { "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-zerobounce.json", "title": "Explorium AgentSource vs ZeroBounce", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.json", "title": "FullContact vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-prospeo" }, { "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/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-prospeo.json", "title": "Hunter API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/hunter-vs-prospeo" }, { "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": 40, "edge": "zerobounce", "key": "reliability", "name": "Reliability", "prospeo": 35, "weight": 16, "zerobounce": 75 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "edge": "prospeo", "key": "schema", "name": "Schema \u0026 documentation", "prospeo": 61, "weight": 13, "zerobounce": 54 }, { "by": 10, "edge": "prospeo", "key": "ergonomics", "name": "Agent ergonomics", "prospeo": 79, "weight": 13, "zerobounce": 69 }, { "by": 11, "edge": "zerobounce", "key": "security", "name": "Security \u0026 auth", "prospeo": 54, "weight": 14, "zerobounce": 65 }, { "by": 5, "edge": "prospeo", "key": "payments", "name": "Payments \u0026 pricing", "prospeo": 40, "weight": 10, "zerobounce": 35 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 51, "edge": "zerobounce", "key": "maintenance", "name": "Maintenance \u0026 community", "prospeo": 19, "weight": 7, "zerobounce": 70 }, { "by": 3, "edge": "zerobounce", "key": "transparency", "name": "Transparency \u0026 trust", "prospeo": 60, "weight": 7, "zerobounce": 63 } ], "summary": "ZeroBounce scores 62.4 (B) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do lead enrichment.", "tasks": null, "tutorials": [], "verdicts": { "prospeo": "MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.", "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/prospeo-vs-zerobounce", "json": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.min.md" }, "markdown": "ZeroBounce scores 62.4 (B) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do lead enrichment.\n\n- Prospeo API + MCP: grade D, 51.1/100, rank #1040 of 1510. Markdown https://www.anchorterminal.com/tools/prospeo.md · JSON https://www.anchorterminal.com/api/v1/tools/prospeo.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### Prospeo API + MCP (D)\n\nGood for: An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.\n\nAhead on:\n- Schema \u0026 documentation, 61 against 54\n- Agent ergonomics, 79 against 69\n- Payments \u0026 pricing, 40 against 35\n\nWatch for: No status page, SLA or changelog\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 35\n- Security \u0026 auth, 65 against 54\n- Maintenance \u0026 community, 70 against 19\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 +51\n\n- Prospeo API + MCP (19): The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow, so it is a packaging release that counts half and can't set recency. Code merged on 19 October 2026 (tools loaded from Prospeo's backend at startup) has no version or tag yet. The newest release that changes code is 1.1.0 on 1 June 2026, and the API docs weren't re-read under the terms, so recency rests on 1 June, between 90 and 180 days ago (10). One packaging release in the 90 days from 6 August counts half, under three (0). No changelog, and the MCP repo's commits are all from staff. We couldn't see issue handling from git (5 of 25). server.json names io.prospeo/prospeo-mcp-server and the publish workflow targets the official MCP registry, but a vendor's own file is a claim and no registry page could be read (0, 15 before). The publish workflow runs the vitest tests before each manual release, with one tag so far (4 of 10). 10 + 0 + 5 + 0 + 4 = 19.\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 +40\n\n- Prospeo API + MCP (35): Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with `x-daily-request-left` and `x-minute-request-left` headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).\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 +11\n\n- Prospeo API + MCP (54): Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. Keys in the `X-KEY` header, several keys per account. The hosted MCP takes OAuth or the same header (22 of 30). Every tool reads, and the MCP marks them so (16 of 20). Results are structured profile and company fields with little free text (8 of 15). Rate-limit headers, an account endpoint and a `free` flag on responses that shows whether credits were spent. No per-call log found (8 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). No 2025 or 2026 record in the CVE list names Prospeo. 22 + 16 + 8 + 8 + 0 = 54.\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### Agent ergonomics: Prospeo API + MCP +10\n\n- Prospeo API + MCP (79): Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free `search_suggestions` tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).\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### Schema \u0026 documentation: Prospeo API + MCP +7\n\n- Prospeo API + MCP (61): Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body `error_code` values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).\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### Payments \u0026 pricing: Prospeo API + MCP +5\n\n- Prospeo API + MCP (40): Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No x402, MPP or L402 (0). Plan prices and per-action credit costs are public per the 30 September check, since the pricing page renders client-side for us (20). Free plan with 100 credits a month, and the docs say API access is free for all users (20). A person signs up in a browser (0).\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 | Prospeo API + MCP | ZeroBounce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 75 | ZeroBounce +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 54 | Prospeo API + MCP +7 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 69 | Prospeo API + MCP +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 65 | ZeroBounce +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Prospeo API + MCP +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 19 | 70 | ZeroBounce +51 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 63 | ZeroBounce +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **51.1 · D** | **62.4 · B** | |\n\n## Facts side by side\n\n| Fact | Prospeo API + MCP | ZeroBounce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Prospeo | Hertza L.L.C. (ZeroBounce) |\n| Hosted endpoint | `https://api.prospeo.io` | `https://api.zerobounce.net/v2` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |\n| Tools exposed | 8 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | `io.prospeo/prospeo-mcp-server` | not listed |\n| Last release | 2026-10-13 | 2026-10-25 |\n| Terms last updated | couldn't be read | 2026-05-05 |\n| Privacy policy last updated | couldn't be read | 2026-06-30 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 0 stars, 641 npm/wk | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Prospeo API + MCP\n\n- +0.1 on 4 November 2026: new evidence, correction\n- +0.1 on 27 October 2026: checklist\n- -0.2 on 8 October 2026: checklist\n\n### ZeroBounce\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Prospeo API + MCP.** MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.\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### Prospeo API + MCP\n\n1. Call `search_suggestions` before using location, technology or industry filters, or the search returns nothing\n2. Pass `person_id` values from search into `bulk_enrich_person`, 25 at a time\n3. Branch on the body `error_code`, not the HTTP status, which is 400 for most failures\n4. Set `enrich_mobile` only when needed. A mobile costs 10 credits against 1 for an email\n5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026\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, Prospeo API + MCP or ZeroBounce?\n\nZeroBounce scores 62.4 (B) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.\n\n### Do Prospeo API + MCP and ZeroBounce need an API key?\n\nProspeo API + MCP takes an API key or an OAuth sign-in. ZeroBounce needs an API key.\n\n### Can an agent call Prospeo API + MCP and ZeroBounce without installing anything?\n\nYes. Prospeo API + MCP has a hosted endpoint at https://api.prospeo.io and ZeroBounce at https://api.zerobounce.net/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"prospeo\", \"b\": \"zerobounce\"}`. From a terminal: `anchor compare prospeo zerobounce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/prospeo.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n\n## Other comparisons with Prospeo API + MCP or ZeroBounce\n\n- [Apollo API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/apollo-vs-prospeo.md)\n- [Clay vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clay-vs-prospeo.md)\n- [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md)\n- [Crustdata API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-prospeo.md)\n- [Dievio vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dievio-vs-prospeo.md)\n- [Enrich Layer API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo.md)\n- [Explorium AgentSource vs Prospeo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo.md)\n- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)\n- [Fuse MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo.md)\n- [Gojiberry vs Prospeo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-prospeo.md)\n- [LeadMagic API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadmagic-vs-prospeo.md)\n- [Lusha API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-prospeo.md)\n- [People Data Labs vs Prospeo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.md)\n- [Prospeo API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/prospeo-vs-rocketreach.md)\n- [Prospeo API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/prospeo-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 Prospeo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-prospeo.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 Prospeo API + MCP](https://www.anchorterminal.com/compare/databar-vs-prospeo.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 Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.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 ZeroBounce](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md)\n- [FullContact vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.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- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)\n- [Hunter API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-prospeo.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": "Prospeo API + MCP vs ZeroBounce", "url": "" } ], "description": "ZeroBounce scores 62.4 (B) to Prospeo's 51.1 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Prospeo API + MCP D 51.1", "ZeroBounce B 62.4", "scores" ], "h1": "Prospeo API + MCP vs ZeroBounce", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/prospeo-vs-zerobounce", "published": "2026-10-01", "section": "tools", "title": "Prospeo vs ZeroBounce for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce" }, "tokens": { "markdown": 4900, "slim": 2730 }, "version": 1 }