{
  "data": {
    "a": {
      "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
      }
    },
    "answer": "ZeroBounce scores 64.6 (B) 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": "zerobounce",
      "name": "ZeroBounce",
      "vendor": "Hertza L.L.C. (ZeroBounce)",
      "vendorUrl": "https://www.zerobounce.net",
      "company": "zerobounce.net",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "ZeroBounce is an email verification API from Hertza L.L.C. that checks single addresses and lists for deliverability, with status and sub-status codes, plus AI scoring, email finder, domain search and activity data, and an open-source MCP server.",
      "url": "https://www.anchorterminal.com/tools/zerobounce",
      "markdownUrl": "https://www.anchorterminal.com/tools/zerobounce.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zerobounce.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zerobounce.json",
      "dns": "zerobounce.grade.anchorterminal.com",
      "repo": "https://github.com/zerobounce",
      "license": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://api.zerobounce.net/v2",
      "packages": [
        {
          "registry": "npm",
          "name": "@zerobounce/zero-bounce-sdk"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key from the dashboard, sent as the `api_key` query parameter in the documented calls. Several keys per account besides a Master key; keys can be named, switched off, regenerated, deleted and limited to whitelisted IPs or ranges. No endpoint scopes found.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go from $39 for 2,000 validations, one credit per email, 20 per successful Email Finder query, nothing for unknown results. ZeroBounce ONE from $99 a month, minimum 10,000 credits. Freemium of 100 validations a month for business or premium domains. Credits bought after 1 June 2026 expire two years after the last purchase (https://www.zerobounce.net/pricing, https://www.zerobounce.net/terms-of-use, checked 2026-11-06).",
      "priceSummary": "$0.0195 / call",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs, pricing or MCP page (checked 2026-11-06).",
        "endpoints": []
      },
      "toolCount": 0,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-06"
      },
      "docsUrl": "https://www.zerobounce.net/docs/",
      "llmsTxt": "https://www.zerobounce.net/llms.txt",
      "capabilities": [
        "email.verification",
        "email.finder",
        "lead.enrichment"
      ],
      "tags": [
        "hosted",
        "mcp",
        "status-page",
        "soc2",
        "iso27001",
        "free-tier",
        "usage-based",
        "typescript",
        "eu-region",
        "closed-source"
      ],
      "lastRelease": "2026-10-25",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 64.6,
        "grade": "B",
        "agentReady": false,
        "rank": 582,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 70,
          "payments": 53,
          "reliability": 75,
          "schema": 54,
          "security": 65,
          "transparency": 63
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-06"
        },
        "negative": 0,
        "verdict": "ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract.",
        "bestFor": "Email verification before outreach, the verification-first listing in lead-data.",
        "strengths": [
          "Status and sub-status codes per address, and unknown results don't use credits",
          "Statuspage with API, API-US, API-EU and Bulk API components; three short incidents in the 90 days to 6 November 2026",
          "Rate limits published per endpoint group, with the block length for each",
          "SOC 2 Type 2, ISO/IEC 27001:2022, Intigriti testing and a published sub-processor list",
          "Freemium of 100 validations a month for business domains, and pay-as-you-go from $39 for 2,000"
        ],
        "weaknesses": [
          "Every documented example sends the key as an `api_key` query parameter",
          "No OpenAPI or other machine-readable contract; a Postman collection only",
          "Going over a limit blocks the key for a minute to a day, with no Retry-After documented",
          "llms.txt lists marketing pages, not the API docs",
          "Keys can be IP-whitelisted but not scoped to endpoints"
        ],
        "agentNotes": [
          "Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits",
          "Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later",
          "Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour",
          "Use the bulk file API for large lists instead of looping on /v2/validate",
          "Keep the key out of logs; the API takes it only as `api_key` in the URL"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.6
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 70,
          "payments": 53,
          "reliability": 75,
          "schema": 54,
          "security": 65,
          "transparency": 59
        },
        "provenanceScore": 67,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-06",
            "maintenance": "2026-11-06",
            "payments": "2026-11-06",
            "reliability": "2026-11-06",
            "schema": "2026-11-06",
            "security": "2026-11-06",
            "transparency": "2026-11-06"
          },
          "last": "2026-11-06",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-06",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl \"https://api.zerobounce.net/v2/validate?api_key=$ZEROBOUNCE_API_KEY\u0026email=valid@example.com\""
      },
      "letme": {
        "capability": "https://letme.dev/email.verification",
        "tool": "https://letme.dev/zerobounce"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Email validation, smallest pay-as-you-go pack",
          "unit": "call",
          "usd": 0.0195,
          "note": "$39 for 2,000 validations"
        },
        {
          "item": "ZeroBounce ONE",
          "unit": "month",
          "usd": 99,
          "note": "From $99 a month"
        }
      ],
      "provenance": {
        "legalEntity": "Hertza L.L.C.",
        "domain": "zerobounce.net",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.zerobounce.net/terms-of-use",
        "privacy": "https://www.zerobounce.net/privacy-policy",
        "statusPage": "https://status.zerobounce.net",
        "changelog": "",
        "securityTxt": "unknown",
        "checked": "2026-11-06",
        "notes": [
          "Terms of use name Hertza L.L.C., doing business as ZeroBounce, a Nevada LLC, under Nevada law; the terms take effect on the date accepted. Privacy policy last updated 30 June 2026.",
          "www.zerobounce.net/robots.txt allows all and names ClaudeBot as allowed. status.zerobounce.net disallows /api/ and /embed/; its history was read from history.rss.",
          "No public changelog for the API was found.",
          "security.txt was not checked."
        ],
        "score": 67
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/zerobounce.json",
      "live": {
        "slug": "zerobounce",
        "probe": {
          "target": "https://api.zerobounce.net/v2",
          "method": "get",
          "lastAt": "2026-11-18T21:51:26.083703846Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 110,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 100,
          "p95ms24h": 200,
          "samples24h": 242,
          "samples30d": 2905,
          "days": [
            {
              "date": "2026-11-06",
              "probes": 13,
              "ok": 13
            },
            {
              "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-11-06T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.zerobounce.net",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T21:52:14.881122322Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@zerobounce/zero-bounce-sdk",
            "version": "5.0.2",
            "seenAt": "2026-11-18T18:43:47.831011694Z"
          }
        ],
        "npmWeekly": 38370,
        "securityTxt": {
          "url": "https://zerobounce.net/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:30:07.559075741Z"
        },
        "llmsTxt": {
          "url": "https://www.zerobounce.net/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:16:49.714514841Z"
        },
        "domain": {
          "domain": "zerobounce.net",
          "registered": "2017-01-24",
          "source": "https://rdap.verisign.com/net/v1/domain/zerobounce.net",
          "checkedAt": "2026-11-15T15:36:01.988478644Z"
        },
        "pages": [
          {
            "url": "https://www.zerobounce.net/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-17T21:31:15.25888115Z",
            "changedAt": "2026-11-11T17:27:37.904740848Z",
            "fingerprint": "7273dc41ea4e"
          },
          {
            "url": "https://www.zerobounce.net/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-17T21:31:19.160204166Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "6267cfec1592"
          },
          {
            "url": "https://www.zerobounce.net/terms-of-use",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-17T21:31:19.537852882Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "08727e5bbf09"
          }
        ],
        "updatedAt": "2026-11-18T21:52:14.881122322Z"
      },
      "streak": {
        "days": 12,
        "from": "2026-11-06",
        "sinceWatching": true,
        "best": 12
      }
    },
    "edges": [
      {
        "by": 65,
        "category": "maintenance",
        "leads": "zerobounce",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70."
        },
        "scores": {
          "a": 5,
          "b": 70
        }
      },
      {
        "by": 42,
        "category": "security",
        "leads": "zerobounce",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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).",
          "b": "Several named keys besides a Master key, regeneration, deactivation and IP whitelists (25), less 10 because the documented calls carry the key in the `api_key` query string (15 of 30). Validation only reads, though file and list endpoints can delete uploads (12 of 20). Results are structured status codes with little free text (10 of 15). API usage and dashboard statistics endpoints (10 of 15). SOC 2 Type 2, ISO/IEC 27001:2022, continuous testing with Intigriti and penetration testing with BitSentinel; no public disclosure policy found (18 of 20). 15+12+10+10+18 = 65."
        },
        "scores": {
          "a": 23,
          "b": 65
        }
      },
      {
        "by": 30,
        "category": "reliability",
        "leads": "zerobounce",
        "name": "Reliability",
        "reasons": {
          "a": "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).",
          "b": "Hosted lines. Statuspage at status.zerobounce.net with API, API-US, API-EU, Bulk API, website and Cloudflare components (20). The incident feed for 8 August to 6 November shows a 6-minute members platform disruption on 9 September, about 3 minutes of reduced EU API availability on 1 October, and a file upload issue on 26 October resolved within 6 minutes, all minor (20). Limits published per endpoint group with numbers and block lengths (15). 429 is documented with advice to throttle, but no Retry-After, and a block can last an hour or a day (10 of 15). No SLA found (0). Generally available (10). 20+20+15+10+0+10 = 75."
        },
        "scores": {
          "a": 45,
          "b": 75
        }
      },
      {
        "by": 28,
        "category": "schema",
        "leads": "retriever",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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).",
          "b": "No OpenAPI or other machine-readable contract found; a Postman collection is linked (5 of 25). llms.txt lists marketing pages, and the docs have no Markdown twins (5 of 10). Endpoint pages explain timing, credits and when to use batch or file APIs (14 of 20). Parameter tables and listed status and sub-status values, including the ai_agent_mailbox sub-status added in July 2026 (10 of 15). Examples per endpoint, a sandbox and an error-code page (12 of 15). v2 paths, an API migration page and dated maintenance notices on the status page, with no API changelog (8 of 15). 5+5+14+10+12+8 = 54."
        },
        "scores": {
          "a": 82,
          "b": 54
        }
      },
      {
        "by": 23,
        "category": "payments",
        "leads": "zerobounce",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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).",
          "b": "No x402, MPP or L402 (0). Per-credit prices public, from $39 for 2,000 validations (20). Freemium of 100 validations a month for business or premium domains; a card requirement isn't stated, and free webmail addresses don't qualify (15 of 20). A person signs up in a browser (0). 0+20+15+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53."
        },
        "scores": {
          "a": 30,
          "b": 53
        }
      },
      {
        "by": 14,
        "category": "transparency",
        "leads": "zerobounce",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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).",
          "b": "Closed service under terms naming Hertza L.L.C. (ZeroBounce) of Nevada; SDKs and MCP server open source (15 of 30). The data protection page says uploaded data is never kept more than 30 days, the privacy policy of 30 June 2026 keeps account data 'as long as needed', and EU and UK DPAs are published (22 of 30). An API migration page, with no dated deprecation policy (6 of 20). A sub-processor list naming each provider and the data exchanged (16 of 20). 15+22+6+16 = 59."
        },
        "scores": {
          "a": 49,
          "b": 63
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Retriever",
        "b": "Hertza L.L.C. (ZeroBounce)",
        "name": "Vendor"
      },
      {
        "a": "https://api.retriever.run/mcp",
        "b": "https://api.zerobounce.net/v2",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source",
        "name": "Licence"
      },
      {
        "a": "67",
        "b": "0",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "none",
        "b": "2026-10-25",
        "name": "Last release"
      },
      {
        "a": "2026-08-30",
        "b": "2026-05-05",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-30",
        "b": "2026-06-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": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "ZeroBounce scores 64.6 (B) 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, Retriever or ZeroBounce?"
      },
      {
        "answer": "Retriever takes an API key or an OAuth sign-in. ZeroBounce needs an API key.",
        "question": "Do Retriever and ZeroBounce need an API key?"
      },
      {
        "answer": "Yes. Retriever has a hosted endpoint at https://api.retriever.run/mcp and ZeroBounce at https://api.zerobounce.net/v2.",
        "question": "Can an agent call Retriever and ZeroBounce without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 82 against 54",
          "Agent ergonomics, 75 against 69"
        ],
        "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"
      },
      {
        "aheadOn": [
          "Reliability, 75 against 45",
          "Security \u0026 auth, 65 against 23",
          "Payments \u0026 pricing, 53 against 30",
          "Maintenance \u0026 community, 70 against 5",
          "Transparency \u0026 trust, 63 against 49"
        ],
        "also": [
          "Runs on your own machine",
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "Email verification before outreach, the verification-first listing in lead-data.",
        "slug": "zerobounce",
        "watchFor": "Every documented example sends the key as an `api_key` query parameter"
      }
    ],
    "history": {
      "retriever": null,
      "zerobounce": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.2,
          "from": 62.4,
          "fromGrade": "B",
          "to": 64.6,
          "toGrade": "B"
        }
      ]
    },
    "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-zerobounce.json",
        "title": "Apollo API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-zerobounce.json",
        "title": "Clay vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/clay-vs-zerobounce"
      },
      {
        "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/clearbit-vs-zerobounce.json",
        "title": "Clearbit vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.json",
        "title": "Coresignal API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.json",
        "title": "Crustdata API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-zerobounce.json",
        "title": "Databar vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/databar-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce.json",
        "title": "Dievio vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-zerobounce"
      },
      {
        "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/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/enrich-layer-vs-zerobounce.json",
        "title": "Enrich Layer API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.json",
        "title": "Explorium AgentSource vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce"
      },
      {
        "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/fullcontact-vs-zerobounce.json",
        "title": "FullContact vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.json",
        "title": "FullEnrich API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.json",
        "title": "Gojiberry vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce.json",
        "title": "Lusha API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.json",
        "title": "People Data Labs vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.json",
        "title": "Prospeo API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.json",
        "title": "ZeroBounce vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce.json",
        "title": "Hunter API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.json",
        "title": "Fuse MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.json",
        "title": "LeadMagic API + MCP vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce.json",
        "title": "RocketReach API vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/rocketreach-vs-zerobounce"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 30,
        "edge": "zerobounce",
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16,
        "zerobounce": 75
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 28,
        "edge": "retriever",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13,
        "zerobounce": 54
      },
      {
        "by": 6,
        "edge": "retriever",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13,
        "zerobounce": 69
      },
      {
        "by": 42,
        "edge": "zerobounce",
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14,
        "zerobounce": 65
      },
      {
        "by": 23,
        "edge": "zerobounce",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10,
        "zerobounce": 53
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 65,
        "edge": "zerobounce",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7,
        "zerobounce": 70
      },
      {
        "by": 14,
        "edge": "zerobounce",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7,
        "zerobounce": 63
      }
    ],
    "summary": "ZeroBounce scores 64.6 (B) 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": {
      "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.",
      "zerobounce": "ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce",
    "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.min.md"
  },
  "markdown": "ZeroBounce scores 64.6 (B) 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- 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- ZeroBounce: grade B, 64.6/100, rank #582 of 1557. Markdown https://www.anchorterminal.com/tools/zerobounce.md · JSON https://www.anchorterminal.com/api/v1/tools/zerobounce.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### 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 69\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### ZeroBounce (B)\n\nGood for: Email verification before outreach, the verification-first listing in lead-data.\n\nAhead on:\n- Reliability, 75 against 45\n- Security \u0026 auth, 65 against 23\n- Payments \u0026 pricing, 53 against 30\n- Maintenance \u0026 community, 70 against 5\n- Transparency \u0026 trust, 63 against 49\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: Every documented example sends the key as an `api_key` query parameter\n\n\n## Why the edge\n\n### Maintenance \u0026 community: ZeroBounce +65\n\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- ZeroBounce (70): Closed service. The JavaScript SDK 3.0.0 was published on 25 October 2026 (30). No API changelog; the dated changes found in 90 days are that release and status-page notices, fewer than three releases (10 of 20). Support by email and 24/7 chat per the docs, a public status page; replies not tested (10 of 15). Official SDKs in many languages and an MCP server (15). Package health not checked (5 of 10). 30+10+10+15+5 = 70.\n\n### Security \u0026 auth: ZeroBounce +42\n\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- ZeroBounce (65): Several named keys besides a Master key, regeneration, deactivation and IP whitelists (25), less 10 because the documented calls carry the key in the `api_key` query string (15 of 30). Validation only reads, though file and list endpoints can delete uploads (12 of 20). Results are structured status codes with little free text (10 of 15). API usage and dashboard statistics endpoints (10 of 15). SOC 2 Type 2, ISO/IEC 27001:2022, continuous testing with Intigriti and penetration testing with BitSentinel; no public disclosure policy found (18 of 20). 15+12+10+10+18 = 65.\n\n### Reliability: ZeroBounce +30\n\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- ZeroBounce (75): Hosted lines. Statuspage at status.zerobounce.net with API, API-US, API-EU, Bulk API, website and Cloudflare components (20). The incident feed for 8 August to 6 November shows a 6-minute members platform disruption on 9 September, about 3 minutes of reduced EU API availability on 1 October, and a file upload issue on 26 October resolved within 6 minutes, all minor (20). Limits published per endpoint group with numbers and block lengths (15). 429 is documented with advice to throttle, but no Retry-After, and a block can last an hour or a day (10 of 15). No SLA found (0). Generally available (10). 20+20+15+10+0+10 = 75.\n\n### Schema \u0026 documentation: Retriever +28\n\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- ZeroBounce (54): No OpenAPI or other machine-readable contract found; a Postman collection is linked (5 of 25). llms.txt lists marketing pages, and the docs have no Markdown twins (5 of 10). Endpoint pages explain timing, credits and when to use batch or file APIs (14 of 20). Parameter tables and listed status and sub-status values, including the ai_agent_mailbox sub-status added in July 2026 (10 of 15). Examples per endpoint, a sandbox and an error-code page (12 of 15). v2 paths, an API migration page and dated maintenance notices on the status page, with no API changelog (8 of 15). 5+5+14+10+12+8 = 54.\n\n### Payments \u0026 pricing: ZeroBounce +23\n\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- ZeroBounce (53): No x402, MPP or L402 (0). Per-credit prices public, from $39 for 2,000 validations (20). Freemium of 100 validations a month for business or premium domains; a card requirement isn't stated, and free webmail addresses don't qualify (15 of 20). A person signs up in a browser (0). 0+20+15+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.\n\n### Transparency \u0026 trust: ZeroBounce +14\n\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- ZeroBounce (63): Closed service under terms naming Hertza L.L.C. (ZeroBounce) of Nevada; SDKs and MCP server open source (15 of 30). The data protection page says uploaded data is never kept more than 30 days, the privacy policy of 30 June 2026 keeps account data 'as long as needed', and EU and UK DPAs are published (22 of 30). An API migration page, with no dated deprecation policy (6 of 20). A sub-processor list naming each provider and the data exchanged (16 of 20). 15+22+6+16 = 59.\n\n## Score by category\n\n| Category | Weight | Retriever | ZeroBounce | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 75 | ZeroBounce +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 82 | 54 | Retriever +28 |\n| Agent ergonomics | 13% | 75 | 69 | Retriever +6 |\n| Security \u0026 auth | 14% | 23 | 65 | ZeroBounce +42 |\n| Payments \u0026 pricing | 10% | 30 | 53 | ZeroBounce +23 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 5 | 70 | ZeroBounce +65 |\n| Transparency \u0026 trust | 7% | 49 | 63 | ZeroBounce +14 |\n| Negative events | ≤15 | -15 | 0 | |\n| **Total** | | **32 · F** | **64.6 · B** | |\n\n## Facts side by side\n\n| Fact | Retriever | ZeroBounce |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Retriever | Hertza L.L.C. (ZeroBounce) |\n| Hosted endpoint | `https://api.retriever.run/mcp` | `https://api.zerobounce.net/v2` |\n| Transports | Streamable HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under ZeroBounce's terms of use; SDKs and the MCP server are open source |\n| Tools exposed | 67 | 0 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-25 |\n| Terms last updated | 2026-08-30 | 2026-05-05 |\n| Privacy policy last updated | 2026-08-30 | 2026-06-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## How the scores have moved\n\n### Retriever\n\nNo score change since it was listed.\n\n### ZeroBounce\n\n- +2.2 on 13 November 2026: checklist\n\n## Verdicts\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**ZeroBounce.** ZeroBounce's v2 API verifies emails with detailed status and sub-status codes, publishes per-endpoint limits, a Statuspage with short incidents only in the last 90 days, SOC 2 Type 2 and ISO 27001, and $0.0195 per email at the smallest pack. The documented key travels in the query string, and there is no OpenAPI contract.\n\n## Before you call either\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### ZeroBounce\n\n1. Use the regional host (api-us or api-eu) that matches the data, and test with the sandbox addresses, which spend no credits\n2. Set `timeout` (3 to 60 seconds); slow mail servers return unknown, which is free to retry later\n3. Stay under 80,000 validations per 10 seconds and avoid repeated bad requests, which block the key for an hour\n4. Use the bulk file API for large lists instead of looping on /v2/validate\n5. Keep the key out of logs; the API takes it only as `api_key` in the URL\n\n## Questions\n\n### Which is better for AI agents, Retriever or ZeroBounce?\n\nZeroBounce scores 64.6 (B) 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 Retriever and ZeroBounce need an API key?\n\nRetriever takes an API key or an OAuth sign-in. ZeroBounce needs an API key.\n\n### Can an agent call Retriever and ZeroBounce without installing anything?\n\nYes. Retriever has a hosted endpoint at https://api.retriever.run/mcp and ZeroBounce at https://api.zerobounce.net/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json, and with the fewest tokens: https://www.anchorterminal.com/compare/retriever-vs-zerobounce.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"retriever\", \"b\": \"zerobounce\"}`. From a terminal: `anchor compare retriever zerobounce`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/retriever.json and https://www.anchorterminal.com/api/v1/tools/zerobounce.json\n\n## Other comparisons with Retriever or ZeroBounce\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 ZeroBounce](https://www.anchorterminal.com/compare/apollo-vs-zerobounce.md)\n- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)\n- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)\n- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md)\n- [Coresignal API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/coresignal-vs-zerobounce.md)\n- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)\n- [Dievio vs ZeroBounce](https://www.anchorterminal.com/compare/dievio-vs-zerobounce.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [Dropcontact API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/dropcontact-vs-zerobounce.md)\n- [Enrich Layer API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/enrich-layer-vs-zerobounce.md)\n- [Explorium AgentSource vs ZeroBounce](https://www.anchorterminal.com/compare/explorium-agentsource-vs-zerobounce.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [FullContact vs ZeroBounce](https://www.anchorterminal.com/compare/fullcontact-vs-zerobounce.md)\n- [FullEnrich API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fullenrich-vs-zerobounce.md)\n- [Gojiberry vs ZeroBounce](https://www.anchorterminal.com/compare/gojiberry-vs-zerobounce.md)\n- [Lusha API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/lusha-vs-zerobounce.md)\n- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)\n- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)\n- [ZeroBounce vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/zerobounce-vs-zoominfo.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n- [Hunter API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/hunter-vs-zerobounce.md)\n- [Fuse MCP vs ZeroBounce](https://www.anchorterminal.com/compare/fuse-mcp-vs-zerobounce.md)\n- [LeadMagic API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/leadmagic-vs-zerobounce.md)\n- [RocketReach API vs ZeroBounce](https://www.anchorterminal.com/compare/rocketreach-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": "Retriever vs ZeroBounce",
        "url": ""
      }
    ],
    "description": "ZeroBounce scores 64.6 (B) to Retriever's 32 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Retriever F 32",
      "ZeroBounce B 64.6",
      "scores"
    ],
    "h1": "Retriever vs ZeroBounce",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/retriever-vs-zerobounce",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Retriever vs ZeroBounce for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
  },
  "tokens": {
    "markdown": 4600,
    "slim": 1030
  },
  "version": 1
}
