{ "data": { "a": { "slug": "clay", "name": "Clay", "vendor": "Clay Labs Inc.", "vendorUrl": "https://www.clay.com", "kind": "http-api", "category": "lead-data", "summary": "Clay is a go-to-market data and automation platform that searches its own database of companies and people and runs enrichment across 150+ data providers. Agents use it through the Public API v0, the clay CLI and a coding-agent plugin.", "url": "https://www.anchorterminal.com/tools/clay", "markdownUrl": "https://www.anchorterminal.com/tools/clay.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clay.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clay.json", "repo": "https://github.com/clay-run/agent-plugins", "license": "Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file", "transports": [ "http" ], "remoteUrl": "https://api.clay.com/public/v0", "packages": [], "auth": "mixed", "authNotes": "The Public API takes a personal API key in the clay-api-key header, tied to a Clay user and their workspace access, created in the app, with the CLI (clay api-keys create) or by an agent through the plugin. The CLI signs in with OAuth in a browser or with a device code (clay login --device), one workspace per sign-in. Custom functions need API or MCP access switched on per function (https://developers.clay.com/public-api/authentication).", "pricing": "freemium", "pricingNotes": "Free plan with 100 data credits and 500 actions a month. Launch from $167 a month and Growth from $446 a month on the plan cards, while the FAQ on the same page says $185 and $495. Data credits start at $0.05 and actions at under a cent. Failed enrichments aren't charged. The FAQ lists Clay API access under Enterprise, while the developer docs give search limits for Free, Trial and paid plans (https://www.clay.com/pricing, https://developers.clay.com/searches, checked 2026-10-14).", "priceSummary": "$0.05 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://developers.clay.com", "llmsTxt": "https://developers.clay.com/llms.txt", "openapi": "https://developers.clay.com/openapi.json", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.company" ], "tags": [ "hosted", "freemium", "api-key", "openapi", "llms-txt", "cli", "closed-source", "lead-search", "enrichment", "soc2", "webhooks" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 57.7, "grade": "C", "agentReady": false, "rank": 633, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 75, "payments": 30, "reliability": 45, "schema": 84, "security": 48, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.", "bestFor": "Agents building prospect lists and enriching contacts or accounts through many providers at once.", "strengths": [ "Public OpenAPI spec, llms.txt and Markdown copies of the docs", "Search and enrichment across Clay's database and 150+ providers through one API", "Failed enrichments use no credits or actions", "CLI with JSON output and typed exit codes, released five times between 25 September and 6 October 2026", "Valid security.txt and SOC 2 Type II listed" ], "weaknesses": [ "API keys carry no scopes and act with the user's workspace access", "The Claude Code plugin auto-approves most clay CLI commands, including ones that spend credits", "No request-rate number published, and error bodies have no stable codes", "Privacy policy dated September 2020 with no retention periods", "Pricing page gives two different prices for Launch and Growth, and says API access is Enterprise" ], "agentNotes": [ "Fetch GET /search/query-mode/reference before writing a search query", "Poll routine results until a terminal 200, since 202 means still running", "Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date", "Check GET /credits/balance before large batch runs", "Ask the user before enabling the plugin's auto-approve hook in a shared workspace" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.7 } ], "editorialScores": { "ergonomics": 66, "maintenance": 75, "payments": 30, "reliability": 45, "schema": 84, "security": 48, "transparency": 28 }, "provenanceScore": 99 }, "connect": { "http": "curl https://api.clay.com/public/v0/me \\\n -H \"clay-api-key: $CLAY_PUBLIC_API_KEY\"", "claudeCode": "Set up the Clay plugin by following the steps in https://github.com/clay-run/agent-plugins" }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/clay" }, "area": "web-data", "unitPrices": [ { "item": "Data credit", "unit": "credit", "usd": 0.05, "note": "Starting price per the pricing FAQ. Used when buying data from Clay's providers. Cheaper at volume" }, { "item": "Launch plan", "unit": "month", "usd": 167, "note": "Plan card headline. The FAQ says from $185 a month" } ], "provenance": { "legalEntity": "Clay Labs Inc.", "domain": "clay.com", "domainRegistered": "1992-11-13", "endpointOnVendorDomain": true, "terms": "https://www.clay.com/terms-of-service", "privacy": "https://www.clay.com/privacy", "statusPage": "https://status.clay.com", "changelog": "https://www.clay.com/changelog", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "The terms (last updated 23 May 2024) name Clay Labs Inc. with New York law. The privacy policy is dated 11 September 2020.", "clay.com/.well-known/security.txt names security@clay.com and trust.clay.com, expiring 2027-07-31.", "status.clay.com answered with a bot check to both curl and WebFetch, so its components and history weren't read.", "The API answers at api.clay.com and the docs at developers.clay.com.", "RDAP gives clay.com a registration date of 1992-11-13." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/clay.json", "live": { "slug": "clay", "probe": { "target": "https://api.clay.com/public/v0", "method": "get", "lastAt": "2026-10-14T10:27:57.120711351Z", "lastOk": true, "lastStatus": 401, "lastMs": 417, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 149, "p95ms24h": 417, "samples24h": 25, "samples30d": 25, "days": [ { "date": "2026-10-14", "probes": 25, "ok": 25 } ] }, "vendorStatus": { "page": "https://status.clay.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:52:50.29728454Z" }, "updatedAt": "2026-10-14T10:27:57.120711351Z" } }, "answer": "Clay scores 57.7 (C) on agent readiness against Prospeo API + MCP's 50.9 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.", "b": { "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", "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-06-01", "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 814, "ranked": true, "rankOf": 1076, "categoryRank": 15, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 34, "payments": 40, "reliability": 35, "schema": 61, "security": 54, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-01" }, "negative": 0, "verdict": "MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.", "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 annotated readOnlyHint true and destructiveHint false", "Repeat searches within 30 days and re-enrichment within 90 days are free", "Free `search_suggestions` resolves filter values before a paid search", "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 release or docs update since June 2026", "Privacy policy takes a perpetual licence to uploaded contact data, per the 30 September check" ], "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 79, "maintenance": 34, "payments": 40, "reliability": 35, "schema": 61, "security": 54, "transparency": 34 }, "provenanceScore": 49 }, "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-10-02", "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. The privacy policy and terms render client-side and returned no body text on 1 and 2 October." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/prospeo.json", "live": { "slug": "prospeo", "probe": { "target": "https://api.prospeo.io", "method": "get", "lastAt": "2026-10-14T10:28:15.054641024Z", "lastOk": true, "lastStatus": 429, "lastMs": 23, "lastNote": "rate limited", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 28, "p95ms24h": 46, "samples24h": 248, "samples30d": 3533, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "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": 108, "ok": 108 } ] }, "versions": [ { "registry": "mcp-registry", "name": "io.prospeo/prospeo-mcp-server", "version": "1.1.1", "seenAt": "2026-10-14T04:18:30.41681267Z" }, { "registry": "npm", "name": "@prospeo/prospeo-mcp-server", "version": "1.1.1", "seenAt": "2026-10-13T23:19:12.943002952Z" } ], "githubStars": 0, "npmWeekly": 411, "securityTxt": { "url": "https://prospeo.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:38.738953683Z" }, "domain": { "domain": "prospeo.io", "checkedAt": "2026-10-11T13:23:29.855819519Z" }, "pages": [ { "url": "https://prospeo.io/api-docs/email-finder", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-13T20:21:44.938481255Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "31857220e7cb" }, { "url": "https://prospeo.io/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-13T20:21:48.601851162Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7a2b15d0bd55" }, { "url": "https://prospeo.io/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:21:48.963750195Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "474d26a8c22c" }, { "url": "https://prospeo.io/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-10-13T20:21:50.954313664Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "65c942c41696" } ], "updatedAt": "2026-10-14T10:28:15.054641024Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Clay Labs Inc.", "b": "Prospeo", "name": "Vendor" }, { "a": "https://api.clay.com/public/v0", "b": "https://api.prospeo.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file", "b": "MIT", "name": "Licence" }, { "a": "none", "b": "8", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "io.prospeo/prospeo-mcp-server", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-06-01", "name": "Last release" }, { "a": "2024-05-23", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2020-09-11", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "0 stars, 641 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Clay scores 57.7 (C) on agent readiness against Prospeo API + MCP's 50.9 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Clay or Prospeo API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Clay and Prospeo API + MCP need an API key?" }, { "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Prospeo API + MCP at https://api.prospeo.io.", "question": "Can an agent call Clay and Prospeo API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 45 against 35", "Schema \u0026 documentation, 84 against 61", "Maintenance \u0026 community, 75 against 34", "Transparency \u0026 trust, 64 against 42" ], "also": null, "goodFor": "Agents building prospect lists and enriching contacts or accounts through many providers at once.", "slug": "clay", "watchFor": "API keys carry no scopes and act with the user's workspace access" }, { "aheadOn": [ "Agent ergonomics, 79 against 66", "Security \u0026 auth, 54 against 48", "Payments \u0026 pricing, 40 against 30" ], "also": [ "Runs on your own machine" ], "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" } ], "job": { "capability": "lead.search", "name": "Lead search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-clay.json", "title": "Apollo API + MCP vs Clay", "url": "https://www.anchorterminal.com/compare/apollo-vs-clay" }, { "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-coresignal.json", "title": "Clay vs Coresignal API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-coresignal" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-crustdata.json", "title": "Clay vs Crustdata API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-crustdata" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-enrich-layer.json", "title": "Clay vs Enrich Layer API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-enrich-layer" }, { "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/clay-vs-fullenrich.json", "title": "Clay vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.json", "title": "Clay vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-gojiberry.json", "title": "Clay vs Gojiberry", "url": "https://www.anchorterminal.com/compare/clay-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-hunter.json", "title": "Clay vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-leadmagic.json", "title": "Clay vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-lusha.json", "title": "Clay vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs.json", "title": "Clay vs People Data Labs", "url": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-rocketreach.json", "title": "Clay vs RocketReach API", "url": "https://www.anchorterminal.com/compare/clay-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-zoominfo.json", "title": "Clay vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-zoominfo" }, { "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/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/clay-vs-clearbit.json", "title": "Clay vs Clearbit", "url": "https://www.anchorterminal.com/compare/clay-vs-clearbit" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.json", "title": "Clay vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-dropcontact" }, { "json": "https://www.anchorterminal.com/compare/clay-vs-fullcontact.json", "title": "Clay vs FullContact", "url": "https://www.anchorterminal.com/compare/clay-vs-fullcontact" }, { "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/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/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/hunter-vs-prospeo.json", "title": "Hunter API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/hunter-vs-prospeo" } ], "scores": [ { "by": 10, "clay": 45, "edge": "clay", "key": "reliability", "name": "Reliability", "prospeo": 35, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 23, "clay": 84, "edge": "clay", "key": "schema", "name": "Schema \u0026 documentation", "prospeo": 61, "weight": 13 }, { "by": 13, "clay": 66, "edge": "prospeo", "key": "ergonomics", "name": "Agent ergonomics", "prospeo": 79, "weight": 13 }, { "by": 6, "clay": 48, "edge": "prospeo", "key": "security", "name": "Security \u0026 auth", "prospeo": 54, "weight": 14 }, { "by": 10, "clay": 30, "edge": "prospeo", "key": "payments", "name": "Payments \u0026 pricing", "prospeo": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 41, "clay": 75, "edge": "clay", "key": "maintenance", "name": "Maintenance \u0026 community", "prospeo": 34, "weight": 7 }, { "by": 22, "clay": 64, "edge": "clay", "key": "transparency", "name": "Transparency \u0026 trust", "prospeo": 42, "weight": 7 } ], "summary": "Clay scores 57.7 (C) on agent readiness against Prospeo API + MCP's 50.9 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do lead search.", "verdicts": { "clay": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.", "prospeo": "MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clay-vs-prospeo", "json": "https://www.anchorterminal.com/compare/clay-vs-prospeo.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clay-vs-prospeo.md", "slim": "https://www.anchorterminal.com/compare/clay-vs-prospeo.min.md" }, "markdown": "Clay scores 57.7 (C) on agent readiness against Prospeo API + MCP's 50.9 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing. Both do lead search.\n\n- Clay: grade C, 57.7/100, rank #633 of 1076. Markdown https://www.anchorterminal.com/tools/clay.md · JSON https://www.anchorterminal.com/api/v1/tools/clay.json\n- Prospeo API + MCP: grade D, 50.9/100, rank #814 of 1076. Markdown https://www.anchorterminal.com/tools/prospeo.md · JSON https://www.anchorterminal.com/api/v1/tools/prospeo.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 171 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Clay (C)\n\nGood for: Agents building prospect lists and enriching contacts or accounts through many providers at once.\n\nAhead on:\n- Reliability, 45 against 35\n- Schema \u0026 documentation, 84 against 61\n- Maintenance \u0026 community, 75 against 34\n- Transparency \u0026 trust, 64 against 42\n\nWatch for: API keys carry no scopes and act with the user's workspace access\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- Agent ergonomics, 79 against 66\n- Security \u0026 auth, 54 against 48\n- Payments \u0026 pricing, 40 against 30\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No status page, SLA or changelog\n\n\n## Score by category\n\n| Category | Weight | Clay | Prospeo API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 35 | Clay +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 61 | Clay +23 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 79 | Prospeo API + MCP +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 54 | Prospeo API + MCP +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Prospeo API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 34 | Clay +41 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 42 | Clay +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.7 · C** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | Clay | Prospeo API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | Prospeo |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.prospeo.io` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | MIT |\n| Tools exposed | none | 8 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | not listed | `io.prospeo/prospeo-mcp-server` |\n| Last release | 2026-10-06 | 2026-06-01 |\n| Terms last updated | 2024-05-23 | couldn't be read |\n| Privacy policy last updated | 2020-09-11 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | none | 0 stars, 641 npm/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\n\n**Clay.** A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.\n\n**Prospeo API + MCP.** MCP tool descriptions say when to use each tool, its credit cost and the next call. No status page, SLA or changelog.\n\n## Before you call either\n\n### Clay\n\n1. Fetch GET /search/query-mode/reference before writing a search query\n2. Poll routine results until a terminal 200, since 202 means still running\n3. Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date\n4. Check GET /credits/balance before large batch runs\n5. Ask the user before enabling the plugin's auto-approve hook in a shared workspace\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## Questions\n\n### Which is better for AI agents, Clay or Prospeo API + MCP?\n\nClay scores 57.7 (C) on agent readiness against Prospeo API + MCP's 50.9 (D), and leads in 4 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics, security \u0026 auth and payments \u0026 pricing.\n\n### Do Clay and Prospeo API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Clay and Prospeo API + MCP without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Prospeo API + MCP at https://api.prospeo.io.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-prospeo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-prospeo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"prospeo\"}`. From a terminal: `anchor compare clay prospeo`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/prospeo.json\n\n## Other comparisons with Clay or Prospeo API + MCP\n\n- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.md)\n- [Apollo API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/apollo-vs-prospeo.md)\n- [Clay vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clay-vs-coresignal.md)\n- [Clay vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clay-vs-crustdata.md)\n- [Clay vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/clay-vs-enrich-layer.md)\n- [Clay vs Explorium AgentSource](https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.md)\n- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)\n- [Clay vs Fuse MCP](https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.md)\n- [Clay vs Gojiberry](https://www.anchorterminal.com/compare/clay-vs-gojiberry.md)\n- [Clay vs Hunter API + MCP](https://www.anchorterminal.com/compare/clay-vs-hunter.md)\n- [Clay vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/clay-vs-leadmagic.md)\n- [Clay vs Lusha API + MCP](https://www.anchorterminal.com/compare/clay-vs-lusha.md)\n- [Clay vs People Data Labs](https://www.anchorterminal.com/compare/clay-vs-people-data-labs.md)\n- [Clay vs RocketReach API](https://www.anchorterminal.com/compare/clay-vs-rocketreach.md)\n- [Clay vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clay-vs-zoominfo.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- [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- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)\n- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)\n- [Clay vs FullContact](https://www.anchorterminal.com/compare/clay-vs-fullcontact.md)\n- [Clearbit vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-prospeo.md)\n- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)\n- [FullContact vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.md)\n- [Hunter API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-prospeo.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Clay vs Prospeo API + MCP", "url": "" } ], "description": "Clay scores 57.7 (C) to Prospeo's 50.9 (D) for lead search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clay C 57.7", "Prospeo API + MCP D 50.9", "scores" ], "h1": "Clay vs Prospeo API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-clay-vs-prospeo.png", "path": "/compare/clay-vs-prospeo", "published": "2026-10-01", "section": "tools", "title": "Clay vs Prospeo for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/clay-vs-prospeo" }, "tokens": { "markdown": 2550, "slim": 730 }, "version": 1 }