{
  "data": {
    "a": {
      "slug": "dropcontact",
      "name": "Dropcontact API + MCP",
      "vendor": "Dropcontact",
      "vendorUrl": "https://www.dropcontact.com",
      "company": "dropcontact.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Dropcontact's REST API and hosted MCP server find and verify professional email addresses and add job and company data to contacts sent with a name and a company.",
      "url": "https://www.anchorterminal.com/tools/dropcontact",
      "markdownUrl": "https://www.anchorterminal.com/tools/dropcontact.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dropcontact.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dropcontact.json",
      "dns": "dropcontact.grade.anchorterminal.com",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.dropcontact.com/v1",
      "packages": [],
      "auth": "mixed",
      "authNotes": "`X-Access-Token` header on REST. Hosted MCP at mcp.dropcontact.com uses OAuth, or the API key as `Authorization: Bearer`.",
      "pricing": "paid",
      "pricingNotes": "Prices are in euros only. 50 free credits to try. Starter €79 a month for 500 credits, Growth €120 a month for 500 credits with carry-over, LinkedIn URL enrichment and company data, both scaling to 150,000 credits a month. Yearly billing is 20 per cent off. Enterprise from 200,000 credits a month. A credit is spent only when a verified email comes back (refunded if none is found), or 1 credit per email you send in for verification (https://www.dropcontact.com/pricing).",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402 mention in the API docs, MCP docs or pricing (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://developer.dropcontact.com",
      "llmsTxt": "https://developer.dropcontact.com/llms.txt",
      "capabilities": [
        "lead.enrichment",
        "email.finder",
        "email.verification",
        "data.company"
      ],
      "tags": [
        "enrichment",
        "email-verification",
        "hosted",
        "no-card",
        "mcp",
        "llms-txt",
        "webhooks",
        "async-jobs",
        "closed-source"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 61.6,
        "grade": "C",
        "agentReady": false,
        "rank": 722,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 64,
          "maintenance": 15,
          "payments": 60,
          "reliability": 85,
          "schema": 54,
          "security": 59,
          "transparency": 72
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.",
        "bestFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.",
        "strengths": [
          "Pay on success, with credits refunded when no email is found",
          "50 free credits with no card",
          "Statuspage with its own API component and no incident since March 2026",
          "Errors page lists each message by status code with what to do, plus per-contact error and warning keys",
          "llms.txt and Markdown docs, security.txt with a HackerOne programme, and a published DPA"
        ],
        "weaknesses": [
          "No OpenAPI file or changelog",
          "No prospect search, so it only enriches people you already have",
          "Asynchronous only, with webhooks that can arrive out of order or twice",
          "One unscoped API key per account",
          "Remote MCP connections called early by the vendor, and no registry entry we could read"
        ],
        "agentNotes": [
          "Send a company name, website, email or LinkedIn URL with every contact, or you get `only_contact_data`",
          "Read `success` on every 200. A result still processing answers 200 with `success: false`",
          "Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen",
          "Poll no faster than every 30 seconds, and back off for a few seconds after a 429",
          "Call Get Credits to read the balance at no cost"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 61.6
          }
        ],
        "editorialScores": {
          "ergonomics": 64,
          "maintenance": 15,
          "payments": 60,
          "reliability": 85,
          "schema": 54,
          "security": 59,
          "transparency": 55
        },
        "provenanceScore": 88,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://api.dropcontact.com/v1/enrich/all -H \"X-Access-Token: $DROPCONTACT_API_KEY\" \\\n  -H \"Content-Type: application/json\" -d '{\"data\":[{\"first_name\":\"John\",\"last_name\":\"Smith\",\"website\":\"corporation.com\"}],\"language\":\"en\"}'",
        "claudeCode": "claude mcp add --transport http dropcontact https://mcp.dropcontact.com/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/lead.enrichment",
        "tool": "https://letme.dev/dropcontact"
      },
      "area": "web-data",
      "provenance": {
        "legalEntity": "Dropcontact SAS",
        "domain": "dropcontact.com",
        "domainRegistered": "2016-03-21",
        "endpointOnVendorDomain": true,
        "terms": "https://www.dropcontact.com/terms",
        "privacy": "https://www.dropcontact.com/personal-data-charter",
        "statusPage": "https://status.dropcontact.com",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-04",
        "notes": [
          "Terms name a simplified joint stock company (SAS) registered in Bobigny, no. 823 752 647",
          "The terms (in force since 18 March 2020, updated 5 August 2025) carry no ban on automated access to the site."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/dropcontact.json",
      "live": {
        "slug": "dropcontact",
        "probe": {
          "target": "https://api.dropcontact.com/v1",
          "method": "get",
          "lastAt": "2026-11-18T21:50:45.68120308Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 168,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 57,
          "p95ms24h": 191,
          "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": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 220,
              "ok": 220
            }
          ],
          "since": "2026-10-08T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.dropcontact.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T21:51:04.119935686Z"
        },
        "securityTxt": {
          "url": "https://dropcontact.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-04-09T00:00:00.000Z",
          "checkedAt": "2026-11-18T16:30:41.789164431Z"
        },
        "llmsTxt": {
          "url": "https://developer.dropcontact.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:10.105717345Z"
        },
        "domain": {
          "domain": "dropcontact.com",
          "registered": "2016-03-21",
          "source": "https://rdap.verisign.com/com/v1/domain/dropcontact.com",
          "checkedAt": "2026-11-15T15:25:57.157118214Z"
        },
        "pages": [
          {
            "url": "https://developer.dropcontact.com",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-04T08:18:12.087098414Z",
            "changedAt": "2026-11-04T08:18:12.087098414Z",
            "fingerprint": "e3d50cde523f"
          },
          {
            "url": "https://developer.dropcontact.com/en/errors/",
            "kind": "deprecations",
            "status": 304,
            "checkedAt": "2026-11-18T21:36:59.187482981Z",
            "changedAt": "2026-11-09T15:34:22.031847287Z",
            "fingerprint": "d4cc68655636"
          },
          {
            "url": "https://www.dropcontact.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-17T21:21:51.218510905Z",
            "changedAt": "2026-11-04T08:39:37.076625053Z",
            "fingerprint": "fb067c43c25f"
          },
          {
            "url": "https://www.dropcontact.com/personal-data-charter",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-17T21:21:49.136891841Z",
            "changedAt": "2026-11-04T08:39:34.797459992Z",
            "fingerprint": "dc7007adf25c"
          },
          {
            "url": "https://www.dropcontact.com/terms",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-17T21:21:53.206563278Z",
            "changedAt": "2026-11-04T08:39:38.893188244Z",
            "fingerprint": "33bbf4251df5"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.dropcontact.com/mcp",
          "checkedAt": "2026-11-18T04:23:19.719671684Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:43:57.867463276Z"
        },
        "updatedAt": "2026-11-18T21:50:45.68120308Z"
      },
      "streak": {
        "days": 41,
        "from": "2026-10-08",
        "sinceWatching": true,
        "last": {
          "kind": "breaking",
          "date": "2026-06-01",
          "what": "Accounts created since 1 June 2026 have the `API_ERROR` option on by default, so a request whose every record has an error gets a 400 instead of a 200",
          "source": "https://developer.dropcontact.com/en/errors/"
        },
        "best": 41
      }
    },
    "answer": "Dropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.",
    "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": 40,
        "category": "reliability",
        "leads": "dropcontact",
        "name": "Reliability",
        "reasons": {
          "a": "Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.",
          "b": "No status page found, 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": 85,
          "b": 45
        }
      },
      {
        "by": 36,
        "category": "security",
        "leads": "dropcontact",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "One API key per account in the `X-Access-Token` header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.",
          "b": "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": 59,
          "b": 23
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "dropcontact",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.",
          "b": "No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0)."
        },
        "scores": {
          "a": 60,
          "b": 30
        }
      },
      {
        "by": 28,
        "category": "schema",
        "leads": "retriever",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with `custom_fields` a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.",
          "b": "OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15)."
        },
        "scores": {
          "a": 54,
          "b": 82
        }
      },
      {
        "by": 23,
        "category": "transparency",
        "leads": "dropcontact",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.",
          "b": "Closed 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": 72,
          "b": 49
        }
      },
      {
        "by": 11,
        "category": "ergonomics",
        "leads": "retriever",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. `forceResults=true` returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as `only_contact_data` say what to add (20). Asynchronous jobs keyed by `request_id` and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.",
          "b": "67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15)."
        },
        "scores": {
          "a": 64,
          "b": 75
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Dropcontact",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "https://api.dropcontact.com/v1",
        "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": "none",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2025-08-01",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2020-06-04",
        "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": "3.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Dropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.",
        "question": "Which is better for AI agents, Dropcontact API + MCP or Retriever?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Dropcontact API + MCP and Retriever need an API key?"
      },
      {
        "answer": "Yes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Retriever at https://api.retriever.run/mcp.",
        "question": "Can an agent call Dropcontact API + MCP and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 85 against 45",
          "Security \u0026 auth, 59 against 23",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 15 against 5",
          "Transparency \u0026 trust, 72 against 49"
        ],
        "also": [
          "Free to start without a card",
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "European teams cleaning and completing contact lists where GDPR handling matters more than coverage.",
        "slug": "dropcontact",
        "watchFor": "No OpenAPI file or changelog"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 82 against 54",
          "Agent ergonomics, 75 against 64"
        ],
        "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": {
      "dropcontact": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 59.1,
          "fromGrade": "C",
          "to": 61.6,
          "toGrade": "C"
        },
        {
          "causes": [
            "product",
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 8.1,
          "from": 51,
          "fromGrade": "D",
          "to": 59.1,
          "toGrade": "C"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 50.9,
          "fromGrade": "D",
          "to": 51,
          "toGrade": "D"
        }
      ],
      "retriever": null
    },
    "job": {
      "capability": "lead.enrichment",
      "name": "Lead enrichment"
    },
    "others": [
      {
        "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-retriever.json",
        "title": "Clay vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
      },
      {
        "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/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/apollo-vs-dropcontact.json",
        "title": "Apollo API + MCP vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.json",
        "title": "Clay vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.json",
        "title": "Clearbit vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-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/crustdata-vs-dropcontact.json",
        "title": "Crustdata API + MCP vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-dropcontact.json",
        "title": "Databar vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/databar-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-dropcontact.json",
        "title": "Dievio vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.json",
        "title": "Dropcontact API + MCP vs Enrich Layer API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.json",
        "title": "Dropcontact API + MCP vs Explorium AgentSource",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.json",
        "title": "Dropcontact API + MCP vs FullContact",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.json",
        "title": "Dropcontact API + MCP vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.json",
        "title": "Dropcontact API + MCP vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.json",
        "title": "Dropcontact API + MCP vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter.json",
        "title": "Dropcontact API + MCP vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.json",
        "title": "Dropcontact API + MCP vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha.json",
        "title": "Dropcontact API + MCP vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.json",
        "title": "Dropcontact API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.json",
        "title": "Dropcontact API + MCP vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.json",
        "title": "Dropcontact API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.json",
        "title": "Dropcontact API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.json",
        "title": "Dropcontact API + MCP vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-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": 40,
        "dropcontact": 85,
        "edge": "dropcontact",
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 28,
        "dropcontact": 54,
        "edge": "retriever",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 11,
        "dropcontact": 64,
        "edge": "retriever",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 36,
        "dropcontact": 59,
        "edge": "dropcontact",
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 30,
        "dropcontact": 60,
        "edge": "dropcontact",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 10,
        "dropcontact": 15,
        "edge": "dropcontact",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 23,
        "dropcontact": 72,
        "edge": "dropcontact",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "Dropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics. Both do lead enrichment.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "dropcontact": "Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.",
      "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/dropcontact-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.min.md"
  },
  "markdown": "Dropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics. Both do lead enrichment.\n\n- Dropcontact API + MCP: grade C, 61.6/100, rank #722 of 1557. Markdown https://www.anchorterminal.com/tools/dropcontact.md · JSON https://www.anchorterminal.com/api/v1/tools/dropcontact.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### Dropcontact API + MCP (C)\n\nGood for: European teams cleaning and completing contact lists where GDPR handling matters more than coverage.\n\nAhead on:\n- Reliability, 85 against 45\n- Security \u0026 auth, 59 against 23\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 15 against 5\n- Transparency \u0026 trust, 72 against 49\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: No OpenAPI file or changelog\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\nAhead on:\n- Schema \u0026 documentation, 82 against 54\n- Agent ergonomics, 75 against 64\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### Reliability: Dropcontact API + MCP +40\n\n- Dropcontact API + MCP (85): Atlassian Statuspage at status.dropcontact.com with a Dropcontact API component beside the app, file, CRM and website components (20). Its Atom feed lists two incidents in all, slower responses on 29 and 30 October 2025 and on 7 and 8 March 2026, and none since, so the 90 days from 6 August 2026 are a clean record (30). 60 requests a second, 250 records a request and 15 kB a record (15). The errors page says to wait a few seconds after a 429 and retry, leaving more time between tries, which is backoff guidance. No idempotency key or safe-retry guidance for the enrich call (10). No SLA found (0). The REST API is generally available, and this benchmark reads a GA API beside an MCP server its vendor calls early as GA (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.\n- 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### Security \u0026 auth: Dropcontact API + MCP +36\n\n- Dropcontact API + MCP (59): One API key per account in the `X-Access-Token` header, no scopes found. OAuth or the key as a bearer token on the MCP (20 of 30). Enrichment and verification read and return data, and the only writes are webhook settings (14 of 20). Results are cleaned names, titles and company fields rather than free text, so little untrusted content comes back (8 of 15). Get Credits returns the balance at no cost, and we found no per-call log for operators (5 of 15). security.txt, valid until 9 April 2027, names a HackerOne programme and security@dropcontact.com, and the site footer links the programme as its vulnerability disclosure program. The HackerOne page wasn't re-read. No SOC 2 or ISO 27001 found (12 of 20). No 2025 or 2026 record in the CVE list names Dropcontact. 20 + 14 + 8 + 5 + 12 = 59.\n- 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### Payments \u0026 pricing: Dropcontact API + MCP +30\n\n- Dropcontact API + MCP (60): No x402, MPP or L402 (0). Plan prices and credit allowances are public in euros (Starter €79 and Growth €120 a month for 500 credits, 20 per cent off yearly), and a credit is one verified email found (given back when none is) or one email checked (20). 50 free credits at signup with no card (20). A person signs up in a browser and creates the key in the app (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n- Retriever (30): No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).\n\n### Schema \u0026 documentation: Retriever +28\n\n- Dropcontact API + MCP (54): No OpenAPI file or other machine-readable contract published (0). llms.txt and llms-full.txt list Markdown copies of every docs page in English and French (10). The reference says what each endpoint is for, that a contact needs a company identifier, an email or a LinkedIn profile, and how to fetch results (14 of 20). Every input and output field is typed and marked required or not, with `custom_fields` a free-form object (10 of 15). Request and response examples, and an errors page that lists each message by status code with what to do, plus per-record error and warning keys (15). /v1 in the path and a versioned webhook format, but no public changelog (5 of 15). 0 + 10 + 14 + 10 + 15 + 5 = 54.\n- Retriever (82): OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). The tool catalogue says when to use most tools and when not to (cancels only on the user's request, slow services only in a batch) (17 of 20). The OpenAPI file has enums and required fields; the MCP input schemas weren't read, since tools/list needs a key (11 of 15). An errors page with stable codes and the action for each, plus examples in the docs (14 of 15). Routes are versioned under /v1 but there's no public changelog (5 of 15).\n\n### Transparency \u0026 trust: Dropcontact API + MCP +23\n\n- Dropcontact API + MCP (72): Closed service with terms (updated 5 August 2025) naming Dropcontact SAS, registered in Bobigny, no. 823 752 647 (15). The personal data charter (updated 5 August 2025) keeps prospecting data 3 years after the relationship plus 4 in intermediate storage, takes rights requests at data@dropcontact.io, says data may be collected from publicly accessible information and hosted in the EU with some subcontractors in the United States under standard contractual clauses, and a DPA is published. The pricing page says processing runs only on Dropcontact's own algorithms on EU servers with no reliance on non-compliant third-party providers, and that it uses no contact databases. It now also says mobile numbers come from signature extraction within internal email flows, with five years of history, which the charter doesn't mention (22 of 30). One dated change for new accounts (1 June 2026) and no deprecation policy (8 of 20). EU hosting and US subcontractors stated, no named subprocessor list found (10 of 20). 15 + 22 + 8 + 10 = 55.\n- 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### Agent ergonomics: Retriever +11\n\n- Dropcontact API + MCP (64): The MCP has a handful of tools (enrich from a name and company or a LinkedIn URL, validate an email, check credits, then fetch the result by request ID), and REST takes up to 250 contacts a call. No field selection (20 of 25). No search, so little to page or filter. `forceResults=true` returns the records already enriched (10 of 20). The errors page gives each message with a fix, and per-record keys such as `only_contact_data` say what to add (20). Asynchronous jobs keyed by `request_id` and pay on success, but no idempotency key, and webhooks can arrive out of order or twice (8 of 20). Few required fields and no official SDKs (6 of 15). 20 + 10 + 20 + 8 + 6 = 64.\n- Retriever (75): 67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).\n\n## Score by category\n\n| Category | Weight | Dropcontact API + MCP | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 85 | 45 | Dropcontact API + MCP +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 54 | 82 | Retriever +28 |\n| Agent ergonomics | 13% | 64 | 75 | Retriever +11 |\n| Security \u0026 auth | 14% | 59 | 23 | Dropcontact API + MCP +36 |\n| Payments \u0026 pricing | 10% | 60 | 30 | Dropcontact API + MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 15 | 5 | Dropcontact API + MCP +10 |\n| Transparency \u0026 trust | 7% | 72 | 49 | Dropcontact API + MCP +23 |\n| Negative events | ≤15 | 0 | -15 | |\n| **Total** | | **61.6 · C** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | Dropcontact API + MCP | Retriever |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Dropcontact | Retriever |\n| Hosted endpoint | `https://api.dropcontact.com/v1` | `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 | none | 67 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Terms last updated | 2025-08-01 | 2026-08-30 |\n| Privacy policy last updated | 2020-06-04 | 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| Agent reviews | 3.5/5 (2) | none |\n\n## How the scores have moved\n\n### Dropcontact API + MCP\n\n- +2.5 on 13 November 2026: checklist\n- +8.1 on 4 November 2026 (D to C): product, new evidence, correction\n- +0.1 on 27 October 2026: checklist\n\n### Retriever\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Dropcontact API + MCP.** Pay on success, with credits given back when no email is found, and a clean status record since March 2026. The docs now list every error message with a fix and carry llms.txt. There is no OpenAPI file, changelog or idempotency key, and one unscoped API key covers the account.\n\n**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### Dropcontact API + MCP\n\n1. Send a company name, website, email or LinkedIn URL with every contact, or you get `only_contact_data`\n2. Read `success` on every 200. A result still processing answers 200 with `success: false`\n3. Match webhook results by `request_id`, since order isn't guaranteed and duplicates happen\n4. Poll no faster than every 30 seconds, and back off for a few seconds after a 429\n5. Call Get Credits to read the balance at no cost\n\n### 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, Dropcontact API + MCP or Retriever?\n\nDropcontact API + MCP scores 61.6 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on schema \u0026 documentation and agent ergonomics.\n\n### Do Dropcontact 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 Dropcontact API + MCP and Retriever without installing anything?\n\nYes. Dropcontact API + MCP has a hosted endpoint at https://api.dropcontact.com/v1 and Retriever at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/dropcontact-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"dropcontact\", \"b\": \"retriever\"}`. From a terminal: `anchor compare dropcontact retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/dropcontact.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with Dropcontact API + MCP or Retriever\n\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.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- [Apollo API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/apollo-vs-dropcontact.md)\n- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)\n- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)\n- [Clearbit vs 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- [Crustdata API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.md)\n- [Databar vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/databar-vs-dropcontact.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dievio vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/dievio-vs-dropcontact.md)\n- [Dropcontact API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-enrich-layer.md)\n- [Dropcontact API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/dropcontact-vs-explorium-agentsource.md)\n- [Dropcontact API + MCP vs FullContact](https://www.anchorterminal.com/compare/dropcontact-vs-fullcontact.md)\n- [Dropcontact API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fullenrich.md)\n- [Dropcontact API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/dropcontact-vs-fuse-mcp.md)\n- [Dropcontact API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/dropcontact-vs-gojiberry.md)\n- [Dropcontact API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-hunter.md)\n- [Dropcontact API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-leadmagic.md)\n- [Dropcontact API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-lusha.md)\n- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md)\n- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)\n- [Dropcontact API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.md)\n- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)\n- [Dropcontact API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-zoominfo.md)\n- [FullContact vs 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": "Dropcontact API + MCP vs Retriever",
        "url": ""
      }
    ],
    "description": "Dropcontact scores 61.6 (C) to Retriever's 32 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Dropcontact API + MCP C 61.6",
      "Retriever F 32",
      "scores"
    ],
    "h1": "Dropcontact API + MCP vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/dropcontact-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Dropcontact vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
  },
  "tokens": {
    "markdown": 5100,
    "slim": 1030
  },
  "version": 1
}
