{
  "data": {
    "a": {
      "slug": "dropcontact",
      "name": "Dropcontact API + MCP",
      "vendor": "Dropcontact",
      "vendorUrl": "https://www.dropcontact.com",
      "company": "dropcontact.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Dropcontact's REST API and hosted MCP server find and verify professional email addresses and add job and company data to contacts sent with a name and a company.",
      "url": "https://www.anchorterminal.com/tools/dropcontact",
      "markdownUrl": "https://www.anchorterminal.com/tools/dropcontact.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dropcontact.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/dropcontact.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dropcontact.json",
      "dns": "dropcontact.grade.anchorterminal.com",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.dropcontact.com/v1",
      "packages": [],
      "auth": "mixed",
      "authNotes": "`X-Access-Token` header on REST. Hosted MCP at mcp.dropcontact.com uses OAuth, or the API key as `Authorization: Bearer`.",
      "pricing": "paid",
      "pricingNotes": "Prices are in euros only. 50 free credits to try. Starter €79 a month for 500 credits, Growth €120 a month for 500 credits with carry-over, LinkedIn URL enrichment and company data, both scaling to 150,000 credits a month. Yearly billing is 20 per cent off. Enterprise from 200,000 credits a month. A credit is spent only when a verified email comes back (refunded if none is found), or 1 credit per email you send in for verification (https://www.dropcontact.com/pricing).",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402 mention in the API docs, MCP docs or pricing (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://developer.dropcontact.com",
      "llmsTxt": "https://developer.dropcontact.com/llms.txt",
      "capabilities": [
        "lead.enrichment",
        "email.finder",
        "email.verification",
        "data.company"
      ],
      "tags": [
        "enrichment",
        "email-verification",
        "hosted",
        "no-card",
        "mcp",
        "llms-txt",
        "webhooks",
        "async-jobs",
        "closed-source"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 61.6,
        "grade": "C",
        "agentReady": false,
        "rank": 727,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 9,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 64,
          "maintenance": 15,
          "payments": 60,
          "reliability": 85,
          "schema": 54,
          "security": 59,
          "transparency": 72
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.",
        "bestFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.",
        "strengths": [
          "Pay on success, with credits refunded when no email is found",
          "50 free credits with no card",
          "Statuspage with its own API component and no incident since March 2026",
          "Errors page lists each message by status code with what to do, plus per-contact error and warning keys",
          "llms.txt and Markdown docs, security.txt with a HackerOne programme, and a published DPA"
        ],
        "weaknesses": [
          "No OpenAPI file or changelog",
          "No prospect search, so it only enriches people you already have",
          "Asynchronous only, with webhooks that can arrive out of order or twice",
          "One unscoped API key per account",
          "Remote MCP connections called early by the vendor, and no registry entry we could read"
        ],
        "agentNotes": [
          "Send a company name, website, email or LinkedIn URL with every contact, or you get `only_contact_data`",
          "Read `success` on every 200. A result still processing answers 200 with `success: false`",
          "Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen",
          "Poll no faster than every 30 seconds, and back off for a few seconds after a 429",
          "Call Get Credits to read the balance at no cost"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 61.6
          }
        ],
        "editorialScores": {
          "ergonomics": 64,
          "maintenance": 15,
          "payments": 60,
          "reliability": 85,
          "schema": 54,
          "security": 59,
          "transparency": 55
        },
        "provenanceScore": 88,
        "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 -X POST https://api.dropcontact.com/v1/enrich/all -H \"X-Access-Token: $DROPCONTACT_API_KEY\" \\\n  -H \"Content-Type: application/json\" -d '{\"data\":[{\"first_name\":\"John\",\"last_name\":\"Smith\",\"website\":\"corporation.com\"}],\"language\":\"en\"}'",
        "claudeCode": "claude mcp add --transport http dropcontact https://mcp.dropcontact.com/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/lead.enrichment",
        "tool": "https://letme.dev/dropcontact"
      },
      "area": "web-data",
      "provenance": {
        "legalEntity": "Dropcontact SAS",
        "domain": "dropcontact.com",
        "domainRegistered": "2016-03-21",
        "endpointOnVendorDomain": true,
        "terms": "https://www.dropcontact.com/terms",
        "privacy": "https://www.dropcontact.com/personal-data-charter",
        "statusPage": "https://status.dropcontact.com",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-04",
        "notes": [
          "Terms name a simplified joint stock company (SAS) registered in Bobigny, no. 823 752 647",
          "The terms (in force since 18 March 2020, updated 5 August 2025) carry no ban on automated access to the site."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/dropcontact.json",
      "live": {
        "slug": "dropcontact",
        "probe": {
          "target": "https://api.dropcontact.com/v1",
          "method": "get",
          "lastAt": "2026-11-22T22:37:02.819946926Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 146,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 58,
          "p95ms24h": 144,
          "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.dropcontact.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-22T22:30:28.115983756Z"
        },
        "securityTxt": {
          "url": "https://dropcontact.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-04-09T00:00:00.000Z",
          "checkedAt": "2026-11-22T16:40:55.856510159Z"
        },
        "llmsTxt": {
          "url": "https://developer.dropcontact.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-22T16:30:16.9726628Z"
        },
        "domain": {
          "domain": "dropcontact.com",
          "registered": "2016-03-21",
          "source": "https://rdap.verisign.com/com/v1/domain/dropcontact.com",
          "checkedAt": "2026-11-22T15:51:28.577877641Z"
        },
        "pages": [
          {
            "url": "https://developer.dropcontact.com",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-04T08:18:12.087098414Z",
            "changedAt": "2026-11-04T08:18:12.087098414Z",
            "fingerprint": "e3d50cde523f"
          },
          {
            "url": "https://developer.dropcontact.com/en/errors/",
            "kind": "deprecations",
            "status": 304,
            "checkedAt": "2026-11-21T23:40:05.661150907Z",
            "changedAt": "2026-11-09T15:34:22.031847287Z",
            "fingerprint": "d4cc68655636"
          },
          {
            "url": "https://www.dropcontact.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-22T00:05:34.108658508Z",
            "changedAt": "2026-11-19T22:43:35.508345862Z",
            "fingerprint": "1f24cab2fec1"
          },
          {
            "url": "https://www.dropcontact.com/personal-data-charter",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-22T00:05:31.981754205Z",
            "changedAt": "2026-11-19T22:43:33.301801565Z",
            "fingerprint": "d2f9335872b1"
          },
          {
            "url": "https://www.dropcontact.com/terms",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-22T00:05:36.067524823Z",
            "changedAt": "2026-11-19T22:43:37.449889414Z",
            "fingerprint": "03a45682b1f0"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.dropcontact.com/mcp",
          "checkedAt": "2026-11-22T05:22:54.841317359Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:43:57.867463276Z"
        },
        "updatedAt": "2026-11-22T22:37:02.819946926Z"
      },
      "streak": {
        "days": 45,
        "from": "2026-10-08",
        "sinceWatching": true,
        "last": {
          "kind": "breaking",
          "date": "2026-06-01",
          "what": "Accounts created since 1 June 2026 have the `API_ERROR` option on by default, so a request whose every record has an error gets a 400 instead of a 200",
          "source": "https://developer.dropcontact.com/en/errors/"
        },
        "best": 45
      }
    },
    "answer": "Leadsets scores 62.9 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments \u0026 pricing and transparency \u0026 trust.",
    "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": 65,
        "category": "maintenance",
        "leads": "leadsets",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "No changelog. The newest dated API change found is the `API_ERROR` option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.",
          "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": 15,
          "b": 80
        }
      },
      {
        "by": 45,
        "category": "reliability",
        "leads": "dropcontact",
        "name": "Reliability",
        "reasons": {
          "a": "Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.",
          "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": 85,
          "b": 40
        }
      },
      {
        "by": 26,
        "category": "ergonomics",
        "leads": "leadsets",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. `forceResults=true` returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as `only_contact_data` say what to add (20). Asynchronous jobs keyed by `request_id` and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.",
          "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": 64,
          "b": 90
        }
      },
      {
        "by": 10,
        "category": "payments",
        "leads": "dropcontact",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (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
        }
      },
      {
        "by": 8,
        "category": "security",
        "leads": "leadsets",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "One API key per account in the `X-Access-Token` header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.",
          "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": 59,
          "b": 67
        }
      },
      {
        "by": 5,
        "category": "transparency",
        "leads": "dropcontact",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.",
          "b": "Closed service with terms naming Mobylogix LLC under Texas law. The SDK is MIT (15). The privacy policy, terms, DPA and compliance page say where dataset records come from (licensed suppliers and permitted public sources such as company websites), what is held, that uploaded files are deleted 30 days after a job, and how to opt out. The suppliers aren't named, and the privacy policy says analytics run only on the public website while the compliance page lists PostHog and Google Analytics as \"Product analytics (customers only)\" (20 of 30). Breaking changes get 90 days' notice by email and material changes to plans or terms 30 days, with no dated notices yet (15 of 20). Subprocessors named (Vercel, Supabase, Stripe, Resend, PostHog, Google Analytics), all in the US, with 30 days' notice before adding one (18 of 20). 15 + 20 + 15 + 18 = 68."
        },
        "scores": {
          "a": 72,
          "b": 67
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Dropcontact",
        "b": "Leadsets",
        "name": "Vendor"
      },
      {
        "a": "https://api.dropcontact.com/v1",
        "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": "Paid",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "8",
        "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.leadsets/leadsets",
        "name": "MCP registry"
      },
      {
        "a": "none",
        "b": "2026-11-22",
        "name": "Last release"
      },
      {
        "a": "2025-08-01",
        "b": "2026-11-15",
        "name": "Terms last updated"
      },
      {
        "a": "2020-06-04",
        "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": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Leadsets scores 62.9 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments \u0026 pricing and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Dropcontact API + MCP or Leadsets?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Dropcontact API + MCP and Leadsets need an API key?"
      },
      {
        "answer": "Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Leadsets at https://mcp.leadsets.ai.",
        "question": "Can an agent call Dropcontact API + MCP and Leadsets without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 85 against 40",
          "Payments \u0026 pricing, 60 against 50",
          "Transparency \u0026 trust, 72 against 67"
        ],
        "also": null,
        "goodFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.",
        "slug": "dropcontact",
        "watchFor": "No OpenAPI file or changelog"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 90 against 64",
          "Security \u0026 auth, 67 against 59",
          "Maintenance \u0026 community, 80 against 15"
        ],
        "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": {
      "dropcontact": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 59.1,
          "fromGrade": "C",
          "to": 61.6,
          "toGrade": "C"
        },
        {
          "causes": [
            "product",
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 8.1,
          "from": 51,
          "fromGrade": "D",
          "to": 59.1,
          "toGrade": "C"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 50.9,
          "fromGrade": "D",
          "to": 51,
          "toGrade": "D"
        }
      ],
      "leadsets": null
    },
    "job": {
      "capability": "lead.enrichment",
      "name": "Lead enrichment"
    },
    "others": [
      {
        "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-leadsets.json",
        "title": "Clay vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadsets"
      },
      {
        "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-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-leadsets.json",
        "title": "Dievio vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-leadsets"
      },
      {
        "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-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-leadsets.json",
        "title": "FullEnrich API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets"
      },
      {
        "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/apollo-vs-dropcontact.json",
        "title": "Apollo API + MCP vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.json",
        "title": "Clay vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.json",
        "title": "Clearbit vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact"
      },
      {
        "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/coresignal-vs-dropcontact.json",
        "title": "Coresignal API + MCP vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.json",
        "title": "Crustdata API + MCP vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-dropcontact.json",
        "title": "Databar vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-dropcontact"
      },
      {
        "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/dievio-vs-dropcontact.json",
        "title": "Dievio vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.json",
        "title": "Dropcontact API + MCP vs Enrich Layer API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.json",
        "title": "Dropcontact API + MCP vs Explorium AgentSource",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.json",
        "title": "Dropcontact API + MCP vs FullContact",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.json",
        "title": "Dropcontact API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.json",
        "title": "Dropcontact API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.json",
        "title": "Dropcontact API + MCP vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter.json",
        "title": "Dropcontact API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.json",
        "title": "Dropcontact API + MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha.json",
        "title": "Dropcontact API + MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.json",
        "title": "Dropcontact API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.json",
        "title": "Dropcontact API + MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.json",
        "title": "Dropcontact API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.json",
        "title": "Dropcontact API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.json",
        "title": "Dropcontact API + MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo"
      },
      {
        "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/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": 45,
        "dropcontact": 85,
        "edge": "dropcontact",
        "key": "reliability",
        "leadsets": 40,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 4,
        "dropcontact": 54,
        "edge": "leadsets",
        "key": "schema",
        "leadsets": 58,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 26,
        "dropcontact": 64,
        "edge": "leadsets",
        "key": "ergonomics",
        "leadsets": 90,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 8,
        "dropcontact": 59,
        "edge": "leadsets",
        "key": "security",
        "leadsets": 67,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 10,
        "dropcontact": 60,
        "edge": "dropcontact",
        "key": "payments",
        "leadsets": 50,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 65,
        "dropcontact": 15,
        "edge": "leadsets",
        "key": "maintenance",
        "leadsets": 80,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 5,
        "dropcontact": 72,
        "edge": "dropcontact",
        "key": "transparency",
        "leadsets": 67,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Leadsets scores 62.9 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments \u0026 pricing and transparency \u0026 trust. Both do lead enrichment.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "dropcontact": "Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.",
      "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/dropcontact-vs-leadsets",
    "json": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.min.md"
  },
  "markdown": "Leadsets scores 62.9 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments \u0026 pricing and transparency \u0026 trust. Both do lead enrichment.\n\n- Dropcontact API + MCP: grade C, 61.6/100, rank #727 of 1571. Markdown https://www.anchorterminal.com/tools/dropcontact.md · JSON https://www.anchorterminal.com/api/v1/tools/dropcontact.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### Dropcontact API + MCP (C)\n\nGood for: European teams cleaning and completing contact lists where GDPR handling matters more than coverage.\n\nAhead on:\n- Reliability, 85 against 40\n- Payments \u0026 pricing, 60 against 50\n- Transparency \u0026 trust, 72 against 67\n\nWatch for: No OpenAPI file or changelog\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 64\n- Security \u0026 auth, 67 against 59\n- Maintenance \u0026 community, 80 against 15\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 +65\n\n- Dropcontact API + MCP (15): No changelog. The newest dated API change found is the `API_ERROR` option, on by default for accounts created since 1 June 2026, which answers 400 when every record in a request has an error. That is between 90 and 180 days ago (10). The rebuilt docs carry no dated entries, so none fall in the 90 days from 6 August (0). Email support on every plan and no public changelog (5 of 15). No official SDKs and no registry entry we could read (0). No packages to judge (0, an in-between 3 with nothing behind it before). 10 + 0 + 5 + 0 + 0 = 15.\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: Dropcontact API + MCP +45\n\n- Dropcontact API + MCP (85): Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.\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 +26\n\n- Dropcontact API + MCP (64): The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. `forceResults=true` returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as `only_contact_data` say what to add (20). Asynchronous jobs keyed by `request_id` and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.\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### Payments \u0026 pricing: Dropcontact API + MCP +10\n\n- Dropcontact API + MCP (60): No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (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### Security \u0026 auth: Leadsets +8\n\n- Dropcontact API + MCP (59): One API key per account in the `X-Access-Token` header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.\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### Transparency \u0026 trust: Dropcontact API + MCP +5\n\n- Dropcontact API + MCP (72): Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.\n- Leadsets (67): Closed service with terms naming Mobylogix LLC under Texas law. The SDK is MIT (15). The privacy policy, terms, DPA and compliance page say where dataset records come from (licensed suppliers and permitted public sources such as company websites), what is held, that uploaded files are deleted 30 days after a job, and how to opt out. The suppliers aren't named, and the privacy policy says analytics run only on the public website while the compliance page lists PostHog and Google Analytics as \"Product analytics (customers only)\" (20 of 30). Breaking changes get 90 days' notice by email and material changes to plans or terms 30 days, with no dated notices yet (15 of 20). Subprocessors named (Vercel, Supabase, Stripe, Resend, PostHog, Google Analytics), all in the US, with 30 days' notice before adding one (18 of 20). 15 + 20 + 15 + 18 = 68.\n\n## Score by category\n\n| Category | Weight | Dropcontact API + MCP | Leadsets | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 85 | 40 | Dropcontact API + MCP +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 54 | 58 | Leadsets +4 |\n| Agent ergonomics | 13% | 64 | 90 | Leadsets +26 |\n| Security \u0026 auth | 14% | 59 | 67 | Leadsets +8 |\n| Payments \u0026 pricing | 10% | 60 | 50 | Dropcontact API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 15 | 80 | Leadsets +65 |\n| Transparency \u0026 trust | 7% | 72 | 67 | Dropcontact API + MCP +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.6 · C** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Dropcontact API + MCP | Leadsets |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Dropcontact | Leadsets |\n| Hosted endpoint | `https://api.dropcontact.com/v1` | `https://mcp.leadsets.ai` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Tools exposed | none | 8 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.leadsets/leadsets` |\n| Last release | none | 2026-11-22 |\n| Terms last updated | 2025-08-01 | 2026-11-15 |\n| Privacy policy last updated | 2020-06-04 | 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 | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Dropcontact API + MCP\n\n- +2.5 on 13 November 2026: checklist\n- +8.1 on 4 November 2026 (D to C): product, new evidence, correction\n- +0.1 on 27 October 2026: checklist\n\n### Leadsets\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Dropcontact API + MCP.** Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.\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### Dropcontact API + MCP\n\n1. Send a company name, website, email or LinkedIn URL with every contact, or you get `only_contact_data`\n2. Read `success` on every 200. A result still processing answers 200 with `success: false`\n3. Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen\n4. Poll no faster than every 30 seconds, and back off for a few seconds after a 429\n5. Call Get Credits to read the balance at no cost\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, Dropcontact API + MCP or Leadsets?\n\nLeadsets scores 62.9 (B) on agent readiness against Dropcontact API + MCP's 61.6 (C), and leads in 4 of 7 scored categories. Dropcontact API + MCP leads on reliability, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do Dropcontact 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 Dropcontact API + MCP and Leadsets without installing anything?\n\nYes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Leadsets at https://mcp.leadsets.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"dropcontact\", \"b\": \"leadsets\"}`. From a terminal: `anchor compare dropcontact leadsets`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/dropcontact.json and https://www.anchorterminal.com/api/v1/tools/leadsets.json\n\n## Other comparisons with Dropcontact API + MCP or Leadsets\n\n- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)\n- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)\n- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)\n- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)\n- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)\n- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)\n- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.md)\n- [FullEnrich API + MCP vs Leadsets](https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.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- [Apollo API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/apollo-vs-dropcontact.md)\n- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)\n- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)\n- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)\n- [Coresignal API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-dropcontact.md)\n- [Crustdata API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.md)\n- [Databar vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/databar-vs-dropcontact.md)\n- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)\n- [Dievio vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/dievio-vs-dropcontact.md)\n- [Dropcontact API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.md)\n- [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md)\n- [Dropcontact API + MCP vs FullContact](https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.md)\n- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)\n- [Dropcontact API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.md)\n- [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)\n- [Dropcontact API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-hunter.md)\n- [Dropcontact API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.md)\n- [Dropcontact API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-lusha.md)\n- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md)\n- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [Dropcontact API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.md)\n- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)\n- [Dropcontact API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.md)\n- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.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": "Dropcontact API + MCP vs Leadsets",
        "url": ""
      }
    ],
    "description": "Leadsets scores 62.9 (B) to Dropcontact's 61.6 (C) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Dropcontact API + MCP C 61.6",
      "Leadsets B 62.9",
      "scores"
    ],
    "h1": "Dropcontact API + MCP vs Leadsets",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/dropcontact-vs-leadsets",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Dropcontact vs Leadsets for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-22",
    "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets"
  },
  "tokens": {
    "markdown": 5350,
    "slim": 1030
  },
  "version": 1
}
