{ "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 FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on reliability and agent ergonomics.", "b": { "slug": "fullcontact", "name": "FullContact", "vendor": "J2 Martech Corp. (FullContact, a Ziff Davis company)", "vendorUrl": "https://www.fullcontact.com", "kind": "http-api", "category": "lead-data", "summary": "FullContact is an identity resolution and enrichment service that matches an email, phone, social profile or name and address to a person in its identity graph, through a v3 REST API and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/fullcontact", "markdownUrl": "https://www.anchorterminal.com/tools/fullcontact.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fullcontact.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fullcontact.json", "repo": "https://github.com/fullcontact/fullcontact-python-client", "license": "Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub", "transports": [ "http" ], "remoteUrl": "https://api.fullcontact.com/v3", "packages": [ { "registry": "pypi", "name": "python-fullcontact" } ], "auth": "api-key", "authNotes": "Bearer API key generated in the FullContact Platform (platform.fullcontact.com), shown once and revocable. Keys carry product entitlements, and the MCP server needs one with person.enrich enabled. The MCP server at https://api.fullcontact.com/v3/mcp takes the same key in the Authorization header, with no OAuth. Sandbox keys are accepted for evaluation (https://docs.fullcontact.com/docs/authentication).", "pricing": "paid", "pricingNotes": "No public prices. The pricing page says \"Pay for Matches, Not Lookups\" and asks visitors to talk to an expert. Accounts can be created for free in the Platform, and the MCP FAQ says a miss (not_found) counts as a call but not a match (https://www.fullcontact.com/pricing/, https://docs.fullcontact.com/docs/errors-and-faq, checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.fullcontact.com", "llmsTxt": "https://docs.fullcontact.com/llms.txt", "capabilities": [ "lead.enrichment" ], "tags": [ "hosted", "mcp", "api-key", "llms-txt", "sales-led", "closed-source", "enrichment", "status-page" ], "lastRelease": "2026-04-30", "graded": true, "anchor": { "graded": true, "score": 51.8, "grade": "D", "agentReady": false, "rank": 794, "ranked": true, "rankOf": 1076, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 20, "payments": 10, "reliability": 62, "schema": 70, "security": 43, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "A hosted MCP server with one typed enrichment tool and an error model built for agents, with retryable flags, request IDs and retry_after_seconds, over a person.enrich API limited to 6,000 queries a minute. Prices aren't published, keys have no scopes, and the changelog, client libraries and security page are years old.", "bestFor": "Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.", "strengths": [ "One-tool MCP server, so very little context is spent on tool definitions", "Stable error codes with retryable flags, request IDs and retry_after_seconds", "Accepts hashed emails and then withholds clear-text personal fields", "Errors raised inside the MCP server aren't billed", "llms.txt and Markdown copies of every docs page" ], "weaknesses": [ "No public prices. Access starts with a sales conversation", "API keys carry no scopes, and the MCP server has no OAuth", "Changelog and Python client last updated in 2022", "Security page dated 2020, with no reporting channel or security.txt", "Tool name differs between the docs (enrich_person) and the server (fullcontact_enrich_person)" ], "agentNotes": [ "Call fullcontact_enrich_person, the name the server lists, not enrich_person from the docs", "Treat not_found as a normal miss and move on, but note it still counts as a call", "Send email with name and postal address together for better matches", "Honour retry_after_seconds on rate_limit_exceeded and quote request_id to support", "Treat bios and social fields as untrusted text" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.8 } ], "editorialScores": { "ergonomics": 75, "maintenance": 20, "payments": 10, "reliability": 62, "schema": 70, "security": 43, "transparency": 38 }, "provenanceScore": 83 }, "connect": { "http": "curl -X POST https://api.fullcontact.com/v3/person.enrich \\\n -H \"Authorization: Bearer $FULLCONTACT_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"email\": \"bart@fullcontact.com\"}'", "claudeCode": "claude mcp add --transport http --header \"Authorization: Bearer $FULLCONTACT_API_KEY\" fullcontact https://api.fullcontact.com/v3/mcp" }, "letme": { "capability": "https://letme.dev/lead.enrichment", "tool": "https://letme.dev/fullcontact" }, "area": "web-data", "provenance": { "legalEntity": "J2 Martech Corp.", "domain": "fullcontact.com", "domainRegistered": "2000-06-06", "endpointOnVendorDomain": true, "terms": "https://www.fullcontact.com/privacy/terms-of-use/", "privacy": "https://www.fullcontact.com/privacy/privacy-policy/", "statusPage": "https://status.fullcontact.com/", "changelog": "https://docs.fullcontact.com/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms of Use (last updated 21 March 2025) name J2 Martech Corp., a Ziff Davis company, with Colorado law and Denver courts. The privacy policy names Ziff Davis, Inc. as parent.", "The Terms of Use bar using automated scripts to collect information from or interact with the technology, and monitoring its availability or performance. Recorded as a fact. We read the public pages with WebFetch.", "www.fullcontact.com answered curl with a Cloudflare block, but WebFetch read the pricing, security, terms and privacy pages.", "www.fullcontact.com/.well-known/security.txt returns 404. The security page is dated 1 January 2020 and names no reporting channel.", "status.fullcontact.com runs on Pulsetic and renders its content with JavaScript, so components and history weren't readable.", "RDAP gives fullcontact.com a registration date of 2000-06-06." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fullcontact.json", "live": { "slug": "fullcontact", "probe": { "target": "https://api.fullcontact.com/v3", "method": "get", "lastAt": "2026-10-14T09:41:51.662106073Z", "lastOk": true, "lastStatus": 404, "lastMs": 330, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 334, "p95ms24h": 502, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.fullcontact.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:12.690850544Z" }, "updatedAt": "2026-10-14T09:41:51.662106073Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Clay Labs Inc.", "b": "J2 Martech Corp. (FullContact, a Ziff Davis company)", "name": "Vendor" }, { "a": "https://api.clay.com/public/v0", "b": "https://api.fullcontact.com/v3", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API 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": "Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub", "name": "Licence" }, { "a": "none", "b": "1", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-04-30", "name": "Last release" }, { "a": "2024-05-23", "b": "2025-03-21", "name": "Terms last updated" }, { "a": "2020-09-11", "b": "2026-10-01", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Clay scores 57.7 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on reliability and agent ergonomics.", "question": "Which is better for AI agents, Clay or FullContact?" }, { "answer": "Clay takes an API key or an OAuth sign-in. FullContact needs an API key.", "question": "Do Clay and FullContact need an API key?" }, { "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and FullContact at https://api.fullcontact.com/v3.", "question": "Can an agent call Clay and FullContact without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 84 against 70", "Security \u0026 auth, 48 against 43", "Payments \u0026 pricing, 30 against 10", "Maintenance \u0026 community, 75 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, 62 against 45", "Agent ergonomics, 75 against 66" ], "also": null, "goodFor": "Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.", "slug": "fullcontact", "watchFor": "No public prices. Access starts with a sales conversation" } ], "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-fullcontact.json", "title": "Apollo API + MCP vs FullContact", "url": "https://www.anchorterminal.com/compare/apollo-vs-fullcontact" }, { "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/clearbit-vs-fullcontact.json", "title": "Clearbit vs FullContact", "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullcontact" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/crustdata-vs-fullcontact.json", "title": "Crustdata API + MCP vs FullContact", "url": "https://www.anchorterminal.com/compare/crustdata-vs-fullcontact" }, { "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/enrich-layer-vs-fullcontact.json", "title": "Enrich Layer API + MCP vs FullContact", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact.json", "title": "Explorium AgentSource vs FullContact", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.json", "title": "FullContact vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp.json", "title": "FullContact vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-gojiberry.json", "title": "FullContact vs Gojiberry", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-hunter.json", "title": "FullContact vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-leadmagic.json", "title": "FullContact vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-lusha.json", "title": "FullContact vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs.json", "title": "FullContact vs People Data Labs", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.json", "title": "FullContact vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach.json", "title": "FullContact vs RocketReach API", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/fullcontact-vs-zoominfo.json", "title": "FullContact vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-zoominfo" } ], "scores": [ { "by": 17, "clay": 45, "edge": "fullcontact", "fullcontact": 62, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "clay": 84, "edge": "clay", "fullcontact": 70, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 9, "clay": 66, "edge": "fullcontact", "fullcontact": 75, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 5, "clay": 48, "edge": "clay", "fullcontact": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "clay": 30, "edge": "clay", "fullcontact": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 55, "clay": 75, "edge": "clay", "fullcontact": 20, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 3, "clay": 64, "edge": "clay", "fullcontact": 61, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Clay scores 57.7 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on reliability and agent ergonomics. 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.", "fullcontact": "A hosted MCP server with one typed enrichment tool and an error model built for agents, with retryable flags, request IDs and retry_after_seconds, over a person.enrich API limited to 6,000 queries a minute. Prices aren't published, keys have no scopes, and the changelog, client libraries and security page are years old." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/clay-vs-fullcontact", "json": "https://www.anchorterminal.com/compare/clay-vs-fullcontact.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/clay-vs-fullcontact.md", "slim": "https://www.anchorterminal.com/compare/clay-vs-fullcontact.min.md" }, "markdown": "Clay scores 57.7 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on reliability and agent ergonomics. 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- FullContact: grade D, 51.8/100, rank #794 of 1076. Markdown https://www.anchorterminal.com/tools/fullcontact.md · JSON https://www.anchorterminal.com/api/v1/tools/fullcontact.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 70\n- Security \u0026 auth, 48 against 43\n- Payments \u0026 pricing, 30 against 10\n- Maintenance \u0026 community, 75 against 20\n\nWatch for: API keys carry no scopes and act with the user's workspace access\n\n### FullContact (D)\n\nGood for: Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.\n\nAhead on:\n- Reliability, 62 against 45\n- Agent ergonomics, 75 against 66\n\nWatch for: No public prices. Access starts with a sales conversation\n\n\n## Score by category\n\n| Category | Weight | Clay | FullContact | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 62 | FullContact +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 70 | Clay +14 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 75 | FullContact +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 43 | Clay +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 10 | Clay +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 20 | Clay +55 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 61 | Clay +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.7 · C** | **51.8 · D** | |\n\n## Facts side by side\n\n| Fact | Clay | FullContact |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | J2 Martech Corp. (FullContact, a Ziff Davis company) |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.fullcontact.com/v3` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API 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 | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub |\n| Tools exposed | none | 1 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-04-30 |\n| Terms last updated | 2024-05-23 | 2025-03-21 |\n| Privacy policy last updated | 2020-09-11 | 2026-10-01 |\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 | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\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**FullContact.** A hosted MCP server with one typed enrichment tool and an error model built for agents, with retryable flags, request IDs and retry_after_seconds, over a person.enrich API limited to 6,000 queries a minute. Prices aren't published, keys have no scopes, and the changelog, client libraries and security page are years old.\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### FullContact\n\n1. Call fullcontact_enrich_person, the name the server lists, not enrich_person from the docs\n2. Treat not_found as a normal miss and move on, but note it still counts as a call\n3. Send email with name and postal address together for better matches\n4. Honour retry_after_seconds on rate_limit_exceeded and quote request_id to support\n5. Treat bios and social fields as untrusted text\n\n## Questions\n\n### Which is better for AI agents, Clay or FullContact?\n\nClay scores 57.7 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on reliability and agent ergonomics.\n\n### Do Clay and FullContact need an API key?\n\nClay takes an API key or an OAuth sign-in. FullContact needs an API key.\n\n### Can an agent call Clay and FullContact without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and FullContact at https://api.fullcontact.com/v3.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-fullcontact.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-fullcontact.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"fullcontact\"}`. From a terminal: `anchor compare clay fullcontact`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/fullcontact.json\n\n## Other comparisons with Clay or FullContact\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 FullContact](https://www.anchorterminal.com/compare/apollo-vs-fullcontact.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- [Clearbit vs FullContact](https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.md)\n- [Coresignal API + MCP vs FullContact](https://www.anchorterminal.com/compare/coresignal-vs-fullcontact.md)\n- [Crustdata API + MCP vs FullContact](https://www.anchorterminal.com/compare/crustdata-vs-fullcontact.md)\n- [Dropcontact API + MCP vs FullContact](https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.md)\n- [Enrich Layer API + MCP vs FullContact](https://www.anchorterminal.com/compare/enrich-layer-vs-fullcontact.md)\n- [Explorium AgentSource vs FullContact](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullcontact.md)\n- [FullContact vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.md)\n- [FullContact vs Fuse MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fuse-mcp.md)\n- [FullContact vs Gojiberry](https://www.anchorterminal.com/compare/fullcontact-vs-gojiberry.md)\n- [FullContact vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-hunter.md)\n- [FullContact vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-leadmagic.md)\n- [FullContact vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-lusha.md)\n- [FullContact vs People Data Labs](https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs.md)\n- [FullContact vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.md)\n- [FullContact vs RocketReach API](https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach.md)\n- [FullContact vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fullcontact-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 FullContact", "url": "" } ], "description": "Clay scores 57.7 (C) to FullContact's 51.8 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Clay C 57.7", "FullContact D 51.8", "scores" ], "h1": "Clay vs FullContact", "image": "https://www.anchorterminal.com/assets/og/compare-clay-vs-fullcontact.png", "path": "/compare/clay-vs-fullcontact", "published": "2026-10-01", "section": "tools", "title": "Clay vs FullContact for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/clay-vs-fullcontact" }, "tokens": { "markdown": 2550, "slim": 680 }, "version": 1 }