{
  "data": {
    "a": {
      "slug": "coresignal",
      "name": "Coresignal API + MCP",
      "vendor": "Coresignal",
      "vendorUrl": "https://coresignal.com",
      "company": "coresignal.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Company, employee and job posting data collected from the public web, queried with filters or Elasticsearch DSL and pulled by ID, with a real-time employee lookup, profile-change webhooks and a natural-language Agentic Search API.",
      "url": "https://www.anchorterminal.com/tools/coresignal",
      "markdownUrl": "https://www.anchorterminal.com/tools/coresignal.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/coresignal.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/coresignal.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/coresignal.json",
      "dns": "coresignal.grade.anchorterminal.com",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.coresignal.com/cdapi",
      "packages": [],
      "auth": "mixed",
      "authNotes": "`apikey` header on REST. Hosted MCP v2 at mcp.coresignal.com uses OAuth 2.1 through the Coresignal dashboard and looks up the team's key server-side, so no key sits in the client.",
      "pricing": "paid",
      "pricingNotes": "7-day free trial with 2,000 credits, once per company email domain. Monthly plans Mini $49 (2,500 credits), Starter $199 (12,000), Pro $499 (35,000), Growth $1,000 (150,000), Premium $1,500 (1,000,000), Scale $3,000 (4,000,000), Elite $5,000 (10,000,000). Annual plans are 10 per cent off from Starter up. Search is free. Collecting a record costs 1 credit for jobs and posts, 10 for Historical Headcount, 12 for Real-time Employee, and 10 to 20 for a multi-source company or employee record by bundle (core 10, full record 20). Agentic Search costs 20 (fast) or 100 (reasoning) (https://docs.coresignal.com/pricing/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": 5,
      "popularity": {
        "githubStars": 2,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.coresignal.com",
      "llmsTxt": "https://docs.coresignal.com/llms.txt",
      "openapi": "https://api.coresignal.com/cdapi/openapi.json",
      "registryName": "com.coresignal/mcp",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company",
        "data.person"
      ],
      "tags": [
        "lead-search",
        "enrichment",
        "hosted",
        "card-required",
        "mcp",
        "llms-txt",
        "openapi",
        "webhooks",
        "async-jobs",
        "closed-source"
      ],
      "lastRelease": "2026-11-01",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.1,
        "grade": "B",
        "agentReady": false,
        "rank": 701,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 82,
          "payments": 30,
          "reliability": 60,
          "schema": 86,
          "security": 58,
          "transparency": 71
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": -3,
        "negativeNotes": [
          "-3. A published behaviour changed for existing clients, announced the day it took effect. The 7 October 2026 release notes say `primary_professional_email`, `primary_professional_email_status` and `professional_emails_collection` \"are no longer available in the Multi-source Employee API\", with no earlier notice in the August or September notes. They moved to the Contact Enrichment API, added on 15 October. The 26 August 2026 raise of the Agentic Search `threshold` default from 0.92 to 0.97, announced that day, is the same kind and folds into this term. https://docs.coresignal.com/release-notes/october-2026"
        ],
        "verdict": "Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.",
        "bestFor": "Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.",
        "strengths": [
          "Search is free, and credits are only taken on collect or enrich calls that return 200",
          "Every plan price and per-endpoint credit cost is public, with multi-source bundles from 10 credits a record",
          "Hosted MCP with 5 tools, OAuth 2.1 and a confirmation step before large pulls",
          "35 dated release-note entries from 10 August to 1 November, with scheduled breaking changes flagged ahead",
          "Privacy policy covers people in the datasets, with a five-year retention cap"
        ],
        "weaknesses": [
          "Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted",
          "Three work-email fields left the Multi-source Employee API on 7 October, the day the removal was announced",
          "Main search takes Elasticsearch DSL, a free-form JSON body",
          "7-day trial with a card per the 30 September check, and no free tier",
          "Terms name Deeptrace Inc. while the privacy policy names Binary House LLC"
        ],
        "agentNotes": [
          "Search for IDs first (free), then collect only the records you need",
          "Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full",
          "Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026",
          "Treat a 402 as out of credits, not a transient error",
          "Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.1
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 82,
          "payments": 30,
          "reliability": 60,
          "schema": 86,
          "security": 58,
          "transparency": 55
        },
        "provenanceScore": 87,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-02",
            "maintenance": "2026-11-02",
            "payments": "2026-11-02",
            "reliability": "2026-11-02",
            "schema": "2026-11-02",
            "security": "2026-11-02",
            "transparency": "2026-11-02"
          },
          "last": "2026-11-02",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl \"https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?enrich_query=stripe.com\" -H \"apikey: $CORESIGNAL_API_KEY\"",
        "claudeCode": "claude mcp add --transport http coresignal https://mcp.coresignal.com/mcp/v2"
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/coresignal"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Mini plan",
          "unit": "month",
          "usd": 49,
          "note": "2,500 credits"
        },
        {
          "item": "Starter plan",
          "unit": "month",
          "usd": 199,
          "note": "12,000 credits"
        },
        {
          "item": "Pro plan",
          "unit": "month",
          "usd": 499,
          "note": "35,000 credits, adds contact enrichment"
        },
        {
          "item": "Growth plan",
          "unit": "month",
          "usd": 1000,
          "note": "150,000 credits"
        },
        {
          "item": "Multi-source company or employee record",
          "unit": "record",
          "usd": 0.285,
          "note": "20 credits at Pro plan rates ($499 for 35,000 credits)"
        }
      ],
      "provenance": {
        "legalEntity": "Deeptrace Inc.",
        "domain": "coresignal.com",
        "domainRegistered": "2014-12-16",
        "endpointOnVendorDomain": true,
        "terms": "https://coresignal.com/terms-and-conditions/",
        "privacy": "https://coresignal.com/privacy-policy/",
        "statusPage": "https://status.coresignal.com",
        "changelog": "https://docs.coresignal.com/release-notes",
        "securityTxt": "none",
        "checked": "2026-11-02",
        "notes": [
          "The terms and conditions name Deeptrace Inc. (Lewes, Delaware) as the contracting company for Coresignal",
          "The privacy policy, updated 25 August 2026, names Binary House LLC as the data controller and lists Deeptrace Inc. as a processor"
        ],
        "score": 87
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/coresignal.json",
      "live": {
        "slug": "coresignal",
        "probe": {
          "target": "https://api.coresignal.com/cdapi",
          "method": "get",
          "lastAt": "2026-11-22T22:36:58.778843513Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 163,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 99.99,
          "p50ms24h": 91,
          "p95ms24h": 182,
          "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": 249
            },
            {
              "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
            }
          ],
          "outages": [
            {
              "start": "2026-10-05T05:02:39.72752943Z",
              "end": "2026-10-05T06:45:00.818712073Z",
              "note": "HTTP 503 server error"
            }
          ],
          "since": "2026-10-05T05:02:39.72752943Z"
        },
        "vendorStatus": {
          "page": "https://status.coresignal.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-22T22:07:29.890692457Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.coresignal/mcp",
            "version": "2.0.0",
            "seenAt": "2026-11-22T00:00:22.236652523Z"
          }
        ],
        "securityTxt": {
          "url": "https://coresignal.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-22T16:41:48.486043073Z"
        },
        "llmsTxt": {
          "url": "https://docs.coresignal.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-22T16:30:07.786069674Z"
        },
        "domain": {
          "domain": "coresignal.com",
          "registered": "2014-12-16",
          "source": "https://rdap.verisign.com/com/v1/domain/coresignal.com",
          "checkedAt": "2026-11-22T15:50:48.684288528Z"
        },
        "pages": [
          {
            "url": "https://docs.coresignal.com/release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-21T23:42:47.813929794Z",
            "changedAt": "2026-11-20T23:01:33.861968435Z",
            "fingerprint": "86a5a4f96da5"
          },
          {
            "url": "https://docs.coresignal.com/integrations/coresignal-mcp",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-21T23:42:42.836736258Z",
            "changedAt": "2026-11-18T21:39:39.428033547Z",
            "fingerprint": "2e6d7cecaec6"
          },
          {
            "url": "https://docs.coresignal.com/release-notes/october-2026",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-21T23:42:49.517530864Z",
            "changedAt": "2026-11-19T22:20:39.966369209Z",
            "fingerprint": "1d1004a0fb2d"
          },
          {
            "url": "https://coresignal.com/pricing/",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-02T07:10:43.675195323Z",
            "changedAt": "2026-10-22T01:12:24.083375791Z",
            "fingerprint": "950f77b775d2"
          },
          {
            "url": "https://docs.coresignal.com/pricing/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-21T23:42:45.281016658Z",
            "changedAt": "2026-11-18T21:39:41.980874409Z",
            "fingerprint": "6de37751e403"
          },
          {
            "url": "https://coresignal.com/privacy-policy/",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-21T23:39:03.869766072Z",
            "changedAt": "2026-11-19T22:16:54.961014858Z",
            "fingerprint": "6c016659f243"
          },
          {
            "url": "https://coresignal.com/terms-and-conditions/",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-21T23:39:05.915474382Z",
            "changedAt": "2026-11-19T22:16:57.107466936Z",
            "fingerprint": "4a0ae16e2e66"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.coresignal.com/mcp/v2",
          "checkedAt": "2026-11-22T05:22:27.711151375Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:43:27.078662654Z"
        },
        "updatedAt": "2026-11-22T22:36:58.778843513Z"
      },
      "streak": {
        "days": 19,
        "from": "2026-11-03",
        "last": {
          "kind": "shutdown",
          "date": "2026-11-03",
          "what": "The original MCP endpoint `https://mcp.coresignal.com/mcp` is deprecated. Move to `https://mcp.coresignal.com/mcp/v2` (the docs give 3 November in one place and 1 November in another)",
          "source": "https://docs.coresignal.com/integrations/coresignal-mcp"
        },
        "next": {
          "kind": "breaking",
          "date": "2026-12-01",
          "what": "The Base Company `funding_rounds` struct is removed after the 1 December 2026 data dumps. Use `funding_rounds_legacy`",
          "source": "https://docs.coresignal.com/release-notes/october-2026"
        },
        "best": 29
      }
    },
    "answer": "Leadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema \u0026 documentation.",
    "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": 28,
        "category": "schema",
        "leads": "coresignal",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "OpenAPI 3.1 file at api.coresignal.com/cdapi/openapi.json, 56 paths and 247 schemas on 2 November, with `apikey` header auth (25). llms.txt index of 195 pages and Markdown copies of every docs page (10). Endpoint pages and the MCP tool list state purpose and credit cost per call (15 of 20). Simple filters are typed, but the main search takes Elasticsearch DSL, a free-form JSON body (9 of 15). Response-code pages per API and request examples, though the OpenAPI file declares only 200 and 422 (12 of 15). v2 API paths and monthly release notes with dated entries and flagged breaking changes (15).",
          "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": 86,
          "b": 58
        }
      },
      {
        "by": 20,
        "category": "reliability",
        "leads": "coresignal",
        "name": "Reliability",
        "reasons": {
          "a": "Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, \"RTAPI requests failing\" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI \"Down for 4 hours and 20 minutes\" on 24 October and \"Down for 8 hours and 19 minutes\" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.",
          "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": 60,
          "b": 40
        }
      },
      {
        "by": 20,
        "category": "payments",
        "leads": "leadsets",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.",
          "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": 30,
          "b": 50
        }
      },
      {
        "by": 17,
        "category": "ergonomics",
        "leads": "leadsets",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "The hosted MCP has 5 tools, and large results go to a file read back in pages with `artifact_read` rather than into the context (23 of 25). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).",
          "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": 73,
          "b": 90
        }
      },
      {
        "by": 9,
        "category": "security",
        "leads": "leadsets",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "`apikey` header on REST. MCP v2 signs in with OAuth 2.1 through the dashboard and keeps the key server-side. We found no key scopes (22 of 30). Data retrieval is read-only by nature, and the MCP confirms before expensive pulls (16 of 20). Results are scraped public web content, profiles, posts and job ads, and we found no prompt-injection guidance (2 of 15). Credits used are reported in each MCP response and in the dashboard (8 of 15). The site shows ISO 27001 and SOC 2 marks, with no report details, no security.txt (coresignal.com/.well-known/security.txt answers 404 on 2 November) and no bug bounty found (10 of 20).",
          "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": 58,
          "b": 67
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Coresignal",
        "b": "Leadsets",
        "name": "Vendor"
      },
      {
        "a": "https://api.coresignal.com/cdapi",
        "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": "5",
        "b": "8",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "com.coresignal/mcp",
        "b": "io.github.leadsets/leadsets",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-01",
        "b": "2026-11-22",
        "name": "Last release"
      },
      {
        "a": "2022-02-21",
        "b": "2026-11-15",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-25",
        "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": "2 stars",
        "b": "none",
        "name": "Popularity"
      },
      {
        "a": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Leadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema \u0026 documentation.",
        "question": "Which is better for AI agents, Coresignal API + MCP or Leadsets?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Coresignal API + MCP and Leadsets need an API key?"
      },
      {
        "answer": "Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Leadsets at https://mcp.leadsets.ai.",
        "question": "Can an agent call Coresignal API + MCP and Leadsets without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 60 against 40",
          "Schema \u0026 documentation, 86 against 58"
        ],
        "also": null,
        "goodFor": "Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.",
        "slug": "coresignal",
        "watchFor": "Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 90 against 73",
          "Security \u0026 auth, 67 against 58",
          "Payments \u0026 pricing, 50 against 30"
        ],
        "also": [
          "Free to start without a card",
          "No incidents deducted, where Coresignal API + MCP loses 3 points for them"
        ],
        "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": {
      "coresignal": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 60.9,
          "fromGrade": "C",
          "to": 62.1,
          "toGrade": "B"
        },
        {
          "causes": [
            "evidence",
            "event"
          ],
          "date": "2026-11-02",
          "delta": -2,
          "from": 62.9,
          "fromGrade": "B",
          "to": 60.9,
          "toGrade": "C"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-08",
          "delta": -0.2,
          "from": 63.1,
          "fromGrade": "B",
          "to": 62.9,
          "toGrade": "B"
        }
      ],
      "leadsets": null
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-coresignal.json",
        "title": "Apollo API + MCP vs Coresignal API + MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-coresignal"
      },
      {
        "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-coresignal.json",
        "title": "Clay vs Coresignal API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-coresignal"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-leadsets.json",
        "title": "Clay vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-crustdata.json",
        "title": "Coresignal API + MCP vs Crustdata API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-crustdata"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-databar.json",
        "title": "Coresignal API + MCP vs Databar",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-databar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-dievio.json",
        "title": "Coresignal API + MCP vs Dievio",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-dievio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.json",
        "title": "Coresignal API + MCP vs Enrich Layer API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.json",
        "title": "Coresignal API + MCP vs Explorium AgentSource",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.json",
        "title": "Coresignal API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.json",
        "title": "Coresignal API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.json",
        "title": "Coresignal API + MCP vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-gojiberry"
      },
      {
        "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-leadmagic.json",
        "title": "Coresignal API + MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-lusha.json",
        "title": "Coresignal API + MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.json",
        "title": "Coresignal API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-prospeo.json",
        "title": "Coresignal API + MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
        "title": "Coresignal API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-rocketreach.json",
        "title": "Coresignal API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.json",
        "title": "Coresignal API + MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-zoominfo"
      },
      {
        "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/clearbit-vs-coresignal.json",
        "title": "Clearbit vs Coresignal API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal"
      },
      {
        "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/coresignal-vs-fullcontact.json",
        "title": "Coresignal API + MCP vs FullContact",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-fullcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.json",
        "title": "Coresignal API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce"
      },
      {
        "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-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-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": 20,
        "coresignal": 60,
        "edge": "coresignal",
        "key": "reliability",
        "leadsets": 40,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 28,
        "coresignal": 86,
        "edge": "coresignal",
        "key": "schema",
        "leadsets": 58,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 17,
        "coresignal": 73,
        "edge": "leadsets",
        "key": "ergonomics",
        "leadsets": 90,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 9,
        "coresignal": 58,
        "edge": "leadsets",
        "key": "security",
        "leadsets": 67,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 20,
        "coresignal": 30,
        "edge": "leadsets",
        "key": "payments",
        "leadsets": 50,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "coresignal": 82,
        "edge": "coresignal",
        "key": "maintenance",
        "leadsets": 80,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 4,
        "coresignal": 71,
        "edge": "coresignal",
        "key": "transparency",
        "leadsets": 67,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Leadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema \u0026 documentation. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "coresignal": "Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.",
      "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/coresignal-vs-leadsets",
    "json": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets.min.md"
  },
  "markdown": "Leadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema \u0026 documentation. Both do lead search.\n\n- Coresignal API + MCP: grade B, 62.1/100, rank #701 of 1571. Markdown https://www.anchorterminal.com/tools/coresignal.md · JSON https://www.anchorterminal.com/api/v1/tools/coresignal.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### Coresignal API + MCP (B)\n\nGood for: Company and workforce research, headcount history and hiring signals at volume, and for pipelines that want raw records.\n\nAhead on:\n- Reliability, 60 against 40\n- Schema \u0026 documentation, 86 against 58\n\nWatch for: Status page shows CDAPI down 4 hours 20 minutes on 24 October and 8 hours 19 minutes on 25 October, with no incident posted\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 73\n- Security \u0026 auth, 67 against 58\n- Payments \u0026 pricing, 50 against 30\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Coresignal API + MCP loses 3 points for them\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### Schema \u0026 documentation: Coresignal API + MCP +28\n\n- Coresignal API + MCP (86): OpenAPI 3.1 file at api.coresignal.com/cdapi/openapi.json, 56 paths and 247 schemas on 2 November, with `apikey` header auth (25). llms.txt index of 195 pages and Markdown copies of every docs page (10). Endpoint pages and the MCP tool list state purpose and credit cost per call (15 of 20). Simple filters are typed, but the main search takes Elasticsearch DSL, a free-form JSON body (9 of 15). Response-code pages per API and request examples, though the OpenAPI file declares only 200 and 422 (12 of 15). v2 API paths and monthly release notes with dated entries and flagged breaking changes (15).\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### Reliability: Coresignal API + MCP +20\n\n- Coresignal API + MCP (60): Better Stack status page at status.coresignal.com with CDAPI, RTAPI and Self-service components (20). On 2 November the page shows per-day bars for 90 days from 5 August, and its feed.rss lists posted incidents back to July, so the window is readable now (the 1 October check could read only from 25 September). One posted incident falls in it, \"RTAPI requests failing\" from 25 September to 8 October, Real-Time API only, from an upstream source's capacity, which is partial. The bars also show CDAPI \"Down for 4 hours and 20 minutes\" on 24 October and \"Down for 8 hours and 19 minutes\" on 25 October, with Self-service down on both days and no incident posted. That is the core Data API down for more than an hour, read as one major (10). Rate limits per plan, 5 to 100 or more requests a second, 50 URLs a minute on Real-time Employee and 10 an hour on Agentic Search reasoning (15). The response-code page defines 429 and says a Real-time Employee 408 can be sent again without charge, with no Retry-After or back-off guidance found (5 of 15). No SLA found (0). The surfaces agents use are generally available (10). 20 + 10 + 15 + 5 + 0 + 10 = 60.\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### Payments \u0026 pricing: Leadsets +20\n\n- Coresignal API + MCP (30): No x402, MPP or L402 (0). Every plan price, credit allowance and per-endpoint credit cost is public, and only successful collect or enrich calls are charged (20). 7-day trial with 2,000 credits once per company email domain. The trial docs don't mention a card, and the card requirement rests on the 30 September check (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\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### Agent ergonomics: Leadsets +17\n\n- Coresignal API + MCP (73): The hosted MCP has 5 tools, and large results go to a file read back in pages with `artifact_read` rather than into the context (23 of 25). Search filters and pagination, with search itself free (18 of 20). 402 when credits run out and per-API response codes (14 of 20). The API is read-only apart from webhook subscriptions, credits are only taken on a 200, and MCP v2 pauses to confirm record count and credit cost before large pulls (12 of 20). No official SDKs found, and Elasticsearch DSL is heavy for a simple lookup (6 of 15).\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### Security \u0026 auth: Leadsets +9\n\n- Coresignal API + MCP (58): `apikey` header on REST. MCP v2 signs in with OAuth 2.1 through the dashboard and keeps the key server-side. We found no key scopes (22 of 30). Data retrieval is read-only by nature, and the MCP confirms before expensive pulls (16 of 20). Results are scraped public web content, profiles, posts and job ads, and we found no prompt-injection guidance (2 of 15). Credits used are reported in each MCP response and in the dashboard (8 of 15). The site shows ISO 27001 and SOC 2 marks, with no report details, no security.txt (coresignal.com/.well-known/security.txt answers 404 on 2 November) and no bug bounty found (10 of 20).\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## Score by category\n\n| Category | Weight | Coresignal API + MCP | Leadsets | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 60 | 40 | Coresignal API + MCP +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 86 | 58 | Coresignal API + MCP +28 |\n| Agent ergonomics | 13% | 73 | 90 | Leadsets +17 |\n| Security \u0026 auth | 14% | 58 | 67 | Leadsets +9 |\n| Payments \u0026 pricing | 10% | 30 | 50 | Leadsets +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 82 | 80 | Coresignal API + MCP +2 |\n| Transparency \u0026 trust | 7% | 71 | 67 | Coresignal API + MCP +4 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **62.1 · B** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Coresignal API + MCP | Leadsets |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Coresignal | Leadsets |\n| Hosted endpoint | `https://api.coresignal.com/cdapi` | `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 | 5 | 8 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.coresignal/mcp` | `io.github.leadsets/leadsets` |\n| Last release | 2026-11-01 | 2026-11-22 |\n| Terms last updated | 2022-02-21 | 2026-11-15 |\n| Privacy policy last updated | 2026-08-25 | 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| Popularity | 2 stars | none |\n| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Coresignal API + MCP\n\n- +1.2 on 13 November 2026 (C to B): checklist\n- -2.0 on 2 November 2026 (B to C): new evidence, negative event\n- -0.2 on 8 October 2026: checklist\n\n### Leadsets\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Coresignal API + MCP.** Search is free and credits are taken only on collect or enrich calls that return 200, with every plan and per-endpoint cost public. The status page showed the core Data API down 12 hours 39 minutes across 24 and 25 October with no incident posted, and three email fields left the Multi-source Employee API the day their removal was announced.\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### Coresignal API + MCP\n\n1. Search for IDs first (free), then collect only the records you need\n2. Request only the bundles you need. A multi-source record costs 10 credits for the core bundle and 20 in full\n3. Use MCP v2 at /mcp/v2. The older /mcp endpoint is deprecated in November 2026\n4. Treat a 402 as out of credits, not a transient error\n5. Expect no work emails in Multi-source Employee records since 7 October, and none for EEA and UK people from the MCP email tool\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, Coresignal API + MCP or Leadsets?\n\nLeadsets and Coresignal API + MCP score within a point of each other on agent readiness, 62.9 (B) and 62.1 (B). Coresignal API + MCP leads on reliability and schema \u0026 documentation.\n\n### Do Coresignal 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 Coresignal API + MCP and Leadsets without installing anything?\n\nYes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Leadsets at https://mcp.leadsets.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/coresignal-vs-leadsets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coresignal-vs-leadsets.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"coresignal\", \"b\": \"leadsets\"}`. From a terminal: `anchor compare coresignal leadsets`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coresignal.json and https://www.anchorterminal.com/api/v1/tools/leadsets.json\n\n## Other comparisons with Coresignal API + MCP or Leadsets\n\n- [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-vs-coresignal.md)\n- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)\n- [Clay vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clay-vs-coresignal.md)\n- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)\n- [Coresignal API + MCP vs Crustdata API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-crustdata.md)\n- [Coresignal API + MCP vs Databar](https://www.anchorterminal.com/compare/coresignal-vs-databar.md)\n- [Coresignal API + MCP vs Dievio](https://www.anchorterminal.com/compare/coresignal-vs-dievio.md)\n- [Coresignal API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-enrich-layer.md)\n- [Coresignal API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/coresignal-vs-explorium-agentsource.md)\n- [Coresignal API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-fullenrich.md)\n- [Coresignal API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/coresignal-vs-fuse-mcp.md)\n- [Coresignal API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/coresignal-vs-gojiberry.md)\n- [Coresignal API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-hunter.md)\n- [Coresignal API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-leadmagic.md)\n- [Coresignal API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-lusha.md)\n- [Coresignal API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.md)\n- [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)\n- [Coresignal API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/coresignal-vs-rocketreach.md)\n- [Coresignal API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-zoominfo.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- [Clearbit vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-coresignal.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- [Coresignal API + MCP vs FullContact](https://www.anchorterminal.com/compare/coresignal-vs-fullcontact.md)\n- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)\n- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)\n- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.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": "Coresignal API + MCP vs Leadsets",
        "url": ""
      }
    ],
    "description": "Leadsets and Coresignal score within a point of each other for lead search, 62.9 and 62.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Coresignal API + MCP B 62.1",
      "Leadsets B 62.9",
      "scores"
    ],
    "h1": "Coresignal API + MCP vs Leadsets",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/coresignal-vs-leadsets",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Coresignal vs Leadsets for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-22",
    "url": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets"
  },
  "tokens": {
    "markdown": 5000,
    "slim": 1030
  },
  "version": 1
}
