{ "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": "Clay scores 57.7 (C) on agent readiness against Dropcontact API + MCP's 50.9 (D), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability, security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "dropcontact", "name": "Dropcontact API + MCP", "vendor": "Dropcontact", "vendorUrl": "https://www.dropcontact.com", "kind": "http-api", "category": "lead-data", "summary": "Batch contact enrichment from a name and company.", "url": "https://www.anchorterminal.com/tools/dropcontact", "markdownUrl": "https://www.anchorterminal.com/tools/dropcontact.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dropcontact.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dropcontact.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.dropcontact.com/v1", "packages": [], "auth": "mixed", "authNotes": "`X-Access-Token` header on REST. Hosted MCP at mcp.dropcontact.com uses OAuth, or the API key as `Authorization: Bearer`.", "pricing": "paid", "pricingNotes": "Prices are in euros only. 50 free credits to try. Starter €79 a month for 500 credits, Growth €120 a month for 500 credits with carry-over, LinkedIn URL enrichment and company data, both scaling to 150,000 credits a month. Yearly billing is 20 per cent off. Enterprise from 200,000 credits a month. A credit is spent only when a verified email comes back (refunded if none is found), or 1 credit per email you send in for verification (https://www.dropcontact.com/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 mention in the API docs, MCP docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.dropcontact.com", "capabilities": [ "lead.enrichment", "email.finder", "email.verification", "data.company" ], "tags": [ "enrichment", "email-verification", "hosted", "no-card", "mcp", "webhooks", "async-jobs", "closed-source" ], "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 813, "ranked": true, "rankOf": 1076, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 18, "payments": 40, "reliability": 57, "schema": 41, "security": 59, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog.", "bestFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.", "strengths": [ "Pay on success, with credits refunded when no email is found", "50 free credits with no card", "Statuspage with its own API component", "Per-contact error and warning codes that say what to add", "security.txt with a HackerOne programme, and a published DPA" ], "weaknesses": [ "No OpenAPI spec, llms.txt or changelog", "No prospect search, so it only enriches people you already have", "Asynchronous only, with webhooks that can arrive out of order or twice", "One unscoped API key per account", "Remote MCP labelled early by the vendor and not in the official registry" ], "agentNotes": [ "Send a company name or website with every contact, or you get `only_contact_data`", "Send only documented fields. New accounts get a 400 for unknown ones", "Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen", "Poll no faster than every 30 seconds, as the not-ready response asks", "Post an empty contact to read the credit balance at no cost" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 60, "maintenance": 18, "payments": 40, "reliability": 57, "schema": 41, "security": 59, "transparency": 55 }, "provenanceScore": 87 }, "connect": { "http": "curl -X POST https://api.dropcontact.com/v1/enrich/all -H \"X-Access-Token: $DROPCONTACT_API_KEY\" \\\n -H \"Content-Type: application/json\" -d '{\"data\":[{\"first_name\":\"John\",\"last_name\":\"Smith\",\"website\":\"corporation.com\"}],\"language\":\"en\"}'", "claudeCode": "claude mcp add --transport http dropcontact https://mcp.dropcontact.com/mcp" }, "letme": { "capability": "https://letme.dev/lead.enrichment", "tool": "https://letme.dev/dropcontact" }, "area": "web-data", "provenance": { "legalEntity": "Dropcontact SAS", "domain": "dropcontact.com", "domainRegistered": "2016-03-21", "endpointOnVendorDomain": true, "terms": "https://www.dropcontact.com/terms", "privacy": "https://www.dropcontact.com/personal-data-charter", "statusPage": "https://status.dropcontact.com", "changelog": "", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "Terms name a simplified joint stock company (SAS) registered in Bobigny, no. 823 752 647" ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/dropcontact.json", "live": { "slug": "dropcontact", "probe": { "target": "https://api.dropcontact.com/v1", "method": "get", "lastAt": "2026-10-14T09:41:49.336179568Z", "lastOk": true, "lastStatus": 404, "lastMs": 51, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 59, "p95ms24h": 84, "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": 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": 100, "ok": 100 } ] }, "vendorStatus": { "page": "https://status.dropcontact.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:07.697934447Z" }, "securityTxt": { "url": "https://dropcontact.com/.well-known/security.txt", "state": "valid", "expires": "2027-04-09T00:00:00.000Z", "checkedAt": "2026-10-13T15:46:01.146708937Z" }, "domain": { "domain": "dropcontact.com", "registered": "2016-03-21", "source": "https://rdap.verisign.com/com/v1/domain/dropcontact.com", "checkedAt": "2026-10-11T13:11:20.697579642Z" }, "pages": [ { "url": "https://developer.dropcontact.com", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-13T20:12:41.217247759Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ff96d39467bb" }, { "url": "https://www.dropcontact.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-13T20:27:34.699457427Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "65a790ec5310" }, { "url": "https://www.dropcontact.com/personal-data-charter", "kind": "privacy", "status": 304, "checkedAt": "2026-10-13T20:27:32.64810909Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e25877e6f61c" }, { "url": "https://www.dropcontact.com/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-13T20:27:36.708640616Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bd33bd1bd813" } ], "updatedAt": "2026-10-14T09:41:49.336179568Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Clay Labs Inc.", "b": "Dropcontact", "name": "Vendor" }, { "a": "https://api.clay.com/public/v0", "b": "https://api.dropcontact.com/v1", "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": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-06", "b": "none", "name": "Last release" }, { "a": "2024-05-23", "b": "2025-08-01", "name": "Terms last updated" }, { "a": "2020-09-11", "b": "2020-06-04", "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": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Clay scores 57.7 (C) on agent readiness against Dropcontact API + MCP's 50.9 (D), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability, security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, Clay or Dropcontact API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Clay and Dropcontact API + MCP need an API key?" }, { "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Dropcontact API + MCP at https://api.dropcontact.com/v1.", "question": "Can an agent call Clay and Dropcontact API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 84 against 41", "Agent ergonomics, 66 against 60", "Maintenance \u0026 community, 75 against 18" ], "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, 57 against 45", "Security \u0026 auth, 59 against 48", "Payments \u0026 pricing, 40 against 30", "Transparency \u0026 trust, 71 against 64" ], "also": [ "Free to start without a card" ], "goodFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.", "slug": "dropcontact", "watchFor": "No OpenAPI spec, llms.txt or changelog" } ], "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "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/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-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/apollo-vs-dropcontact.json", "title": "Apollo API + MCP vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/apollo-vs-dropcontact" }, { "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-fullcontact.json", "title": "Clay vs FullContact", "url": "https://www.anchorterminal.com/compare/clay-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.json", "title": "Clearbit vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact" }, { "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/crustdata-vs-dropcontact.json", "title": "Crustdata API + MCP vs Dropcontact API + MCP", "url": "https://www.anchorterminal.com/compare/crustdata-vs-dropcontact" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.json", "title": "Dropcontact API + MCP vs Enrich Layer API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.json", "title": "Dropcontact API + MCP vs Explorium AgentSource", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.json", "title": "Dropcontact API + MCP vs FullContact", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.json", "title": "Dropcontact API + MCP vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.json", "title": "Dropcontact API + MCP vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.json", "title": "Dropcontact API + MCP vs Gojiberry", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter.json", "title": "Dropcontact API + MCP vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.json", "title": "Dropcontact API + MCP vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha.json", "title": "Dropcontact API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.json", "title": "Dropcontact API + MCP vs People Data Labs", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs" }, { "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-rocketreach.json", "title": "Dropcontact API + MCP vs RocketReach API", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.json", "title": "Dropcontact API + MCP vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo" } ], "scores": [ { "by": 12, "clay": 45, "dropcontact": 57, "edge": "dropcontact", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 43, "clay": 84, "dropcontact": 41, "edge": "clay", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 6, "clay": 66, "dropcontact": 60, "edge": "clay", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 11, "clay": 48, "dropcontact": 59, "edge": "dropcontact", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "clay": 30, "dropcontact": 40, "edge": "dropcontact", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 57, "clay": 75, "dropcontact": 18, "edge": "clay", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 7, "clay": 64, "dropcontact": 71, "edge": "dropcontact", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Clay scores 57.7 (C) on agent readiness against Dropcontact API + MCP's 50.9 (D), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability, security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do lead enrichment.", "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.", "dropcontact": "Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt or changelog." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clay-vs-dropcontact", "json": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.md", "slim": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.min.md" }, "markdown": "Clay scores 57.7 (C) on agent readiness against Dropcontact API + MCP's 50.9 (D), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability, security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do lead enrichment.\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- Dropcontact API + MCP: grade D, 50.9/100, rank #813 of 1076. Markdown https://www.anchorterminal.com/tools/dropcontact.md · JSON https://www.anchorterminal.com/api/v1/tools/dropcontact.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- Schema \u0026 documentation, 84 against 41\n- Agent ergonomics, 66 against 60\n- Maintenance \u0026 community, 75 against 18\n\nWatch for: API keys carry no scopes and act with the user's workspace access\n\n### Dropcontact API + MCP (D)\n\nGood for: European teams cleaning and completing contact lists where GDPR handling matters more than coverage.\n\nAhead on:\n- Reliability, 57 against 45\n- Security \u0026 auth, 59 against 48\n- Payments \u0026 pricing, 40 against 30\n- Transparency \u0026 trust, 71 against 64\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI spec, llms.txt or changelog\n\n\n## Score by category\n\n| Category | Weight | Clay | Dropcontact API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 57 | Dropcontact API + MCP +12 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 41 | Clay +43 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 60 | Clay +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 59 | Dropcontact API + MCP +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Dropcontact 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 | 18 | Clay +57 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 71 | Dropcontact API + MCP +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.7 · C** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | Clay | Dropcontact API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | Dropcontact |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.dropcontact.com/v1` |\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| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-06 | none |\n| Terms last updated | 2024-05-23 | 2025-08-01 |\n| Privacy policy last updated | 2020-09-11 | 2020-06-04 |\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| 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**Dropcontact API + MCP.** Pay on success, with credits refunded when no email is found. No OpenAPI spec, llms.txt 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### Dropcontact API + MCP\n\n1. Send a company name or website with every contact, or you get `only_contact_data`\n2. Send only documented fields. New accounts get a 400 for unknown ones\n3. Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen\n4. Poll no faster than every 30 seconds, as the not-ready response asks\n5. Post an empty contact to read the credit balance at no cost\n\n## Questions\n\n### Which is better for AI agents, Clay or Dropcontact API + MCP?\n\nClay scores 57.7 (C) on agent readiness against Dropcontact API + MCP's 50.9 (D), and leads in 3 of 7 scored categories. Dropcontact API + MCP leads on reliability, security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do Clay and Dropcontact 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 Dropcontact API + MCP without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Dropcontact API + MCP at https://api.dropcontact.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-dropcontact.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-dropcontact.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"dropcontact\"}`. From a terminal: `anchor compare clay dropcontact`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/dropcontact.json\n\n## Other comparisons with Clay or Dropcontact API + MCP\n\n- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.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 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- [Apollo API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/apollo-vs-dropcontact.md)\n- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)\n- [Clay vs FullContact](https://www.anchorterminal.com/compare/clay-vs-fullcontact.md)\n- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)\n- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)\n- [Crustdata API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.md)\n- [Dropcontact API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.md)\n- [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md)\n- [Dropcontact API + MCP vs FullContact](https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.md)\n- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)\n- [Dropcontact API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.md)\n- [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)\n- [Dropcontact API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-hunter.md)\n- [Dropcontact API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.md)\n- [Dropcontact API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-lusha.md)\n- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md)\n- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)\n- [Dropcontact API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.md)\n- [Dropcontact API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.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 Dropcontact API + MCP", "url": "" } ], "description": "Clay scores 57.7 (C) to Dropcontact's 50.9 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clay C 57.7", "Dropcontact API + MCP D 50.9", "scores" ], "h1": "Clay vs Dropcontact API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-clay-vs-dropcontact.png", "path": "/compare/clay-vs-dropcontact", "published": "2026-10-01", "section": "tools", "title": "Clay vs Dropcontact for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/clay-vs-dropcontact" }, "tokens": { "markdown": 2550, "slim": 630 }, "version": 1 }