{
  "data": {
    "a": {
      "slug": "fullenrich",
      "name": "FullEnrich API + MCP",
      "vendor": "FullEnrich",
      "vendorUrl": "https://fullenrich.com",
      "company": "fullenrich.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Waterfall contact enrichment that queries 25+ data providers for work emails, personal emails and mobile numbers, plus people and company search and lookup 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",
      "cardUrl": "https://www.anchorterminal.com/tools/fullenrich.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fullenrich.json",
      "dns": "fullenrich.grade.anchorterminal.com",
      "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 $29 a month for 500 credits ($55 for 1,000, about $0.055 a credit), scaling to $3,500 a month for 100,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.md, checked 2026-11-04).",
      "priceSummary": "$29 / 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": 64.7,
        "grade": "B",
        "agentReady": false,
        "rank": 575,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 4,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 48,
          "payments": 60,
          "reliability": 70,
          "schema": 76,
          "security": 57,
          "transparency": 68
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.",
        "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 with per-operation error codes, llms.txt and a Markdown pricing page",
          "SOC 2 Type 2 per the trust page, with data hosted in the EU"
        ],
        "weaknesses": [
          "Enrichment sources are data providers the vendor doesn't name",
          "Status page covers the web app only, not the API or MCP",
          "No safe-retry guidance for writes and no SLA",
          "Public product changelog stopped at November 2024 and now answers an error",
          "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",
          "On a 429 with `error.rate.limit`, wait a minute before retrying. The limit is 60 calls a minute on every endpoint"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.7
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 48,
          "payments": 60,
          "reliability": 70,
          "schema": 76,
          "security": 57,
          "transparency": 56
        },
        "provenanceScore": 80,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "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, 500 credits",
          "unit": "month",
          "usd": 29
        },
        {
          "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-11-04",
        "notes": [
          "The public changelog's newest entry is 30 November 2024 per the 1 October 2026 check; on 4 November 2026 the page answered 400 \"Invalid page\". 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. Its robots.txt is an empty 200 (no rules)",
          "fullenrich.com/.well-known/security.txt answered 404 on 4 November 2026"
        ],
        "score": 80
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/fullenrich.json",
      "live": {
        "slug": "fullenrich",
        "probe": {
          "target": "https://app.fullenrich.com/api/v2",
          "method": "get",
          "lastAt": "2026-11-22T22:37:07.189450967Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 122,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 64,
          "p95ms24h": 146,
          "samples24h": 242,
          "samples30d": 7788,
          "days": [
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 240,
              "ok": 240
            },
            {
              "date": "2026-11-19",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-20",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-21",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-22",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.fullenrich.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-22T22:07:48.300231679Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.github.FullEnrich/fullenrich",
            "version": "1.0.4",
            "seenAt": "2026-11-22T00:00:22.236652523Z"
          }
        ],
        "securityTxt": {
          "url": "https://fullenrich.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-22T16:40:18.255526085Z"
        },
        "llmsTxt": {
          "url": "https://docs.fullenrich.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-22T16:30:30.709688403Z"
        },
        "domain": {
          "domain": "fullenrich.com",
          "registered": "2023-04-08",
          "source": "https://rdap.verisign.com/com/v1/domain/fullenrich.com",
          "checkedAt": "2026-11-22T15:55:52.873733957Z"
        },
        "pages": [
          {
            "url": "https://fullenrich.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-21T23:47:07.778347604Z",
            "changedAt": "2026-11-06T13:32:21.946678463Z",
            "fingerprint": "21cc3cbeed28"
          },
          {
            "url": "https://fullenrich.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-04T08:24:22.224697456Z",
            "changedAt": "2026-10-28T04:18:22.922082282Z",
            "fingerprint": "b320816d19e5"
          },
          {
            "url": "https://fullenrich.com/pricing.md",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-21T23:47:10.506196379Z",
            "changedAt": "2026-11-12T17:40:02.88622103Z",
            "fingerprint": "b4baf1057ebb"
          },
          {
            "url": "https://fullenrich.com/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-21T23:47:11.813254056Z",
            "changedAt": "2026-11-06T13:32:25.990764115Z",
            "fingerprint": "754c6d67f3dd"
          },
          {
            "url": "https://fullenrich.com/tos",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-21T23:47:14.001979943Z",
            "changedAt": "2026-11-06T13:32:28.60618135Z",
            "fingerprint": "b39985f843fd"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.fullenrich.com/mcp",
          "checkedAt": "2026-11-22T05:23:39.800022854Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:44:40.155434389Z"
        },
        "updatedAt": "2026-11-22T22:37:07.189450967Z"
      },
      "streak": {
        "days": 45,
        "from": "2026-10-08",
        "sinceWatching": true,
        "best": 45
      }
    },
    "answer": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.",
    "b": {
      "slug": "leadsets",
      "name": "Leadsets",
      "vendor": "Leadsets",
      "vendorUrl": "https://www.leadsets.ai",
      "company": "leadsets.ai",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Leadsets is a B2B data API and remote MCP server from Mobylogix LLC. Agents search people and companies, enrich them with verified work emails, verify addresses and scrape company websites over REST or eight MCP tools.",
      "url": "https://www.anchorterminal.com/tools/leadsets",
      "markdownUrl": "https://www.anchorterminal.com/tools/leadsets.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/leadsets.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/leadsets.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/leadsets.json",
      "dns": "leadsets.grade.anchorterminal.com",
      "repo": "https://github.com/leadsets/sdk",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.leadsets.ai",
      "packages": [
        {
          "registry": "npm",
          "name": "@leadsetsai/sdk"
        },
        {
          "registry": "pypi",
          "name": "leadsets"
        }
      ],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ls_live_...`) in the `Authorization` header for REST and MCP, made in the dashboard after a browser signup. Each key has one access level (full, data or read) and an expiry of never, 30, 90 or 365 days. Keys are stored as hashes, shown once and revoked within a minute. MCP clients that support it sign in with OAuth (authorisation code with PKCE S256 and dynamic client registration, no scopes listed in the server metadata).",
      "pricing": "freemium",
      "pricingNotes": "Free plan with 1,000 enrichment records, 100 search records and 1,000 data calls, one time, no card. Flat monthly plans at $29, $99, $399 and $999 with no per-record bill and fair-use limits per rolling five hours and per week. Scraping is an add-on in units, from $9 for 1,000. No machine payment protocol.",
      "priceSummary": "$29 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on the pricing page, the docs, the errors page or llms.txt (checked 2026-11-22). An exhausted Free meter returns 402 `free_records_exhausted` with no payment requirements, and the docs tell the agent to ask the user to upgrade.",
        "endpoints": []
      },
      "toolCount": 8,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-22"
      },
      "docsUrl": "https://www.leadsets.ai/docs",
      "llmsTxt": "https://www.leadsets.ai/llms.txt",
      "registryName": "io.github.leadsets/leadsets",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.verification",
        "email.finder",
        "data.person",
        "data.company",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "remote-mcp",
        "mcp-registry",
        "oauth",
        "api-key",
        "llms-txt",
        "typescript",
        "python",
        "closed-source",
        "no-status-page",
        "new",
        "lead-search",
        "enrichment",
        "email-verification"
      ],
      "lastRelease": "2026-11-22",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.9,
        "grade": "B",
        "agentReady": false,
        "rank": 661,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 90,
          "maintenance": 80,
          "payments": 50,
          "reliability": 40,
          "schema": 58,
          "security": 67,
          "transparency": 67
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-22"
        },
        "negative": 0,
        "verdict": "Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.",
        "bestFor": "Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.",
        "strengths": [
          "Errors carry a machine-readable `type` and `request_id`, and the docs say for each of 11 types whether to retry",
          "`Idempotency-Key` on paid calls lasts 24 hours, and a retry with the same key never counts records twice",
          "Keys carry a full, data or read access level and an optional expiry, and are revoked within a minute",
          "Free plan of 1,000 enrichment and 100 search records with no card, and empty results use no records",
          "TypeScript and Python SDKs that retry 429 and 5xx with Retry-After, and an entry in the official MCP registry"
        ],
        "weaknesses": [
          "No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing",
          "No OpenAPI file found, and the MCP tool definitions can't be read without an account",
          "The API changelog said on 22 November 2026 \"No releases yet. Release notes start at launch.\"",
          "Data comes from licensed suppliers that the pages don't name, and SOC 2 is a target for Q3 2027",
          "Signup and paid plans need a person in a browser, and there is no machine payment protocol"
        ],
        "agentNotes": [
          "Call get_usage before a large run. It costs nothing and returns every meter with its reset time",
          "Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once",
          "If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After",
          "Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it",
          "Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.9
          }
        ],
        "editorialScores": {
          "ergonomics": 90,
          "maintenance": 80,
          "payments": 50,
          "reliability": 40,
          "schema": 58,
          "security": 67,
          "transparency": 68
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-22",
            "maintenance": "2026-11-22",
            "payments": "2026-11-22",
            "reliability": "2026-11-22",
            "schema": "2026-11-22",
            "security": "2026-11-22",
            "transparency": "2026-11-22"
          },
          "last": "2026-11-22",
          "oldest": "2026-11-22",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm i @leadsetsai/sdk",
        "http": "curl https://api.leadsets.ai/v1/usage -H \"Authorization: Bearer $LEADSETS_KEY\"",
        "claudeCode": "claude mcp add --transport http leadsets https://mcp.leadsets.ai --header \"Authorization: Bearer $LEADSETS_KEY\"",
        "config": {
          "mcpServers": {
            "leadsets": {
              "headers": {
                "Authorization": "Bearer YOUR_LEADSETS_API_KEY"
              },
              "url": "https://mcp.leadsets.ai"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/leadsets"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Solo plan",
          "unit": "month",
          "usd": 29,
          "note": "1,000 enrichments per five hours, 5,000 a week"
        },
        {
          "item": "Pro plan",
          "unit": "month",
          "usd": 99,
          "note": "15,000 enrichments per five hours, 75,000 a week"
        },
        {
          "item": "Team plan",
          "unit": "month",
          "usd": 399,
          "note": "150,000 enrichments per five hours, 750,000 a week"
        },
        {
          "item": "Max plan",
          "unit": "month",
          "usd": 999,
          "note": "225,000 enrichments per five hours, 1.125 million a week"
        },
        {
          "item": "Scraping, 1,000-unit pack",
          "unit": "1k-pages",
          "usd": 9,
          "note": "One unit is one standard page"
        },
        {
          "item": "Scraping, 20,000-unit pack",
          "unit": "1k-pages",
          "usd": 2.45,
          "note": "$49 for 20,000 units"
        }
      ],
      "provenance": {
        "legalEntity": "Mobylogix LLC",
        "domain": "leadsets.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.leadsets.ai/terms",
        "privacy": "https://www.leadsets.ai/privacy",
        "statusPage": "",
        "changelog": "https://www.leadsets.ai/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-11-22",
        "notes": [
          "Mobylogix LLC is named on the terms (updated 15 November 2026), the privacy policy (updated 19 November 2026), llms.txt and the SDK's MIT licence. The terms say it is based in Austin, Texas, and choose Texas law and the courts of Travis County. The privacy policy's contact address is 10160 hwy 242, Conroe, TX 77385.",
          "www.leadsets.ai/robots.txt allows ClaudeBot, Claude-User and anthropic-ai except /app, /onboarding, /api/, /dev/, /md/, /auth/, /search and a few account pages. mcp.leadsets.ai/robots.txt answered 404, so that host publishes no rules.",
          "The terms forbid reselling or rebuilding the data and evading limits. No clause on automated reading of the website was found.",
          "RDAP for leadsets.ai answered 429 at rdap.org, so the registration date is unchecked.",
          "/.well-known/security.txt answered 404. No status page found. The SDK repository's SECURITY.md names security@leadsets.ai."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/leadsets.json",
      "live": {
        "slug": "leadsets",
        "probe": {
          "target": "https://mcp.leadsets.ai",
          "method": "get",
          "lastAt": "2026-11-22T22:37:18.649226285Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 176,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 234,
          "p95ms24h": 325,
          "samples24h": 9,
          "samples30d": 9,
          "days": [
            {
              "date": "2026-11-22",
              "probes": 9,
              "ok": 9
            }
          ],
          "since": "2026-11-22T21:49:45.065930097Z"
        },
        "updatedAt": "2026-11-22T22:37:18.649226285Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-22",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 32,
        "category": "maintenance",
        "leads": "leadsets",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.",
          "b": "The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80."
        },
        "scores": {
          "a": 48,
          "b": 80
        }
      },
      {
        "by": 30,
        "category": "reliability",
        "leads": "fullenrich",
        "name": "Reliability",
        "reasons": {
          "a": "Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says \"No incidents reported\" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message \"Too many requests. Try again in 1m\", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.",
          "b": "No status page found, and the support page answers \"Where can I check if Leadsets is down?\" by pointing to the 503 error and support email (0). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an `Idempotency-Key` on paid calls that makes retries safe for 24 hours (15). The terms say \"We aim for high availability but don't guarantee uninterrupted service unless agreed in writing\", and no SLA is published (0). No page calls the service beta or preview, but the changelog says \"No releases yet. Release notes start at launch.\", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40."
        },
        "scores": {
          "a": 70,
          "b": 40
        }
      },
      {
        "by": 24,
        "category": "ergonomics",
        "leads": "leadsets",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.",
          "b": "Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection found (20 of 25). Cursor pagination, typed filters, `max_age_days`, `exclude_stale` and `has_verified_email` (20). Every error has a status, a `type`, a `request_id`, the meter and `charged`, and the docs say whether to retry each one (20). `Idempotency-Key` on every paid call for 24 hours, with 409 `idempotency_conflict` for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as `limit` 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90."
        },
        "scores": {
          "a": 66,
          "b": 90
        }
      },
      {
        "by": 18,
        "category": "schema",
        "leads": "fullenrich",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a `code` and `message` schema and named examples such as `error.enrichment.first_name.empty` and `error.rate.limit`, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 \"Invalid page\" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.",
          "b": "No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for `limit` (1 to 100) and `max_age_days`, ISO country codes and booleans, with one nested `priorities` object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58."
        },
        "scores": {
          "a": 76,
          "b": 58
        }
      },
      {
        "by": 10,
        "category": "security",
        "leads": "leadsets",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.",
          "b": "Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional `X-Leadsets-Client` label, rate-limit headers and `request_id` on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67."
        },
        "scores": {
          "a": 57,
          "b": 67
        }
      },
      {
        "by": 10,
        "category": "payments",
        "leads": "fullenrich",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.",
          "b": "No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0). Plan prices and their per-window limits are public, with no per-record price, and scraping units are priced per pack ($9 for 1,000, $19 for 5,000, $49 for 20,000), so plan-only pricing with a per-unit add-on (20 of 30). Free plan of 1,000 enrichment records, 100 search records and 1,000 data calls, one time, \"no card required\" (30). A person signs up in a browser and makes the key in the dashboard (0). 0 + 20 + 30 + 0 = 50."
        },
        "scores": {
          "a": 60,
          "b": 50
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "FullEnrich",
        "b": "Leadsets",
        "name": "Vendor"
      },
      {
        "a": "https://app.fullenrich.com/api/v2",
        "b": "https://mcp.leadsets.ai",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "13",
        "b": "8",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "io.github.FullEnrich/fullenrich",
        "b": "io.github.leadsets/leadsets",
        "name": "MCP registry"
      },
      {
        "a": "2026-08-27",
        "b": "2026-11-22",
        "name": "Last release"
      },
      {
        "a": "2026-08-20",
        "b": "2026-11-15",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-20",
        "b": "2026-11-19",
        "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": "yes",
        "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": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.",
        "question": "Which is better for AI agents, FullEnrich API + MCP or Leadsets?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do FullEnrich API + MCP and Leadsets need an API key?"
      },
      {
        "answer": "Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Leadsets at https://mcp.leadsets.ai.",
        "question": "Can an agent call FullEnrich API + MCP and Leadsets without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 70 against 40",
          "Schema \u0026 documentation, 76 against 58",
          "Payments \u0026 pricing, 60 against 50"
        ],
        "also": null,
        "goodFor": "Maximising find rate on known contacts, especially mobiles, without a long-term contract.",
        "slug": "fullenrich",
        "watchFor": "Enrichment sources are data providers the vendor doesn't name"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 90 against 66",
          "Security \u0026 auth, 67 against 57",
          "Maintenance \u0026 community, 80 against 48"
        ],
        "also": null,
        "goodFor": "Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.",
        "slug": "leadsets",
        "watchFor": "No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing"
      }
    ],
    "history": {
      "fullenrich": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 62.2,
          "fromGrade": "B",
          "to": 64.7,
          "toGrade": "B"
        },
        {
          "causes": [
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 2.5,
          "from": 59.7,
          "fromGrade": "C",
          "to": 62.2,
          "toGrade": "B"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 59.6,
          "fromGrade": "C",
          "to": 59.7,
          "toGrade": "C"
        }
      ],
      "leadsets": null
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "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/apollo-vs-leadsets.json",
        "title": "Apollo API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-leadsets"
      },
      {
        "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-leadsets.json",
        "title": "Clay vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.json",
        "title": "Coresignal API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets.json",
        "title": "Coresignal API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets"
      },
      {
        "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/crustdata-vs-leadsets.json",
        "title": "Crustdata API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-fullenrich.json",
        "title": "Dievio vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-leadsets.json",
        "title": "Dievio vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-leadsets"
      },
      {
        "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/enrich-layer-vs-leadsets.json",
        "title": "Enrich Layer API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets"
      },
      {
        "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/explorium-agentsource-vs-leadsets.json",
        "title": "Explorium AgentSource vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets"
      },
      {
        "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-retriever.json",
        "title": "FullEnrich API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
      },
      {
        "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/fuse-mcp-vs-leadsets.json",
        "title": "Fuse MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.json",
        "title": "Gojiberry vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.json",
        "title": "LeadMagic API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-lusha.json",
        "title": "Leadsets vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.json",
        "title": "Leadsets vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-prospeo.json",
        "title": "Leadsets vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-retriever.json",
        "title": "Leadsets vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.json",
        "title": "Leadsets vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.json",
        "title": "Leadsets vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-zoominfo"
      },
      {
        "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/clearbit-vs-leadsets.json",
        "title": "Clearbit vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-fullenrich.json",
        "title": "Databar vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-leadsets.json",
        "title": "Databar vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/databar-vs-leadsets"
      },
      {
        "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-leadsets.json",
        "title": "Dropcontact API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets"
      },
      {
        "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-leadsets.json",
        "title": "FullContact vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json",
        "title": "FullEnrich API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-leadsets.json",
        "title": "Hunter API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.json",
        "title": "Leadsets vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-zerobounce"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 30,
        "edge": "fullenrich",
        "fullenrich": 70,
        "key": "reliability",
        "leadsets": 40,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 18,
        "edge": "fullenrich",
        "fullenrich": 76,
        "key": "schema",
        "leadsets": 58,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 24,
        "edge": "leadsets",
        "fullenrich": 66,
        "key": "ergonomics",
        "leadsets": 90,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 10,
        "edge": "leadsets",
        "fullenrich": 57,
        "key": "security",
        "leadsets": 67,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 10,
        "edge": "fullenrich",
        "fullenrich": 60,
        "key": "payments",
        "leadsets": 50,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 32,
        "edge": "leadsets",
        "fullenrich": 48,
        "key": "maintenance",
        "leadsets": 80,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 1,
        "edge": "fullenrich",
        "fullenrich": 68,
        "key": "transparency",
        "leadsets": 67,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "fullenrich": "Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.",
      "leadsets": "Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets",
    "json": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.min.md"
  },
  "markdown": "FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community. Both do lead search.\n\n- FullEnrich API + MCP: grade B, 64.7/100, rank #575 of 1571. Markdown https://www.anchorterminal.com/tools/fullenrich.md · JSON https://www.anchorterminal.com/api/v1/tools/fullenrich.json\n- Leadsets: grade B, 62.9/100, rank #661 of 1571. Markdown https://www.anchorterminal.com/tools/leadsets.md · JSON https://www.anchorterminal.com/api/v1/tools/leadsets.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 276 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### FullEnrich API + MCP (B)\n\nGood for: Maximising find rate on known contacts, especially mobiles, without a long-term contract.\n\nAhead on:\n- Reliability, 70 against 40\n- Schema \u0026 documentation, 76 against 58\n- Payments \u0026 pricing, 60 against 50\n\nWatch for: Enrichment sources are data providers the vendor doesn't name\n\n### Leadsets (B)\n\nGood for: Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.\n\nAhead on:\n- Agent ergonomics, 90 against 66\n- Security \u0026 auth, 67 against 57\n- Maintenance \u0026 community, 80 against 48\n\nWatch for: No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Leadsets +32\n\n- FullEnrich API + MCP (48): Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from `server.json` and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.\n- Leadsets (80): The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80.\n\n### Reliability: FullEnrich API + MCP +30\n\n- FullEnrich API + MCP (70): Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says \"No incidents reported\" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code `error.rate.limit` and the message \"Too many requests. Try again in 1m\", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.\n- Leadsets (40): No status page found, and the support page answers \"Where can I check if Leadsets is down?\" by pointing to the 503 error and support email (0). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an `Idempotency-Key` on paid calls that makes retries safe for 24 hours (15). The terms say \"We aim for high availability but don't guarantee uninterrupted service unless agreed in writing\", and no SLA is published (0). No page calls the service beta or preview, but the changelog says \"No releases yet. Release notes start at launch.\", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.\n\n### Agent ergonomics: Leadsets +24\n\n- FullEnrich API + MCP (66): 13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 66.\n- Leadsets (90): Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection found (20 of 25). Cursor pagination, typed filters, `max_age_days`, `exclude_stale` and `has_verified_email` (20). Every error has a status, a `type`, a `request_id`, the meter and `charged`, and the docs say whether to retry each one (20). `Idempotency-Key` on every paid call for 24 hours, with 409 `idempotency_conflict` for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as `limit` 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90.\n\n### Schema \u0026 documentation: FullEnrich API + MCP +18\n\n- FullEnrich API + MCP (76): OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a `code` and `message` schema and named examples such as `error.enrichment.first_name.empty` and `error.rate.limit`, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 \"Invalid page\" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.\n- Leadsets (58): No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for `limit` (1 to 100) and `max_age_days`, ISO country codes and booleans, with one nested `priorities` object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58.\n\n### Security \u0026 auth: Leadsets +10\n\n- FullEnrich API + MCP (57): Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.\n- Leadsets (67): Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional `X-Leadsets-Client` label, rate-limit headers and `request_id` on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67.\n\n### Payments \u0026 pricing: FullEnrich API + MCP +10\n\n- FullEnrich API + MCP (60): No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n- Leadsets (50): No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0). Plan prices and their per-window limits are public, with no per-record price, and scraping units are priced per pack ($9 for 1,000, $19 for 5,000, $49 for 20,000), so plan-only pricing with a per-unit add-on (20 of 30). Free plan of 1,000 enrichment records, 100 search records and 1,000 data calls, one time, \"no card required\" (30). A person signs up in a browser and makes the key in the dashboard (0). 0 + 20 + 30 + 0 = 50.\n\n## Score by category\n\n| Category | Weight | FullEnrich API + MCP | Leadsets | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 70 | 40 | FullEnrich API + MCP +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 76 | 58 | FullEnrich API + MCP +18 |\n| Agent ergonomics | 13% | 66 | 90 | Leadsets +24 |\n| Security \u0026 auth | 14% | 57 | 67 | Leadsets +10 |\n| Payments \u0026 pricing | 10% | 60 | 50 | FullEnrich API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 48 | 80 | Leadsets +32 |\n| Transparency \u0026 trust | 7% | 68 | 67 | FullEnrich API + MCP +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.7 · B** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | FullEnrich API + MCP | Leadsets |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FullEnrich | Leadsets |\n| Hosted endpoint | `https://app.fullenrich.com/api/v2` | `https://mcp.leadsets.ai` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 13 | 8 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.FullEnrich/fullenrich` | `io.github.leadsets/leadsets` |\n| Last release | 2026-08-27 | 2026-11-22 |\n| Terms last updated | 2026-08-20 | 2026-11-15 |\n| Privacy policy last updated | 2026-08-20 | 2026-11-19 |\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 | yes | 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 | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### FullEnrich API + MCP\n\n- +2.5 on 13 November 2026: checklist\n- +2.5 on 4 November 2026 (C to B): new evidence, correction\n- +0.1 on 28 October 2026: new evidence\n\n### Leadsets\n\nNo score change since it was listed.\n\n## Verdicts\n\n**FullEnrich API + MCP.** Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.\n\n**Leadsets.** Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.\n\n## Before you call either\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\n6. On a 429 with `error.rate.limit`, wait a minute before retrying. The limit is 60 calls a minute on every endpoint\n\n### Leadsets\n\n1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time\n2. Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once\n3. If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After\n4. Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it\n5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found\n\n## Questions\n\n### Which is better for AI agents, FullEnrich API + MCP or Leadsets?\n\nFullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security \u0026 auth and maintenance \u0026 community.\n\n### Do FullEnrich API + MCP and Leadsets need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call FullEnrich API + MCP and Leadsets without installing anything?\n\nYes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Leadsets at https://mcp.leadsets.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fullenrich\", \"b\": \"leadsets\"}`. From a terminal: `anchor compare fullenrich leadsets`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fullenrich.json and https://www.anchorterminal.com/api/v1/tools/leadsets.json\n\n## Other comparisons with FullEnrich API + MCP or Leadsets\n\n- [Apollo API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/apollo-vs-fullenrich.md)\n- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)\n- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)\n- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)\n- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)\n- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)\n- [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md)\n- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)\n- [Dievio vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dievio-vs-fullenrich.md)\n- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)\n- [Enrich Layer API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-fullenrich.md)\n- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)\n- [Explorium AgentSource vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-fullenrich.md)\n- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.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 Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.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- [Fuse MCP vs Leadsets](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.md)\n- [Gojiberry vs Leadsets](https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.md)\n- [LeadMagic API + MCP vs Leadsets](https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.md)\n- [Leadsets vs Lusha API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-lusha.md)\n- [Leadsets vs People Data Labs](https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.md)\n- [Leadsets vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-prospeo.md)\n- [Leadsets vs Retriever](https://www.anchorterminal.com/compare/leadsets-vs-retriever.md)\n- [Leadsets vs RocketReach API](https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.md)\n- [Leadsets vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.md)\n- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.md)\n- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)\n- [Databar vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/databar-vs-fullenrich.md)\n- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)\n- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)\n- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md)\n- [FullContact vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-fullenrich.md)\n- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md)\n- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)\n- [Hunter API + MCP vs Leadsets](https://www.anchorterminal.com/compare/hunter-vs-leadsets.md)\n- [Leadsets vs ZeroBounce](https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-22",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "FullEnrich API + MCP vs Leadsets",
        "url": ""
      }
    ],
    "description": "FullEnrich scores 64.7 (B) to Leadsets's 62.9 (B) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "FullEnrich API + MCP B 64.7",
      "Leadsets B 62.9",
      "scores"
    ],
    "h1": "FullEnrich API + MCP vs Leadsets",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/fullenrich-vs-leadsets",
    "published": "2026-10-01",
    "section": "tools",
    "title": "FullEnrich vs Leadsets for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-22",
    "url": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets"
  },
  "tokens": {
    "markdown": 5650,
    "slim": 1080
  },
  "version": 1
}
