{ "data": { "a": { "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" } }, "answer": "FullEnrich API + MCP scores 59.6 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on agent ergonomics.", "b": { "slug": "fullenrich", "name": "FullEnrich API + MCP", "vendor": "FullEnrich", "vendorUrl": "https://fullenrich.com", "kind": "http-api", "category": "lead-data", "summary": "Waterfall contact enrichment that queries 20+ data providers for work emails, personal emails and mobile numbers, plus people and company search and reverse email lookup.", "url": "https://www.anchorterminal.com/tools/fullenrich", "markdownUrl": "https://www.anchorterminal.com/tools/fullenrich.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fullenrich.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fullenrich.json", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://app.fullenrich.com/api/v2", "packages": [], "auth": "mixed", "authNotes": "Bearer API key in the Authorization header for REST. The hosted MCP server at https://mcp.fullenrich.com/mcp signs in with your FullEnrich account over OAuth. Webhooks carry an X-Signature-SHA1 header, an HMAC-SHA1 of the raw body keyed with your API key.", "pricing": "freemium", "pricingNotes": "Free trial with 50 credits and no card. Pro from $55 a month for 1,000 credits (about $0.055 a credit), scaling to $720 a month for 15,000 credits, with cheaper annual billing and Enterprise on quote. Credits are spent only on found data. A work email costs 1 credit, a personal email 3, a mobile number 10, a reverse email match 1, and each search result 0.25 (free to export again). Unused credits roll over for 3 months on monthly plans and 12 on annual (https://fullenrich.com/pricing).", "priceSummary": "$55 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 13, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.fullenrich.com", "llmsTxt": "https://docs.fullenrich.com/llms.txt", "openapi": "https://docs.fullenrich.com/api/v2/reference/openapi.yaml", "registryName": "io.github.FullEnrich/fullenrich", "capabilities": [ "lead.search", "lead.enrichment", "email.finder", "data.person", "data.company" ], "tags": [ "hosted", "freemium", "no-card", "mcp", "llms-txt", "openapi", "webhooks", "async-jobs", "closed-source", "lead-search", "enrichment" ], "lastRelease": "2026-08-27", "graded": true, "anchor": { "graded": true, "score": 59.6, "grade": "C", "agentReady": false, "rank": 572, "ranked": true, "rankOf": 1076, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 68, "payments": 40, "reliability": 60, "schema": 72, "security": 55, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.", "bestFor": "Maximising find rate on known contacts, especially mobiles, without a long-term contract.", "strengths": [ "Credits only spent on found data, and identical re-runs within 3 months are free", "50 trial credits with no card, API and MCP included", "Hosted MCP with OAuth and 13 tools, listed in the official registry under io.github.FullEnrich", "OpenAPI file and llms.txt", "SOC 2 Type 2 per the trust page" ], "weaknesses": [ "Enrichment sources are third-party providers the vendor doesn't name", "Status page covers the web app only, not the API or MCP", "No 429 or error reference found in the docs", "Public product changelog stops at November 2024", "Webhooks signed with HMAC-SHA1 keyed with the API key itself" ], "agentNotes": [ "Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again", "Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results`", "Ask for mobiles only when needed. They cost 10 credits against 1 for a work email", "Call `list_industries` and `list_seniorities` before filtering search", "Use the 0-credit test contacts in the docs to check an integration" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.6 } ], "editorialScores": { "ergonomics": 60, "maintenance": 68, "payments": 40, "reliability": 60, "schema": 72, "security": 55, "transparency": 50 }, "provenanceScore": 77 }, "connect": { "http": "curl https://app.fullenrich.com/api/v2/account/credits -H \"Authorization: Bearer $FULLENRICH_API_KEY\"", "claudeCode": "claude mcp add --transport http fullenrich https://mcp.fullenrich.com/mcp", "config": { "mcpServers": { "fullenrich": { "url": "https://mcp.fullenrich.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/fullenrich" }, "area": "web-data", "unitPrices": [ { "item": "Pro, 1,000 credits", "unit": "month", "usd": 55 }, { "item": "Pro, 15,000 credits", "unit": "month", "usd": 720 }, { "item": "Credit on Pro 1,000", "unit": "credit", "usd": 0.055, "note": "one found work email; a mobile is 10 credits, a personal email 3, a search result 0.25" } ], "provenance": { "legalEntity": "FullEnrich Corp", "domain": "fullenrich.com", "domainRegistered": "2023-04-08", "endpointOnVendorDomain": true, "terms": "https://fullenrich.com/tos", "privacy": "https://fullenrich.com/privacy-policy", "statusPage": "https://status.fullenrich.com", "changelog": "https://fullenrich.com/changelog", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The public changelog's newest entry is 30 November 2024. The MCP package keeps its own CHANGELOG in github.com/FullEnrich/fullenrich-skills, latest 1.0.4 on 2026-08-27", "The status page has one component, app.fullenrich.com/app, and none for the API" ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fullenrich.json", "live": { "slug": "fullenrich", "probe": { "target": "https://app.fullenrich.com/api/v2", "method": "get", "lastAt": "2026-10-14T09:41:51.664266851Z", "lastOk": true, "lastStatus": 404, "lastMs": 95, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 70, "p95ms24h": 146, "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.fullenrich.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:13.023130784Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.FullEnrich/fullenrich", "version": "1.0.4", "seenAt": "2026-10-14T04:18:30.41681267Z" } ], "securityTxt": { "url": "https://fullenrich.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:55.487214123Z" }, "llmsTxt": { "url": "https://docs.fullenrich.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:36.239774143Z" }, "domain": { "domain": "fullenrich.com", "registered": "2023-04-08", "source": "https://rdap.verisign.com/com/v1/domain/fullenrich.com", "checkedAt": "2026-10-11T13:18:39.437402442Z" }, "pages": [ { "url": "https://fullenrich.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-13T20:17:10.289338459Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3743ba5a6ed1" }, { "url": "https://fullenrich.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-13T20:17:12.904841982Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8d24d5b37df7" }, { "url": "https://fullenrich.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-13T20:17:14.545272307Z", "changedAt": "2026-10-08T18:20:35.863765695Z", "fingerprint": "e5ec8a32f619" }, { "url": "https://fullenrich.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-13T20:17:16.50284783Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "09e6f975476f" } ], "updatedAt": "2026-10-14T09:41:51.664266851Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "J2 Martech Corp. (FullContact, a Ziff Davis company)", "b": "FullEnrich", "name": "Vendor" }, { "a": "https://api.fullcontact.com/v3", "b": "https://app.fullenrich.com/api/v2", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub", "b": "none", "name": "Licence" }, { "a": "1", "b": "13", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.FullEnrich/fullenrich", "name": "MCP registry" }, { "a": "2026-04-30", "b": "2026-08-27", "name": "Last release" }, { "a": "2025-03-21", "b": "2026-08-20", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "2026-08-20", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "FullEnrich API + MCP scores 59.6 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on agent ergonomics.", "question": "Which is better for AI agents, FullContact or FullEnrich API + MCP?" }, { "answer": "FullContact needs an API key. FullEnrich API + MCP takes an API key or an OAuth sign-in.", "question": "Do FullContact and FullEnrich API + MCP need an API key?" }, { "answer": "Yes. FullContact has a hosted endpoint at https://api.fullcontact.com/v3 and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.", "question": "Can an agent call FullContact and FullEnrich API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 75 against 60" ], "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" }, { "aheadOn": [ "Security \u0026 auth, 55 against 43", "Payments \u0026 pricing, 40 against 10", "Maintenance \u0026 community, 68 against 20" ], "also": [ "Free to start without a card" ], "goodFor": "Maximising find rate on known contacts, especially mobiles, without a long-term contract.", "slug": "fullenrich", "watchFor": "Enrichment sources are third-party providers the vendor doesn't name" } ], "job": { "capability": "lead.enrichment", "name": "Lead enrichment" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apollo-vs-fullenrich.json", "title": "Apollo API + MCP vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/apollo-vs-fullenrich" }, { "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/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/crustdata-vs-fullenrich.json", "title": "Crustdata API + MCP vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/crustdata-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.json", "title": "Enrich Layer API + MCP vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.json", "title": "Explorium AgentSource vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.json", "title": "FullEnrich API + MCP vs Fuse MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.json", "title": "FullEnrich API + MCP vs Gojiberry", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-hunter.json", "title": "FullEnrich API + MCP vs Hunter API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-hunter" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.json", "title": "FullEnrich API + MCP vs LeadMagic API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha.json", "title": "FullEnrich API + MCP vs Lusha API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-lusha" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.json", "title": "FullEnrich API + MCP vs People Data Labs", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.json", "title": "FullEnrich API + MCP vs Prospeo API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-prospeo" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.json", "title": "FullEnrich API + MCP vs RocketReach API", "url": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach" }, { "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.json", "title": "FullEnrich API + MCP vs ZoomInfo API + MCP", "url": "https://www.anchorterminal.com/compare/fullenrich-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-fullcontact.json", "title": "Clay vs FullContact", "url": "https://www.anchorterminal.com/compare/clay-vs-fullcontact" }, { "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/clearbit-vs-fullenrich.json", "title": "Clearbit vs FullEnrich API + MCP", "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich" }, { "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/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/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-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": 2, "edge": "fullcontact", "fullcontact": 62, "fullenrich": 60, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "fullenrich", "fullcontact": 70, "fullenrich": 72, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 15, "edge": "fullcontact", "fullcontact": 75, "fullenrich": 60, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 12, "edge": "fullenrich", "fullcontact": 43, "fullenrich": 55, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 30, "edge": "fullenrich", "fullcontact": 10, "fullenrich": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 48, "edge": "fullenrich", "fullcontact": 20, "fullenrich": 68, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 3, "edge": "fullenrich", "fullcontact": 61, "fullenrich": 64, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "FullEnrich API + MCP scores 59.6 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on agent ergonomics. Both do lead enrichment.", "verdicts": { "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.", "fullenrich": "Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich", "json": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.md", "slim": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.min.md" }, "markdown": "FullEnrich API + MCP scores 59.6 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on agent ergonomics. Both do lead enrichment.\n\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- FullEnrich API + MCP: grade C, 59.6/100, rank #572 of 1076. Markdown https://www.anchorterminal.com/tools/fullenrich.md · JSON https://www.anchorterminal.com/api/v1/tools/fullenrich.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### 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- Agent ergonomics, 75 against 60\n\nWatch for: No public prices. Access starts with a sales conversation\n\n### FullEnrich API + MCP (C)\n\nGood for: Maximising find rate on known contacts, especially mobiles, without a long-term contract.\n\nAhead on:\n- Security \u0026 auth, 55 against 43\n- Payments \u0026 pricing, 40 against 10\n- Maintenance \u0026 community, 68 against 20\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Enrichment sources are third-party providers the vendor doesn't name\n\n\n## Score by category\n\n| Category | Weight | FullContact | FullEnrich API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 60 | FullContact +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 72 | FullEnrich API + MCP +2 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 60 | FullContact +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 55 | FullEnrich API + MCP +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 40 | FullEnrich API + MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 68 | FullEnrich API + MCP +48 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 64 | FullEnrich API + MCP +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **51.8 · D** | **59.6 · C** | |\n\n## Facts side by side\n\n| Fact | FullContact | FullEnrich API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | J2 Martech Corp. (FullContact, a Ziff Davis company) | FullEnrich |\n| Hosted endpoint | `https://api.fullcontact.com/v3` | `https://app.fullenrich.com/api/v2` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub | none |\n| Tools exposed | 1 | 13 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.FullEnrich/fullenrich` |\n| Last release | 2026-04-30 | 2026-08-27 |\n| Terms last updated | 2025-03-21 | 2026-08-20 |\n| Privacy policy last updated | 2026-10-01 | 2026-08-20 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\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**FullEnrich API + MCP.** Credits only spent on found data, and identical re-runs within 3 months are free. Enrichment sources are third-party providers the vendor doesn't name.\n\n## Before you call either\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### FullEnrich API + MCP\n\n1. Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again\n2. Expect 30 to 90 seconds a contact. Use the webhook or poll `get_enrichment_results`\n3. Ask for mobiles only when needed. They cost 10 credits against 1 for a work email\n4. Call `list_industries` and `list_seniorities` before filtering search\n5. Use the 0-credit test contacts in the docs to check an integration\n\n## Questions\n\n### Which is better for AI agents, FullContact or FullEnrich API + MCP?\n\nFullEnrich API + MCP scores 59.6 (C) on agent readiness against FullContact's 51.8 (D), and leads in 5 of 7 scored categories. FullContact leads on agent ergonomics.\n\n### Do FullContact and FullEnrich API + MCP need an API key?\n\nFullContact needs an API key. FullEnrich API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call FullContact and FullEnrich API + MCP without installing anything?\n\nYes. FullContact has a hosted endpoint at https://api.fullcontact.com/v3 and FullEnrich API + MCP at https://app.fullenrich.com/api/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fullcontact\", \"b\": \"fullenrich\"}`. From a terminal: `anchor compare fullcontact fullenrich`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fullcontact.json and https://www.anchorterminal.com/api/v1/tools/fullenrich.json\n\n## Other comparisons with FullContact or FullEnrich API + MCP\n\n- [Apollo API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/apollo-vs-fullenrich.md)\n- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)\n- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)\n- [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md)\n- [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md)\n- [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md)\n- [FullEnrich API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/fullenrich-vs-fuse-mcp.md)\n- [FullEnrich API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/fullenrich-vs-gojiberry.md)\n- [FullEnrich API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-hunter.md)\n- [FullEnrich API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-leadmagic.md)\n- [FullEnrich API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-lusha.md)\n- [FullEnrich API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.md)\n- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)\n- [FullEnrich API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.md)\n- [FullEnrich API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-zoominfo.md)\n- [Apollo API + MCP vs FullContact](https://www.anchorterminal.com/compare/apollo-vs-fullcontact.md)\n- [Clay vs FullContact](https://www.anchorterminal.com/compare/clay-vs-fullcontact.md)\n- [Clearbit vs FullContact](https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.md)\n- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.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- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.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 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": "FullContact vs FullEnrich API + MCP", "url": "" } ], "description": "FullEnrich scores 59.6 (C) to FullContact's 51.8 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "FullContact D 51.8", "FullEnrich API + MCP C 59.6", "scores" ], "h1": "FullContact vs FullEnrich API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-fullcontact-vs-fullenrich.png", "path": "/compare/fullcontact-vs-fullenrich", "published": "2026-10-01", "section": "tools", "title": "FullContact vs FullEnrich for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich" }, "tokens": { "markdown": 2650, "slim": 680 }, "version": 1 }