{ "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-14T09:41:46.249843895Z", "lastOk": true, "lastStatus": 401, "lastMs": 152, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 149, "p95ms24h": 229, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.clay.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:52:50.29728454Z" }, "updatedAt": "2026-10-14T09:41:46.249843895Z" } }, "answer": "Coresignal API + MCP scores 62.9 (B) on agent readiness against Clay's 57.7 (C), and leads in 6 of 7 scored categories. Clay leads on payments \u0026 pricing.", "b": { "slug": "coresignal", "name": "Coresignal API + MCP", "vendor": "Coresignal", "vendorUrl": "https://coresignal.com", "kind": "http-api", "category": "lead-data", "summary": "Company, employee and job posting data collected from the public web, queried with filters or Elasticsearch DSL and pulled by ID, with a real-time employee lookup, profile-change webhooks and a natural-language Agentic Search API.", "url": "https://www.anchorterminal.com/tools/coresignal", "markdownUrl": "https://www.anchorterminal.com/tools/coresignal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/coresignal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/coresignal.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.coresignal.com/cdapi", "packages": [], "auth": "mixed", "authNotes": "`apikey` header on REST. Hosted MCP v2 at mcp.coresignal.com uses OAuth 2.1 through the Coresignal dashboard and looks up the team's key server-side, so no key sits in the client.", "pricing": "paid", "pricingNotes": "7-day free trial with 2,000 credits. Monthly plans Mini $49 (2,500 credits), Starter $199 (12,000), Pro $499 (35,000), Growth $1,000 (150,000), Premium $1,500 (1,000,000), Scale $3,000 (4,000,000), Elite $5,000 (10,000,000). Annual plans are 10 per cent off from Starter up. Search is free. Collecting a record costs 1 credit for jobs and posts, 10 for base or clean company and employee records, 20 for multi-source records, 12 for real-time employee. Agentic Search costs 20 (fast) or 100 (reasoning) (https://coresignal.com/pricing/).", "priceSummary": "$49 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 mention in the API docs, MCP docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": 5, "popularity": { "githubStars": 2, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.coresignal.com", "llmsTxt": "https://docs.coresignal.com/llms.txt", "openapi": "https://api.coresignal.com/cdapi/openapi.json", "registryName": "com.coresignal/mcp", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.company", "data.person" ], "tags": [ "lead-search", "enrichment", "hosted", "card-required", "mcp", "llms-txt", "openapi", "webhooks", "async-jobs", "closed-source" ], "lastRelease": "2026-08-07", "graded": true, "anchor": { "graded": true, "score": 62.9, "grade": "B", "agentReady": false, "rank": 439, "ranked": true, "rankOf": 1076, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 82, "payments": 20, "reliability": 55, "schema": 86, "security": 58, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page.", "bestFor": "Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.", "strengths": [ "Search is free, and credits are only taken on collect or enrich calls that return 200", "Every plan price and per-endpoint credit cost is public", "Hosted MCP with 5 tools, OAuth 2.1 and a confirmation step before large pulls", "Monthly release notes with dated entries and flagged breaking changes", "Privacy policy covers people in the datasets, with a five-year retention cap" ], "weaknesses": [ "Real-Time API requests timing out for about six days up to 1 October, per the status page", "Main search takes Elasticsearch DSL, a free-form JSON body", "7-day trial with a card per the 30 September check, and no free tier", "Terms name Deeptrace Inc. while the privacy policy names Binary House LLC", "Breaking changes in August 2026 to Agentic Search and Multi-source Jobs, announced in release notes with no stated notice period" ], "agentNotes": [ "Search for IDs first (free), then collect only the records you need", "Use base records at 10 credits when you don't need the 20-credit multi-source fields", "Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated", "Treat a 402 as out of credits, not a transient error", "Expect no work emails for EEA and UK people from the MCP email tool" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.9 } ], "editorialScores": { "ergonomics": 73, "maintenance": 82, "payments": 20, "reliability": 55, "schema": 86, "security": 58, "transparency": 55 }, "provenanceScore": 87 }, "connect": { "http": "curl \"https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?enrich_query=stripe.com\" -H \"apikey: $CORESIGNAL_API_KEY\"", "claudeCode": "claude mcp add --transport http coresignal https://mcp.coresignal.com/mcp/v2" }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/coresignal" }, "area": "web-data", "unitPrices": [ { "item": "Mini plan", "unit": "month", "usd": 49, "note": "2,500 credits" }, { "item": "Starter plan", "unit": "month", "usd": 199, "note": "12,000 credits" }, { "item": "Pro plan", "unit": "month", "usd": 499, "note": "35,000 credits, adds contact enrichment" }, { "item": "Growth plan", "unit": "month", "usd": 1000, "note": "150,000 credits" }, { "item": "Multi-source company or employee record", "unit": "record", "usd": 0.285, "note": "20 credits at Pro plan rates ($499 for 35,000 credits)" } ], "provenance": { "legalEntity": "Deeptrace Inc.", "domain": "coresignal.com", "domainRegistered": "2014-12-16", "endpointOnVendorDomain": true, "terms": "https://coresignal.com/terms-and-conditions/", "privacy": "https://coresignal.com/privacy-policy/", "statusPage": "https://status.coresignal.com", "changelog": "https://docs.coresignal.com/release-notes", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The terms and conditions name Deeptrace Inc. (Lewes, Delaware) as the contracting company for Coresignal", "The privacy policy, updated 25 August 2026, names Binary House LLC as the data controller and lists Deeptrace Inc. as a processor" ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/coresignal.json", "live": { "slug": "coresignal", "probe": { "target": "https://api.coresignal.com/cdapi", "method": "get", "lastAt": "2026-10-14T09:41:47.335933501Z", "lastOk": true, "lastStatus": 404, "lastMs": 79, "authRequired": false, "uptime24h": 100, "uptime30d": 99.43, "p50ms24h": 73, "p95ms24h": 164, "samples24h": 248, "samples30d": 3525, "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": 252 }, { "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": 100, "ok": 100 } ], "outages": [ { "start": "2026-10-05T05:02:39.72752943Z", "end": "2026-10-05T06:45:00.818712073Z", "note": "HTTP 503 server error" } ] }, "vendorStatus": { "page": "https://status.coresignal.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:00.144677379Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.coresignal/mcp", "version": "2.0.0", "seenAt": "2026-10-14T04:18:30.41681267Z" } ], "securityTxt": { "url": "https://coresignal.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:46:00.661972625Z" }, "llmsTxt": { "url": "https://docs.coresignal.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:18.857318849Z" }, "domain": { "domain": "coresignal.com", "registered": "2014-12-16", "source": "https://rdap.verisign.com/com/v1/domain/coresignal.com", "checkedAt": "2026-10-11T13:14:49.851889147Z" }, "pages": [ { "url": "https://docs.coresignal.com/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-13T20:14:31.51510425Z", "changedAt": "2026-10-08T18:18:31.957477618Z", "fingerprint": "cd2325892a8d" }, { "url": "https://coresignal.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-13T20:11:58.286462854Z", "changedAt": "2026-10-09T18:34:22.355790651Z", "fingerprint": "ecc8378af48a" }, { "url": "https://coresignal.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:12:00.369114149Z", "changedAt": "2026-10-02T15:18:35.054977183Z", "fingerprint": "777e30111f81" }, { "url": "https://coresignal.com/terms-and-conditions/", "kind": "terms", "status": 304, "checkedAt": "2026-10-13T20:12:02.381515279Z", "changedAt": "2026-10-02T15:18:37.038598322Z", "fingerprint": "582fd42b69c8" } ], "updatedAt": "2026-10-14T09:41:47.335933501Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Clay Labs Inc.", "b": "Coresignal", "name": "Vendor" }, { "a": "https://api.clay.com/public/v0", "b": "https://api.coresignal.com/cdapi", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "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": "none", "name": "Licence" }, { "a": "none", "b": "5", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.coresignal/mcp", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-08-07", "name": "Last release" }, { "a": "2024-05-23", "b": "2022-02-21", "name": "Terms last updated" }, { "a": "2020-09-11", "b": "2026-08-25", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2 stars", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Coresignal API + MCP scores 62.9 (B) on agent readiness against Clay's 57.7 (C), and leads in 6 of 7 scored categories. Clay leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Clay or Coresignal API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Clay and Coresignal API + MCP need an API key?" }, { "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Coresignal API + MCP at https://api.coresignal.com/cdapi.", "question": "Can an agent call Clay and Coresignal API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 20" ], "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": [ "Reliability, 55 against 45", "Agent ergonomics, 73 against 66", "Security \u0026 auth, 58 against 48", "Maintenance \u0026 community, 82 against 75", "Transparency \u0026 trust, 71 against 64" ], "also": null, "goodFor": "Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.", "slug": "coresignal", "watchFor": "Real-Time API requests timing out for about six days up to 1 October, per the status page" } ], "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-coresignal.json", "title": "Apollo API + MCP vs Coresignal API + MCP", "url": "https://www.anchorterminal.com/compare/apollo-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-prospeo.json", "title": "Clay vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/clay-vs-prospeo" }, { "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-crustdata.json", "title": "Coresignal API + MCP vs Crustdata API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-crustdata" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.json", "title": "Coresignal API + MCP vs Enrich Layer API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.json", "title": "Coresignal API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.json", "title": "Coresignal API + MCP vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.json", "title": "Coresignal API + MCP vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.json", "title": "Coresignal API + MCP vs Gojiberry", "url": "https://www.anchorterminal.com/compare/coresignal-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-hunter.json", "title": "Coresignal API + MCP vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-leadmagic.json", "title": "Coresignal API + MCP vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-lusha.json", "title": "Coresignal API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.json", "title": "Coresignal API + MCP vs People Data Labs", "url": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs" }, { "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/coresignal-vs-rocketreach.json", "title": "Coresignal API + MCP vs RocketReach API", "url": "https://www.anchorterminal.com/compare/coresignal-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.json", "title": "Coresignal API + MCP vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-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-coresignal.json", "title": "Clearbit vs Coresignal API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.json", "title": "Coresignal API + MCP vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/coresignal-vs-dropcontact" }, { "json": "https://www.anchorterminal.com/compare/coresignal-vs-fullcontact.json", "title": "Coresignal API + MCP vs FullContact", "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullcontact" } ], "scores": [ { "by": 10, "clay": 45, "coresignal": 55, "edge": "coresignal", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "clay": 84, "coresignal": 86, "edge": "coresignal", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "clay": 66, "coresignal": 73, "edge": "coresignal", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 10, "clay": 48, "coresignal": 58, "edge": "coresignal", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "clay": 30, "coresignal": 20, "edge": "clay", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "clay": 75, "coresignal": 82, "edge": "coresignal", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 7, "clay": 64, "coresignal": 71, "edge": "coresignal", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Coresignal API + MCP scores 62.9 (B) on agent readiness against Clay's 57.7 (C), and leads in 6 of 7 scored categories. Clay leads on 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.", "coresignal": "Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clay-vs-coresignal", "json": "https://www.anchorterminal.com/compare/clay-vs-coresignal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clay-vs-coresignal.md", "slim": "https://www.anchorterminal.com/compare/clay-vs-coresignal.min.md" }, "markdown": "Coresignal API + MCP scores 62.9 (B) on agent readiness against Clay's 57.7 (C), and leads in 6 of 7 scored categories. Clay leads on 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- Coresignal API + MCP: grade B, 62.9/100, rank #439 of 1076. Markdown https://www.anchorterminal.com/tools/coresignal.md · JSON https://www.anchorterminal.com/api/v1/tools/coresignal.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- Payments \u0026 pricing, 30 against 20\n\nWatch for: API keys carry no scopes and act with the user's workspace access\n\n### Coresignal API + MCP (B)\n\nGood for: Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.\n\nAhead on:\n- Reliability, 55 against 45\n- Agent ergonomics, 73 against 66\n- Security \u0026 auth, 58 against 48\n- Maintenance \u0026 community, 82 against 75\n- Transparency \u0026 trust, 71 against 64\n\nWatch for: Real-Time API requests timing out for about six days up to 1 October, per the status page\n\n\n## Score by category\n\n| Category | Weight | Clay | Coresignal API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 55 | Coresignal API + MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 86 | Coresignal API + MCP +2 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 73 | Coresignal API + MCP +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 58 | Coresignal API + MCP +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Clay +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 82 | Coresignal API + MCP +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 71 | Coresignal API + MCP +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.7 · C** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Clay | Coresignal API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | Coresignal |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.coresignal.com/cdapi` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | none |\n| Tools exposed | none | 5 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.coresignal/mcp` |\n| Last release | 2026-10-06 | 2026-08-07 |\n| Terms last updated | 2024-05-23 | 2022-02-21 |\n| Privacy policy last updated | 2020-09-11 | 2026-08-25 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 2 stars |\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**Coresignal API + MCP.** Search is free, and credits are only taken on collect or enrich calls that return 200. Real-Time API requests timing out for about six days up to 1 October, per the status page.\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### Coresignal API + MCP\n\n1. Search for IDs first (free), then collect only the records you need\n2. Use base records at 10 credits when you don't need the 20-credit multi-source fields\n3. Use MCP v2 at /mcp/v2. The older /mcp endpoint will be deprecated\n4. Treat a 402 as out of credits, not a transient error\n5. Expect no work emails for EEA and UK people from the MCP email tool\n\n## Questions\n\n### Which is better for AI agents, Clay or Coresignal API + MCP?\n\nCoresignal API + MCP scores 62.9 (B) on agent readiness against Clay's 57.7 (C), and leads in 6 of 7 scored categories. Clay leads on payments \u0026 pricing.\n\n### Do Clay and Coresignal 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 Coresignal API + MCP without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Coresignal API + MCP at https://api.coresignal.com/cdapi.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-coresignal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-coresignal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"coresignal\"}`. From a terminal: `anchor compare clay coresignal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/coresignal.json\n\n## Other comparisons with Clay or Coresignal API + MCP\n\n- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.md)\n- [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-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 Prospeo API + MCP](https://www.anchorterminal.com/compare/clay-vs-prospeo.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 Crustdata API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-crustdata.md)\n- [Coresignal API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.md)\n- [Coresignal API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.md)\n- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)\n- [Coresignal API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.md)\n- [Coresignal API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.md)\n- [Coresignal API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-hunter.md)\n- [Coresignal API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-leadmagic.md)\n- [Coresignal API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-lusha.md)\n- [Coresignal API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.md)\n- [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md)\n- [Coresignal API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/coresignal-vs-rocketreach.md)\n- [Coresignal API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/coresignal-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 Coresignal API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-coresignal.md)\n- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)\n- [Coresignal API + MCP vs FullContact](https://www.anchorterminal.com/compare/coresignal-vs-fullcontact.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 Coresignal API + MCP", "url": "" } ], "description": "Coresignal scores 62.9 (B) to Clay's 57.7 (C) for lead search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clay C 57.7", "Coresignal API + MCP B 62.9", "scores" ], "h1": "Clay vs Coresignal API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-clay-vs-coresignal.png", "path": "/compare/clay-vs-coresignal", "published": "2026-10-01", "section": "tools", "title": "Clay vs Coresignal for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/clay-vs-coresignal" }, "tokens": { "markdown": 2550, "slim": 630 }, "version": 1 }