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