{
  "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",
      "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": 696,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 7,
        "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-18T21:50:42.156379588Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 103,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 99.99,
          "p50ms24h": 80,
          "p95ms24h": 212,
          "samples24h": 242,
          "samples30d": 7829,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "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": 220,
              "ok": 220
            }
          ],
          "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-18T18:52:20.194861972Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.coresignal/mcp",
            "version": "2.0.0",
            "seenAt": "2026-11-17T22:21:47.712728033Z"
          }
        ],
        "securityTxt": {
          "url": "https://coresignal.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:30:15.119555076Z"
        },
        "llmsTxt": {
          "url": "https://docs.coresignal.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:01.570817837Z"
        },
        "domain": {
          "domain": "coresignal.com",
          "registered": "2014-12-16",
          "source": "https://rdap.verisign.com/com/v1/domain/coresignal.com",
          "checkedAt": "2026-11-15T15:34:49.572204044Z"
        },
        "pages": [
          {
            "url": "https://docs.coresignal.com/release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:44.305755795Z",
            "changedAt": "2026-11-18T21:39:44.305755795Z",
            "fingerprint": "5b62ca5b67de"
          },
          {
            "url": "https://docs.coresignal.com/integrations/coresignal-mcp",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-18T21:39:39.428033547Z",
            "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-18T21:39:45.908610538Z",
            "changedAt": "2026-11-18T21:39:45.908610538Z",
            "fingerprint": "6492449fb59f"
          },
          {
            "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-18T21:39:41.980874409Z",
            "changedAt": "2026-11-18T21:39:41.980874409Z",
            "fingerprint": "6de37751e403"
          },
          {
            "url": "https://coresignal.com/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:35:53.725549773Z",
            "changedAt": "2026-10-22T01:12:26.149618037Z",
            "fingerprint": "cc381ea927a3"
          },
          {
            "url": "https://coresignal.com/terms-and-conditions/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:35:55.880657874Z",
            "changedAt": "2026-10-22T01:12:28.173752872Z",
            "fingerprint": "52d6faae51c5"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.coresignal.com/mcp/v2",
          "checkedAt": "2026-11-18T04:22:45.235731569Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:43:27.078662654Z"
        },
        "updatedAt": "2026-11-18T21:50:42.156379588Z"
      },
      "streak": {
        "days": 15,
        "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": "Coresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories.",
    "b": {
      "slug": "retriever",
      "name": "Retriever",
      "vendor": "Retriever",
      "vendorUrl": "https://retriever.run",
      "company": "retriever.run",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Retriever is a hosted prospecting agent that finds and qualifies companies and contacts, enriches them with emails and phone numbers, and runs email and LinkedIn outreach, through a REST API and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/retriever",
      "markdownUrl": "https://www.anchorterminal.com/tools/retriever.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/retriever.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/retriever.json",
      "dns": "retriever.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://api.retriever.run/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ret_live_...`) made in the app under Settings \u003e API keys after a browser signup, shown once. The MCP server also takes OAuth 2.1 with dynamic client registration and PKCE, and the access token it issues is an ordinary API key named after the connection. No scopes or expiry were found: a key works as its creator in that person's organisation. Keys are revoked one by one in Settings; removing a connector doesn't revoke its key. The MCP docs also accept the key in the URL as `?api_key=`, with a warning about logs.",
      "pricing": "paid",
      "pricingNotes": "Starter from $80 a month billed quarterly for 6,000 credits ($0.0134 a credit), up to 40,000 credits a month, with one-off top-ups and credits kept 12 months. Email senders $2 each or $30 for unlimited, LinkedIn senders $10 an account. Credits per action are published, a work email 4 to 12, a phone 15 to 60, a company 0.5 to 2. Enterprise is through sales. No free tier or no-card trial was found; the terms say only that free tiers may be offered.",
      "priceSummary": "$0.0134 / credit",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the pricing page, the docs, llms.txt or the OpenAPI file, 18 November 2026. Credits come with a subscription bought in the app.",
        "endpoints": []
      },
      "toolCount": 67,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.retriever.run",
      "llmsTxt": "https://docs.retriever.run/llms.txt",
      "openapi": "https://docs.retriever.run/openapi.yaml",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company",
        "web.search",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "openapi",
        "llms-txt",
        "closed-source",
        "paid",
        "subscription",
        "linkedin",
        "outreach",
        "no-status-page",
        "platform-rules",
        "eu"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 32,
        "grade": "F",
        "agentReady": false,
        "rank": 1455,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 49
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": -15,
        "warnings": [
          {
            "kind": "platform-rules",
            "name": "Breaks the rules of the platforms it acts on",
            "text": "Retriever connects a customer's LinkedIn accounts and sends invitations, messages, profile visits and post likes from them on a schedule, with messages a model writes, which LinkedIn's rules on automated activity forbid.",
            "deduct": -15,
            "since": "2026-11-18",
            "sources": [
              "https://docs.retriever.run/mcp/tools.md",
              "https://retriever.run/pricing",
              "https://www.linkedin.com/help/linkedin/answer/90586",
              "https://www.linkedin.com/help/linkedin/answer/a1341387"
            ]
          }
        ],
        "verdict": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.",
        "bestFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "strengths": [
          "OpenAPI 3.1 file, llms.txt and Markdown docs, with an errors page of stable codes and the action to take for each",
          "Remote MCP server with OAuth 2.1, dynamic client registration and PKCE, so a client connects without pasting a key",
          "Rate limits published per key and class (30 a minute for runs, 120 for services, 600 for reads and MCP messages), with Retry-After on 429",
          "Idempotency keys on run creation and a recipe for safe retries, plus read-only, destructive and idempotent hints on the MCP tools",
          "Credits per action and the dollar price per credit published without a login"
        ],
        "weaknesses": [
          "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted",
          "No status page, changelog, security.txt, disclosure policy or certification found",
          "Keys have no scopes or expiry, and the MCP docs accept the key in the URL as `?api_key=`",
          "No free tier or trial without a card found; access needs a browser signup and a subscription from $80 a month",
          "The terms and privacy policy name only \"Retriever\" under French law, with no company number or address, and the privacy policy doesn't mention connected LinkedIn or email accounts"
        ],
        "agentNotes": [
          "Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account",
          "Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run",
          "Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them",
          "Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it",
          "On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 32
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 43
        },
        "provenanceScore": 54,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -s https://api.retriever.run/credits -H \"Authorization: Bearer $RETRIEVER_API_KEY\"",
        "claudeCode": "claude mcp add --transport http --scope user retriever https://api.retriever.run/mcp",
        "config": {
          "mcpServers": {
            "retriever": {
              "url": "https://api.retriever.run/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/retriever"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Credit, Starter plan",
          "unit": "credit",
          "usd": 0.0134,
          "note": "$80 a month billed quarterly for 6,000 credits"
        },
        {
          "item": "Work email found",
          "unit": "tx",
          "usd": 0.06,
          "note": "4 to 12 credits, about $0.06 to $0.18 per the pricing page"
        },
        {
          "item": "Phone number found",
          "unit": "tx",
          "usd": 0.22,
          "note": "15 to 60 credits, about $0.22 to $0.89 per the pricing page"
        },
        {
          "item": "LinkedIn sender",
          "unit": "account-month",
          "usd": 10,
          "note": "Per connected LinkedIn account"
        }
      ],
      "provenance": {
        "legalEntity": "Retriever",
        "domain": "retriever.run",
        "domainRegistered": "2026-04-07",
        "endpointOnVendorDomain": true,
        "terms": "https://retriever.run/terms",
        "privacy": "https://retriever.run/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms and privacy policy, both last updated 30 August 2026, name the entity only as Retriever, choose French law and the Paris courts, and give emma@retriever.run as the contact. No company number, address or register entry was found; the French company register (annuaire-entreprises.data.gouv.fr) answered with a bot check, so it wasn't searched.",
          "retriever.run/robots.txt allows every crawler. docs.retriever.run publishes rules that didn't close the pages read. The site carries a content-signals preamble in robots.txt with no ai-input=no.",
          "RDAP gives retriever.run a registration date of 7 April 2026.",
          "/.well-known/security.txt answered 404. No status page or changelog is linked from the site or the docs.",
          "The privacy policy names Vercel, Railway, Supabase, Anthropic and OpenAI as examples of subprocessors and says personal data isn't sold. It doesn't cover the LinkedIn and email accounts customers connect, or the data providers named on the pricing page."
        ],
        "score": 54
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/retriever.json",
      "live": {
        "slug": "retriever",
        "probe": {
          "target": "https://api.retriever.run/mcp",
          "method": "get",
          "lastAt": "2026-11-18T21:51:12.571692585Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 193,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 201,
          "p95ms24h": 385,
          "samples24h": 172,
          "samples30d": 172,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 172,
              "ok": 172
            }
          ],
          "since": "2026-11-18T04:42:08.539827226Z"
        },
        "securityTxt": {
          "url": "https://retriever.run/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:40.595836687Z"
        },
        "llmsTxt": {
          "url": "https://docs.retriever.run/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:58.22750683Z"
        },
        "pages": [
          {
            "url": "https://retriever.run/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:43.303154652Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "df5f8e8262ec"
          },
          {
            "url": "https://retriever.run/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:45.492573613Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7d5324c0992b"
          }
        ],
        "updatedAt": "2026-11-18T21:52:45.492573613Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 77,
        "category": "maintenance",
        "leads": "coresignal",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Release notes have dated entries to 1 November 2026 (30). 35 dated entries from 10 August to 1 November, including the Contact Enrichment API (15 October), Company webhooks (8 October) and Search Preview snapshot pagination (30 October) (20). Public, detailed release notes, and we didn't test support (12 of 15). Listed in the official MCP registry as com.coresignal/mcp 2.0.0, a domain-verified namespace, published 7 August 2026 (15). No SDK packages to judge (5 of 10). 30 + 20 + 12 + 15 + 5 = 82.",
          "b": "No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026."
        },
        "scores": {
          "a": 82,
          "b": 5
        }
      },
      {
        "by": 35,
        "category": "security",
        "leads": "coresignal",
        "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": "The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0)."
        },
        "scores": {
          "a": 58,
          "b": 23
        }
      },
      {
        "by": 22,
        "category": "transparency",
        "leads": "coresignal",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc. (Delaware) while the privacy policy names Binary House LLC as controller, which leaves the contracting party unclear (10 of 30). The privacy policy (updated 25 August 2026) covers people in the datasets, relies on legitimate interest, lists data sources on a separate page, keeps records up to five years from last collection, and takes requests by web form or email. No DPA found in the policy (20 of 30). Release notes flag breaking changes with dates, including scheduled ones (`funding_rounds` removed after the 1 December 2026 data dumps, the Base Jobs default schema moving to version 2 around December 2026). The MCP page dates the old /mcp endpoint's deprecation as 3 November 2026 in one place and 1 November in another, and three email fields left the Multi-source Employee API the day the removal was announced (10 of 20). Subprocessors named in the policy (Stripe, SendGrid, Deeptrace, Google, Meta) with US transfers under contractual clauses (15 of 20).",
          "b": "Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed \"with reasonable notice\" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20)."
        },
        "scores": {
          "a": 71,
          "b": 49
        }
      },
      {
        "by": 15,
        "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, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10)."
        },
        "scores": {
          "a": 60,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Coresignal",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "https://api.coresignal.com/cdapi",
        "b": "https://api.retriever.run/mcp",
        "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": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "5",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "com.coresignal/mcp",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-01",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2022-02-21",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-25",
        "b": "2026-08-30",
        "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": "yes",
        "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": "Coresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories.",
        "question": "Which is better for AI agents, Coresignal API + MCP or Retriever?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Coresignal API + MCP and Retriever need an API key?"
      },
      {
        "answer": "Yes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Retriever at https://api.retriever.run/mcp.",
        "question": "Can an agent call Coresignal API + MCP and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 60 against 45",
          "Security \u0026 auth, 58 against 23",
          "Maintenance \u0026 community, 82 against 5",
          "Transparency \u0026 trust, 71 against 49"
        ],
        "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": null,
        "also": null,
        "goodFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "slug": "retriever",
        "watchFor": "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted"
      }
    ],
    "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"
        }
      ],
      "retriever": 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-retriever.json",
        "title": "Apollo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-retriever"
      },
      {
        "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-retriever.json",
        "title": "Clay vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
      },
      {
        "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-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-retriever.json",
        "title": "Crustdata API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-retriever.json",
        "title": "Dievio vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json",
        "title": "Enrich Layer API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.json",
        "title": "Explorium AgentSource vs Retriever",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json",
        "title": "FullEnrich API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json",
        "title": "Fuse MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json",
        "title": "Gojiberry vs Retriever",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json",
        "title": "LeadMagic API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-retriever.json",
        "title": "Lusha API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-retriever.json",
        "title": "Prospeo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach.json",
        "title": "Retriever vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo.json",
        "title": "Retriever vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/retriever-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-retriever.json",
        "title": "Clearbit vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-retriever"
      },
      {
        "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-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json",
        "title": "FullContact vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
        "title": "Retriever vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
      },
      {
        "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"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 15,
        "coresignal": 60,
        "edge": "coresignal",
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 4,
        "coresignal": 86,
        "edge": "coresignal",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 2,
        "coresignal": 73,
        "edge": "retriever",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 35,
        "coresignal": 58,
        "edge": "coresignal",
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 0,
        "coresignal": 30,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 77,
        "coresignal": 82,
        "edge": "coresignal",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 22,
        "coresignal": 71,
        "edge": "coresignal",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "Coresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. 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.",
      "retriever": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/coresignal-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.min.md"
  },
  "markdown": "Coresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Both do lead search.\n\n- Coresignal API + MCP: grade B, 62.1/100, rank #696 of 1557. Markdown https://www.anchorterminal.com/tools/coresignal.md · JSON https://www.anchorterminal.com/api/v1/tools/coresignal.json\n- Retriever: grade F, 32/100, rank #1455 of 1557. Markdown https://www.anchorterminal.com/tools/retriever.md · JSON https://www.anchorterminal.com/api/v1/tools/retriever.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 253 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 45\n- Security \u0026 auth, 58 against 23\n- Maintenance \u0026 community, 82 against 5\n- Transparency \u0026 trust, 71 against 49\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### Retriever (F)\n\nGood for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.\n\nWatch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Coresignal API + MCP +77\n\n- Coresignal API + MCP (82): Release notes have dated entries to 1 November 2026 (30). 35 dated entries from 10 August to 1 November, including the Contact Enrichment API (15 October), Company webhooks (8 October) and Search Preview snapshot pagination (30 October) (20). Public, detailed release notes, and we didn't test support (12 of 15). Listed in the official MCP registry as com.coresignal/mcp 2.0.0, a domain-verified namespace, published 7 August 2026 (15). No SDK packages to judge (5 of 10). 30 + 20 + 12 + 15 + 5 = 82.\n- Retriever (5): No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.\n\n### Security \u0026 auth: Coresignal API + MCP +35\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- Retriever (23): The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).\n\n### Transparency \u0026 trust: Coresignal API + MCP +22\n\n- Coresignal API + MCP (71): Closed service with published terms, but the terms (last updated 21 February 2022) name Deeptrace Inc. (Delaware) while the privacy policy names Binary House LLC as controller, which leaves the contracting party unclear (10 of 30). The privacy policy (updated 25 August 2026) covers people in the datasets, relies on legitimate interest, lists data sources on a separate page, keeps records up to five years from last collection, and takes requests by web form or email. No DPA found in the policy (20 of 30). Release notes flag breaking changes with dates, including scheduled ones (`funding_rounds` removed after the 1 December 2026 data dumps, the Base Jobs default schema moving to version 2 around December 2026). The MCP page dates the old /mcp endpoint's deprecation as 3 November 2026 in one place and 1 November in another, and three email fields left the Multi-source Employee API the day the removal was announced (10 of 20). Subprocessors named in the policy (Stripe, SendGrid, Deeptrace, Google, Meta) with US transfers under contractual clauses (15 of 20).\n- Retriever (49): Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed \"with reasonable notice\" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).\n\n### Reliability: Coresignal API + MCP +15\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- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).\n\n## Score by category\n\n| Category | Weight | Coresignal API + MCP | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 60 | 45 | Coresignal API + MCP +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 86 | 82 | Coresignal API + MCP +4 |\n| Agent ergonomics | 13% | 73 | 75 | Retriever +2 |\n| Security \u0026 auth | 14% | 58 | 23 | Coresignal API + MCP +35 |\n| Payments \u0026 pricing | 10% | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 82 | 5 | Coresignal API + MCP +77 |\n| Transparency \u0026 trust | 7% | 71 | 49 | Coresignal API + MCP +22 |\n| Negative events | ≤15 | -3 | -15 | |\n| **Total** | | **62.1 · B** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | Coresignal API + MCP | Retriever |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Coresignal | Retriever |\n| Hosted endpoint | `https://api.coresignal.com/cdapi` | `https://api.retriever.run/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Tools exposed | 5 | 67 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.coresignal/mcp` | not listed |\n| Last release | 2026-11-01 | none |\n| Terms last updated | 2022-02-21 | 2026-08-30 |\n| Privacy policy last updated | 2026-08-25 | 2026-08-30 |\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 | yes |\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### Retriever\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**Retriever.** Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.\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### Retriever\n\n1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account\n2. Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run\n3. Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them\n4. Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it\n5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again\n\n## Questions\n\n### Which is better for AI agents, Coresignal API + MCP or Retriever?\n\nCoresignal API + MCP scores 62.1 (B) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories.\n\n### Do Coresignal API + MCP and Retriever 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 Retriever without installing anything?\n\nYes. Coresignal API + MCP has a hosted endpoint at https://api.coresignal.com/cdapi and Retriever at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/coresignal-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coresignal-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"coresignal\", \"b\": \"retriever\"}`. From a terminal: `anchor compare coresignal retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coresignal.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with Coresignal API + MCP or Retriever\n\n- [Apollo API + MCP vs Coresignal API + MCP](https://www.anchorterminal.com/compare/apollo-vs-coresignal.md)\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clay-vs-coresignal.md)\n- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.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 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 Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)\n- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)\n- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)\n- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)\n- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)\n- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md)\n- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)\n- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)\n- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)\n- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)\n- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)\n- [Clearbit vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-coresignal.md)\n- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.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 Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.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-18",
    "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 Retriever",
        "url": ""
      }
    ],
    "description": "Coresignal scores 62.1 (B) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Coresignal API + MCP B 62.1",
      "Retriever F 32",
      "scores"
    ],
    "h1": "Coresignal API + MCP vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/coresignal-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Coresignal vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
  },
  "tokens": {
    "markdown": 4450,
    "slim": 880
  },
  "version": 1
}
