{
  "data": {
    "a": {
      "slug": "hunter",
      "name": "Hunter API + MCP",
      "vendor": "Hunter",
      "vendorUrl": "https://hunter.io",
      "company": "hunter.io",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Email finder, email verifier, domain search, company discovery and person and company enrichment over a REST API, plus a hosted MCP server that also drives Hunter's leads, lists and cold-email sequences.",
      "url": "https://www.anchorterminal.com/tools/hunter",
      "markdownUrl": "https://www.anchorterminal.com/tools/hunter.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hunter.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/hunter.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hunter.json",
      "dns": "hunter.grade.anchorterminal.com",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.hunter.io/v2",
      "packages": [],
      "auth": "mixed",
      "authNotes": "REST takes the key in the `X-API-Key` header (the `?api_key=` query form still works but puts the key in logs). Hosted MCP at mcp.hunter.io uses OAuth for Claude, ChatGPT and Gemini, or the same `X-API-Key` header for other clients. A `test-api-key` returns dummy responses on Domain Search, Email Finder and Email Verifier.",
      "pricing": "freemium",
      "pricingNotes": "Free plan with 50 credits a month and API access. Starter $49 a month ($34 billed yearly, 2,000 credits), Growth $149 ($104 yearly, 10,000 credits), Scale $299 ($209 yearly, 25,000 credits), Enterprise custom. One credit per email found by Email Finder or Domain Search (Bulk Domain Search is 1 credit per 10 emails), 0.5 per verification, nothing when no result comes back, and repeat lookups count once per billing period. Discover (company search) and Email Count are free. An API-only Data Platform sells search and verification credits in bulk, valid 12 months (https://hunter.io/pricing).",
      "priceSummary": "$49 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402 mention in the API docs, MCP docs or pricing (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": 102,
      "popularity": {
        "githubStars": 9,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://hunter.io/api-documentation/v2",
      "llmsTxt": "https://hunter.io/llms.txt",
      "openapi": "https://hunter.io/openapi.json",
      "capabilities": [
        "email.finder",
        "email.verification",
        "lead.search",
        "lead.enrichment",
        "data.company",
        "data.person"
      ],
      "tags": [
        "lead-search",
        "enrichment",
        "email-verification",
        "hosted",
        "freemium",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "webhooks",
        "closed-source"
      ],
      "lastRelease": "2026-09-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 60.9,
        "grade": "C",
        "agentReady": false,
        "rank": 756,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 54,
          "maintenance": 63,
          "payments": 60,
          "reliability": 50,
          "schema": 90,
          "security": 43,
          "transparency": 79
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.",
        "bestFor": "Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.",
        "strengths": [
          "Returns 451 for people who asked not to be processed",
          "Privacy policy names its sources, cites a legitimate interest assessment and DPIA, and hosts in Belgium",
          "Free plan with API and MCP access, no card",
          "Charges only when an email is found or a verification completes, and repeats in a billing period are free",
          "OpenAPI JSON, llms.txt, llms-full.txt, a test key with dummy responses, and a public paid bug bounty"
        ],
        "weaknesses": [
          "Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode",
          "API key accepted in the `api_key` query string",
          "Rate limits answer 403 and quota exhaustion answers 429, with no Retry-After or back-off guidance",
          "No security.txt or certification found",
          "Status page renders client-side and its history couldn't be read"
        ],
        "agentNotes": [
          "Treat 451 as final. The person opted out and retrying won't help",
          "Back off on 403 with a rate-limit message. 429 means the plan's credits are gone",
          "Send the key in `X-API-Key`, never as `?api_key=`",
          "Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409",
          "Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.9
          }
        ],
        "editorialScores": {
          "ergonomics": 54,
          "maintenance": 63,
          "payments": 60,
          "reliability": 50,
          "schema": 90,
          "security": 43,
          "transparency": 71
        },
        "provenanceScore": 86,
        "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://api.hunter.io/v2/domain-search?domain=stripe.com\u0026limit=5\" -H \"X-API-Key: $HUNTER_API_KEY\"",
        "claudeCode": "claude mcp add --transport http hunter https://mcp.hunter.io/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/email.finder",
        "tool": "https://letme.dev/hunter"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Starter plan",
          "unit": "month",
          "usd": 49,
          "note": "2,000 credits. $34 a month billed yearly"
        },
        {
          "item": "Growth plan",
          "unit": "month",
          "usd": 149,
          "note": "10,000 credits. $104 a month billed yearly"
        },
        {
          "item": "Scale plan",
          "unit": "month",
          "usd": 299,
          "note": "25,000 credits. $209 a month billed yearly"
        },
        {
          "item": "Email found or verified",
          "unit": "credit",
          "usd": 0.0245,
          "note": "Starter monthly, $49 for 2,000 credits. One email found is 1 credit, one verification 0.5"
        }
      ],
      "provenance": {
        "legalEntity": "Hunter Web Services, Inc.",
        "domain": "hunter.io",
        "domainRegistered": "2012-08-24",
        "endpointOnVendorDomain": true,
        "terms": "https://hunter.io/terms-of-service",
        "privacy": "https://hunter.io/privacy-policy",
        "statusPage": "https://status.hunter.io",
        "changelog": "https://hunter.io/changelog",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "hunter.io served the pricing page in euros from our location. USD figures match the same numbers and third-party reports"
        ],
        "score": 86
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/hunter.json",
      "live": {
        "slug": "hunter",
        "probe": {
          "target": "https://api.hunter.io/v2",
          "method": "get",
          "lastAt": "2026-11-22T22:37:13.200316159Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 237,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 99.91,
          "p50ms24h": 110,
          "p95ms24h": 180,
          "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": 247
            },
            {
              "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": 238
            },
            {
              "date": "2026-11-20",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-21",
              "probes": 242,
              "ok": 241
            },
            {
              "date": "2026-11-22",
              "probes": 228,
              "ok": 228
            }
          ],
          "outages": [
            {
              "start": "2026-11-19T18:28:54.336025944Z",
              "end": "2026-11-19T18:58:43.408889959Z",
              "note": "HTTP 502 server error"
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.hunter.io",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-22T22:07:55.563540371Z"
        },
        "securityTxt": {
          "url": "https://hunter.io/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-22T16:41:10.300729664Z"
        },
        "llmsTxt": {
          "url": "https://hunter.io/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-22T16:30:47.707218464Z"
        },
        "domain": {
          "domain": "hunter.io",
          "checkedAt": "2026-11-22T16:08:06.103863126Z"
        },
        "pages": [
          {
            "url": "https://hunter.io/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-21T23:48:08.285050127Z",
            "changedAt": "2026-10-08T18:20:54.682281696Z",
            "fingerprint": "646788a7e0c7"
          },
          {
            "url": "https://hunter.io/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-21T23:48:10.40104341Z",
            "changedAt": "2026-11-14T19:04:34.159830022Z",
            "fingerprint": "d0f8816f5f9c"
          },
          {
            "url": "https://hunter.io/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-21T23:48:12.369710683Z",
            "changedAt": "2026-10-08T18:20:58.809513027Z",
            "fingerprint": "c2ea1ffda353"
          },
          {
            "url": "https://hunter.io/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-21T23:48:14.350690254Z",
            "changedAt": "2026-10-08T18:21:00.870589486Z",
            "fingerprint": "8093d765728f"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.hunter.io/mcp",
          "checkedAt": "2026-11-22T05:24:26.548803881Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:45:20.394107637Z"
        },
        "updatedAt": "2026-11-22T22:37:13.200316159Z"
      },
      "streak": {
        "days": 3,
        "from": "2026-11-19",
        "last": {
          "kind": "outage",
          "date": "2026-11-19",
          "what": "HTTP 502 server error",
          "lasted": "29 minutes"
        },
        "best": 42
      }
    },
    "answer": "Leadsets scores 62.9 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 3 of 7 scored categories. Hunter API + MCP leads on reliability, schema \u0026 documentation, 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": 36,
        "category": "ergonomics",
        "leads": "leadsets",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "The hosted MCP exposes about 100 tools (102 by our count of llms-full.txt on 4 November, 96 on 1 October, 107 in the 30 September check) across search, enrichment, leads, lists, sequences and account admin, with no toolsets or read-only subset found. The REST side returns up to 100 rows a call (8 of 25). `limit` up to 100, `offset` up to 10,000, cursor pagination on multi-domain search (18 of 20). Structured errors, but rate limits answer 403 and quota exhaustion 429, which inverts what most clients expect (12 of 20). Repeat lookups within a billing period are free, POST and PUT /v2/leads dedupe by email, and sequence and email writes take an Idempotency-Key, but the MCP's 16 delete and bulk-delete tools carry no annotations we could find (8 of 20, the earlier partial kept). Few required parameters and a test key (8 of 15). 8 + 18 + 12 + 8 + 8 = 54.",
          "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": 54,
          "b": 90
        }
      },
      {
        "by": 32,
        "category": "schema",
        "leads": "hunter",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "OpenAPI 3.0.3 JSON at hunter.io/openapi.json, version 2.0.0, 101 paths and 182 operations on 4 November (25). llms.txt, llms-full.txt and agents.md written for agents (10). Reference pages state purpose and credit rules per endpoint, and llms-full.txt adds usage advice and a when-to-use line per MCP tool (15 of 20). Typed parameters with documented maxima (12 of 15). Examples, a `test-api-key` that returns dummy responses, and an error envelope `{errors: [{id, code, details}]}` including 451 for people who opted out (14 of 15). v2 API and a public dated changelog, with several newer endpoints labelled Beta (14 of 15). 25 + 10 + 15 + 12 + 14 + 14 = 90.",
          "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": 90,
          "b": 58
        }
      },
      {
        "by": 24,
        "category": "security",
        "leads": "leadsets",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "API keys can be created and deleted, and the docs accept the key in a header, as a bearer token or in the `api_key` query string, which puts it in logs (20 less 10). OAuth for the MCP in Claude, ChatGPT, Gemini and Codex, `X-API-Key` elsewhere (15 of 30). No read-only mode. MCP tools can delete leads and lists in bulk, create and delete API keys and start sequences that send email, with no built-in confirmation (3 of 20). Results are emails, names and source URLs with little free text (8 of 15). Account usage via the API, no per-call log found (5 of 15). The 1 October check found hunter.io/security returning 404, but the footer links a Security Policy (last updated 19 October 2023) and a public, paid Bounty Program page with a report form, security@hunter.io, \"We answer all submissions within a few days\" and a hall of fame of paid reports. No security.txt (404 on 4 November), certification or public advisory found (12 of 20, as dropcontact's HackerOne programme and openrouter's private bounty). 15 + 3 + 8 + 5 + 12 = 43.",
          "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": 43,
          "b": 67
        }
      },
      {
        "by": 17,
        "category": "maintenance",
        "leads": "leadsets",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Newest changelog entries are three dated 30 September 2026 (the ChatGPT app, saved searches and AI tool setup paths), 35 days before 4 November. The official Claude Code plugin (hunter-io/claude-plugin) moved from 0.1.0 (18 March) to 0.1.1 on 28 October. The commit that bumps the version only adds an icon, but 0.1.1 is the first version to carry the skill changes made since 0.1.0, including domain-search on 17 August, build-sequences on 14 September and 16 October, and discover on 16 October, so it counts as a full release, 7 days before 4 November (30). Three changelog entries and the plugin release in the 90 days from 6 August (20). Public changelog and support. Issue handling not visible (10 of 15). Not in the official MCP registry. We didn't find current official SDKs; the plugin is MIT on GitHub (0). llms-full.txt tells agents to avoid a deprecated local package, whose repository was last changed on 7 July 2025 (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.",
          "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": 63,
          "b": 80
        }
      },
      {
        "by": 12,
        "category": "transparency",
        "leads": "hunter",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service with terms naming Hunter Web Services, Inc. (last updated 23 May 2024, 15 days' notice of material changes) (15). The privacy policy (updated 13 April 2026, unchanged on 4 November) covers the people in Hunter's index, says profiles come from crawling public pages that allow it and from pattern-generated addresses, cites a legitimate interest assessment and a DPIA, takes removal requests at hunter.io/claim, drops profiles within 3 months of leaving their source page, and links a DPA. The API enforces opt-outs with a 451 (28 of 30). The changelog flagged the June 2026 switch to recipient-based engagement figures as affecting API users, Beta endpoints warn of breaking changes, and no deprecation policy found (8 of 20). Subprocessors at hunter.io/subprocessors and servers on Google Cloud in Belgium (20). 15 + 28 + 8 + 20 = 71.",
          "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": 79,
          "b": 67
        }
      },
      {
        "by": 10,
        "category": "reliability",
        "leads": "hunter",
        "name": "Reliability",
        "reasons": {
          "a": "A status page at status.hunter.io (a Checkly dashboard) exists per the 30 September check, but it renders client-side and both the page and its incidents feed came back empty on 1 October, so components were never confirmed (15 of 20, the earlier partial kept). On 4 November its robots.txt answered with the dashboard's app page, so the host was not read further and no history is readable (5). Per-endpoint limits published, from 5 a second and 50 a minute on Discover to 15 a second and 500 a minute on Domain Search and Email Finder (15). Hitting a rate limit returns 403, while 429 means the plan's usage is spent, and no Retry-After or back-off guidance for either was found. The API reference now documents an Idempotency-Key on sequence and email writes (409 with Retry-After 2 while a request with the same key runs) and calls POST and PUT /v2/leads retry-safe, but with no overload guidance the line stays at the earlier partial (5 of 15). No SLA found (0). Generally available (10). 15 + 5 + 15 + 5 + 0 + 10 = 50.",
          "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": 50,
          "b": 40
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Hunter",
        "b": "Leadsets",
        "name": "Vendor"
      },
      {
        "a": "https://api.hunter.io/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": "102",
        "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": "2026-09-30",
        "b": "2026-11-22",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "2026-11-15",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "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": "yes",
        "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": "9 stars",
        "b": "none",
        "name": "Popularity"
      },
      {
        "a": "3/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Leadsets scores 62.9 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 3 of 7 scored categories. Hunter API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Hunter API + MCP or Leadsets?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Hunter API + MCP and Leadsets need an API key?"
      },
      {
        "answer": "Yes. Hunter API + MCP has a hosted endpoint at https://api.hunter.io/v2 and Leadsets at https://mcp.leadsets.ai.",
        "question": "Can an agent call Hunter API + MCP and Leadsets without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 50 against 40",
          "Schema \u0026 documentation, 90 against 58",
          "Payments \u0026 pricing, 60 against 50",
          "Transparency \u0026 trust, 79 against 67"
        ],
        "also": null,
        "goodFor": "Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.",
        "slug": "hunter",
        "watchFor": "Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 90 against 54",
          "Security \u0026 auth, 67 against 43",
          "Maintenance \u0026 community, 80 against 63"
        ],
        "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": {
      "hunter": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 58.4,
          "fromGrade": "C",
          "to": 60.9,
          "toGrade": "C"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-11-04",
          "delta": 1.8,
          "from": 56.6,
          "fromGrade": "C",
          "to": 58.4,
          "toGrade": "C"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 56.5,
          "fromGrade": "C",
          "to": 56.6,
          "toGrade": "C"
        }
      ],
      "leadsets": null
    },
    "job": {
      "capability": "email.finder",
      "name": "Email finding"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-hunter.json",
        "title": "Apollo API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Clay vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-leadsets.json",
        "title": "Clay vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-hunter.json",
        "title": "Coresignal API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Crustdata API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Dievio vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Enrich Layer API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Explorium AgentSource vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter"
      },
      {
        "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-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-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-hunter.json",
        "title": "Fuse MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Gojiberry vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-hunter"
      },
      {
        "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/hunter-vs-people-data-labs.json",
        "title": "Hunter API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-zoominfo.json",
        "title": "Hunter API + MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-zoominfo"
      },
      {
        "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-hunter.json",
        "title": "Clearbit vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-hunter"
      },
      {
        "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-hunter.json",
        "title": "Databar vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-hunter"
      },
      {
        "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-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-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-hunter.json",
        "title": "FullContact vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.json",
        "title": "FullContact vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-leadmagic.json",
        "title": "Hunter API + MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-lusha.json",
        "title": "Hunter API + MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-prospeo.json",
        "title": "Hunter API + MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-rocketreach.json",
        "title": "Hunter API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce.json",
        "title": "Hunter API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce"
      },
      {
        "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": 10,
        "edge": "hunter",
        "hunter": 50,
        "key": "reliability",
        "leadsets": 40,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 32,
        "edge": "hunter",
        "hunter": 90,
        "key": "schema",
        "leadsets": 58,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 36,
        "edge": "leadsets",
        "hunter": 54,
        "key": "ergonomics",
        "leadsets": 90,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 24,
        "edge": "leadsets",
        "hunter": 43,
        "key": "security",
        "leadsets": 67,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 10,
        "edge": "hunter",
        "hunter": 60,
        "key": "payments",
        "leadsets": 50,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 17,
        "edge": "leadsets",
        "hunter": 63,
        "key": "maintenance",
        "leadsets": 80,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 12,
        "edge": "hunter",
        "hunter": 79,
        "key": "transparency",
        "leadsets": 67,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Leadsets scores 62.9 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 3 of 7 scored categories. Hunter API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. Both do email finding.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "hunter": "Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.",
      "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/hunter-vs-leadsets",
    "json": "https://www.anchorterminal.com/compare/hunter-vs-leadsets.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/hunter-vs-leadsets.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/hunter-vs-leadsets.min.md"
  },
  "markdown": "Leadsets scores 62.9 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 3 of 7 scored categories. Hunter API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. Both do email finding.\n\n- Hunter API + MCP: grade C, 60.9/100, rank #756 of 1571. Markdown https://www.anchorterminal.com/tools/hunter.md · JSON https://www.anchorterminal.com/api/v1/tools/hunter.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### Hunter API + MCP (C)\n\nGood for: Finding and verifying work emails from a domain or a name, where GDPR handling of the people looked up matters.\n\nAhead on:\n- Reliability, 50 against 40\n- Schema \u0026 documentation, 90 against 58\n- Payments \u0026 pricing, 60 against 50\n- Transparency \u0026 trust, 79 against 67\n\nWatch for: Hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode\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 54\n- Security \u0026 auth, 67 against 43\n- Maintenance \u0026 community, 80 against 63\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### Agent ergonomics: Leadsets +36\n\n- Hunter API + MCP (54): The hosted MCP exposes about 100 tools (102 by our count of llms-full.txt on 4 November, 96 on 1 October, 107 in the 30 September check) across search, enrichment, leads, lists, sequences and account admin, with no toolsets or read-only subset found. The REST side returns up to 100 rows a call (8 of 25). `limit` up to 100, `offset` up to 10,000, cursor pagination on multi-domain search (18 of 20). Structured errors, but rate limits answer 403 and quota exhaustion 429, which inverts what most clients expect (12 of 20). Repeat lookups within a billing period are free, POST and PUT /v2/leads dedupe by email, and sequence and email writes take an Idempotency-Key, but the MCP's 16 delete and bulk-delete tools carry no annotations we could find (8 of 20, the earlier partial kept). Few required parameters and a test key (8 of 15). 8 + 18 + 12 + 8 + 8 = 54.\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: Hunter API + MCP +32\n\n- Hunter API + MCP (90): OpenAPI 3.0.3 JSON at hunter.io/openapi.json, version 2.0.0, 101 paths and 182 operations on 4 November (25). llms.txt, llms-full.txt and agents.md written for agents (10). Reference pages state purpose and credit rules per endpoint, and llms-full.txt adds usage advice and a when-to-use line per MCP tool (15 of 20). Typed parameters with documented maxima (12 of 15). Examples, a `test-api-key` that returns dummy responses, and an error envelope `{errors: [{id, code, details}]}` including 451 for people who opted out (14 of 15). v2 API and a public dated changelog, with several newer endpoints labelled Beta (14 of 15). 25 + 10 + 15 + 12 + 14 + 14 = 90.\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 +24\n\n- Hunter API + MCP (43): API keys can be created and deleted, and the docs accept the key in a header, as a bearer token or in the `api_key` query string, which puts it in logs (20 less 10). OAuth for the MCP in Claude, ChatGPT, Gemini and Codex, `X-API-Key` elsewhere (15 of 30). No read-only mode. MCP tools can delete leads and lists in bulk, create and delete API keys and start sequences that send email, with no built-in confirmation (3 of 20). Results are emails, names and source URLs with little free text (8 of 15). Account usage via the API, no per-call log found (5 of 15). The 1 October check found hunter.io/security returning 404, but the footer links a Security Policy (last updated 19 October 2023) and a public, paid Bounty Program page with a report form, security@hunter.io, \"We answer all submissions within a few days\" and a hall of fame of paid reports. No security.txt (404 on 4 November), certification or public advisory found (12 of 20, as dropcontact's HackerOne programme and openrouter's private bounty). 15 + 3 + 8 + 5 + 12 = 43.\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### Maintenance \u0026 community: Leadsets +17\n\n- Hunter API + MCP (63): Newest changelog entries are three dated 30 September 2026 (the ChatGPT app, saved searches and AI tool setup paths), 35 days before 4 November. The official Claude Code plugin (hunter-io/claude-plugin) moved from 0.1.0 (18 March) to 0.1.1 on 28 October. The commit that bumps the version only adds an icon, but 0.1.1 is the first version to carry the skill changes made since 0.1.0, including domain-search on 17 August, build-sequences on 14 September and 16 October, and discover on 16 October, so it counts as a full release, 7 days before 4 November (30). Three changelog entries and the plugin release in the 90 days from 6 August (20). Public changelog and support. Issue handling not visible (10 of 15). Not in the official MCP registry. We didn't find current official SDKs; the plugin is MIT on GitHub (0). llms-full.txt tells agents to avoid a deprecated local package, whose repository was last changed on 7 July 2025 (3 of 10). 30 + 20 + 10 + 0 + 3 = 63.\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### Transparency \u0026 trust: Hunter API + MCP +12\n\n- Hunter API + MCP (79): Closed service with terms naming Hunter Web Services, Inc. (last updated 23 May 2024, 15 days' notice of material changes) (15). The privacy policy (updated 13 April 2026, unchanged on 4 November) covers the people in Hunter's index, says profiles come from crawling public pages that allow it and from pattern-generated addresses, cites a legitimate interest assessment and a DPIA, takes removal requests at hunter.io/claim, drops profiles within 3 months of leaving their source page, and links a DPA. The API enforces opt-outs with a 451 (28 of 30). The changelog flagged the June 2026 switch to recipient-based engagement figures as affecting API users, Beta endpoints warn of breaking changes, and no deprecation policy found (8 of 20). Subprocessors at hunter.io/subprocessors and servers on Google Cloud in Belgium (20). 15 + 28 + 8 + 20 = 71.\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### Reliability: Hunter API + MCP +10\n\n- Hunter API + MCP (50): A status page at status.hunter.io (a Checkly dashboard) exists per the 30 September check, but it renders client-side and both the page and its incidents feed came back empty on 1 October, so components were never confirmed (15 of 20, the earlier partial kept). On 4 November its robots.txt answered with the dashboard's app page, so the host was not read further and no history is readable (5). Per-endpoint limits published, from 5 a second and 50 a minute on Discover to 15 a second and 500 a minute on Domain Search and Email Finder (15). Hitting a rate limit returns 403, while 429 means the plan's usage is spent, and no Retry-After or back-off guidance for either was found. The API reference now documents an Idempotency-Key on sequence and email writes (409 with Retry-After 2 while a request with the same key runs) and calls POST and PUT /v2/leads retry-safe, but with no overload guidance the line stays at the earlier partial (5 of 15). No SLA found (0). Generally available (10). 15 + 5 + 15 + 5 + 0 + 10 = 50.\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## Score by category\n\n| Category | Weight | Hunter API + MCP | Leadsets | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 50 | 40 | Hunter API + MCP +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 90 | 58 | Hunter API + MCP +32 |\n| Agent ergonomics | 13% | 54 | 90 | Leadsets +36 |\n| Security \u0026 auth | 14% | 43 | 67 | Leadsets +24 |\n| Payments \u0026 pricing | 10% | 60 | 50 | Hunter API + MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 63 | 80 | Leadsets +17 |\n| Transparency \u0026 trust | 7% | 79 | 67 | Hunter API + MCP +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.9 · C** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Hunter API + MCP | Leadsets |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hunter | Leadsets |\n| Hosted endpoint | `https://api.hunter.io/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 | 102 | 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 | 2026-09-30 | 2026-11-22 |\n| Terms last updated | no date given | 2026-11-15 |\n| Privacy policy last updated | no date given | 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 | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 9 stars | none |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Hunter API + MCP\n\n- +2.5 on 13 November 2026: checklist\n- +1.8 on 4 November 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n### Leadsets\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Hunter API + MCP.** Finds and verifies work emails, returns 451 for people who asked not to be processed, and runs a public paid bug bounty. Its hosted MCP has about 100 tools, including bulk deletes and API key creation, with no read-only mode, and the API key may travel in the query string.\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### Hunter API + MCP\n\n1. Treat 451 as final. The person opted out and retrying won't help\n2. Back off on 403 with a rate-limit message. 429 means the plan's credits are gone\n3. Send the key in `X-API-Key`, never as `?api_key=`\n4. Send an Idempotency-Key when creating sequences or sending email, and retry with the same key after a 409\n5. Use the hosted MCP at mcp.hunter.io/mcp, not the deprecated local npm package\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, Hunter API + MCP or Leadsets?\n\nLeadsets scores 62.9 (B) on agent readiness against Hunter API + MCP's 60.9 (C), and leads in 3 of 7 scored categories. Hunter API + MCP leads on reliability, schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do Hunter 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 Hunter API + MCP and Leadsets without installing anything?\n\nYes. Hunter API + MCP has a hosted endpoint at https://api.hunter.io/v2 and Leadsets at https://mcp.leadsets.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hunter-vs-leadsets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hunter-vs-leadsets.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hunter\", \"b\": \"leadsets\"}`. From a terminal: `anchor compare hunter leadsets`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hunter.json and https://www.anchorterminal.com/api/v1/tools/leadsets.json\n\n## Other comparisons with Hunter API + MCP or Leadsets\n\n- [Apollo API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/apollo-vs-hunter.md)\n- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)\n- [Clay vs Hunter API + MCP](https://www.anchorterminal.com/compare/clay-vs-hunter.md)\n- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)\n- [Coresignal API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-hunter.md)\n- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)\n- [Crustdata API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-hunter.md)\n- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)\n- [Dievio vs Hunter API + MCP](https://www.anchorterminal.com/compare/dievio-vs-hunter.md)\n- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)\n- [Enrich Layer API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-hunter.md)\n- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)\n- [Explorium AgentSource vs Hunter API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-hunter.md)\n- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.md)\n- [FullEnrich API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-hunter.md)\n- [FullEnrich API + MCP vs Leadsets](https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.md)\n- [Fuse MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-hunter.md)\n- [Fuse MCP vs Leadsets](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.md)\n- [Gojiberry vs Hunter API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-hunter.md)\n- [Gojiberry vs Leadsets](https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.md)\n- [Hunter API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/hunter-vs-people-data-labs.md)\n- [Hunter API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-zoominfo.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 Hunter API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-hunter.md)\n- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)\n- [Databar vs Hunter API + MCP](https://www.anchorterminal.com/compare/databar-vs-hunter.md)\n- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)\n- [Dropcontact API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-hunter.md)\n- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md)\n- [FullContact vs Hunter API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-hunter.md)\n- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md)\n- [Hunter API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/hunter-vs-leadmagic.md)\n- [Hunter API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/hunter-vs-lusha.md)\n- [Hunter API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-prospeo.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n- [Hunter API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/hunter-vs-rocketreach.md)\n- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.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": "Hunter API + MCP vs Leadsets",
        "url": ""
      }
    ],
    "description": "Leadsets scores 62.9 (B) to Hunter's 60.9 (C) for email finding. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Hunter API + MCP C 60.9",
      "Leadsets B 62.9",
      "scores"
    ],
    "h1": "Hunter API + MCP vs Leadsets",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/hunter-vs-leadsets",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Hunter vs Leadsets for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-22",
    "url": "https://www.anchorterminal.com/compare/hunter-vs-leadsets"
  },
  "tokens": {
    "markdown": 5650,
    "slim": 1130
  },
  "version": 1
}
