{
  "data": {
    "a": {
      "slug": "clearbit",
      "name": "Clearbit",
      "vendor": "HubSpot",
      "vendorUrl": "https://clearbit.com",
      "company": "hubspot.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Clearbit is a B2B data provider for company, contact and IP intelligence, acquired by HubSpot. It still runs enrichment, reveal and prospecting APIs for existing customers, and HubSpot's Breeze Intelligence carries its data for new buyers.",
      "url": "https://www.anchorterminal.com/tools/clearbit",
      "markdownUrl": "https://www.anchorterminal.com/tools/clearbit.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clearbit.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clearbit.json",
      "dns": "clearbit.grade.anchorterminal.com",
      "license": "Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand",
      "transports": [
        "http"
      ],
      "packages": [],
      "auth": "api-key",
      "authNotes": "API access is for existing Clearbit customers through their dashboard, and dashboard.clearbit.com/docs redirects to a login. The home page links only to a customer login, with no sign-up for new customers (checked 2026-10-14).",
      "pricing": "paid",
      "pricingNotes": "No public prices. clearbit.com/pricing redirects to the home page. The free tools (Free Clearbit Platform, Weekly Visitor Report, Clearbit Connect, TAM Calculator and the free Slack integration) were discontinued on 30 April 2025, and the free Logo API was shut down on 8 December 2025 (https://clearbit.com/changelog, checked 2026-10-14).",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on the public Clearbit pages (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "capabilities": [
        "lead.enrichment",
        "data.company"
      ],
      "tags": [
        "hosted",
        "not-for-agents",
        "sales-led",
        "closed-source",
        "enrichment",
        "status-page",
        "soc2"
      ],
      "lastRelease": "2025-12-08",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 15.6,
        "grade": "F",
        "agentReady": false,
        "rank": 1515,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 23,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 0,
          "maintenance": 4,
          "payments": 0,
          "reliability": 40,
          "schema": 0,
          "security": 5,
          "transparency": 73
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-11"
        },
        "negative": 0,
        "verdict": "There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.",
        "bestFor": "Only for teams that already hold a Clearbit contract.",
        "strengths": [
          "Public status page with 22 components and an incident feed that posts partial incidents",
          "Dated sunset notices with months of warning, such as the Logo API",
          "Sub-processor page names nine providers with purpose and country and promises 30 days' notice of changes",
          "Privacy policy updated 31 August 2026 and a trust page claiming SOC 2 Type 2"
        ],
        "weaknesses": [
          "No public API or MCP server an outside agent can call",
          "No sign-up or public prices, and the home page links only to a customer login",
          "Free tools retired on 30 April 2025 and the Logo API after 8 December 2025",
          "No security.txt, and the help centre sits behind a bot check"
        ],
        "agentNotes": [
          "Don't plan to call Clearbit. Hand the task to a person with an existing Clearbit account, or use HubSpot's Breeze Intelligence through HubSpot",
          "Replace logo.clearbit.com links, which stopped working after 8 December 2025"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 1.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 15.6
          }
        ],
        "editorialScores": {
          "ergonomics": 0,
          "maintenance": 4,
          "payments": 0,
          "reliability": 40,
          "schema": 0,
          "security": 5,
          "transparency": 73
        },
        "provenanceScore": 73,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-11",
            "maintenance": "2026-11-11",
            "payments": "2026-11-11",
            "reliability": "2026-11-11",
            "schema": "2026-11-11",
            "security": "2026-11-11",
            "transparency": "2026-11-11"
          },
          "last": "2026-11-11",
          "lastMoved": "2026-11-11",
          "oldest": "2026-11-11",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.enrichment",
        "tool": "https://letme.dev/clearbit"
      },
      "sameCompany": [
        "hubspot-mcp"
      ],
      "area": "web-data",
      "provenance": {
        "legalEntity": "HubSpot, Inc.",
        "domain": "clearbit.com",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://clearbit.com/legal",
        "privacy": "https://clearbit.com/privacy-policy",
        "statusPage": "https://status.clearbit.com",
        "changelog": "https://clearbit.com/changelog",
        "securityTxt": "none",
        "checked": "2026-11-11",
        "notes": [
          "The terms were last updated on 30 May 2025 and the privacy policy on 31 August 2026 (both re-read 2026-11-11). Both name HubSpot, Inc. under its Clearbit brand; the terms say APIHub, Inc. dba Clearbit assigned them to HubSpot.",
          "clearbit.com/.well-known/security.txt returns 404 (re-read 2026-11-11; on 14 October it answered with an HTML page).",
          "help.clearbit.com answered with a Cloudflare bot check on 14 and 17 October, so its article on buying Clearbit wasn't read. A search result quoted it as saying new standalone subscriptions are no longer offered, which we couldn't confirm first-hand.",
          "status.clearbit.com is an Atlassian Statuspage (clearbit.statuspage.io), read through its page and /history.atom on 2026-11-11.",
          "No RDAP lookup was made for clearbit.com.",
          "robots.txt on clearbit.com (200 on 2026-11-11) disallows only /reset, with no Content-Signal line. The terms carry no clause on automated access."
        ],
        "score": 73
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/clearbit.json",
      "live": {
        "slug": "clearbit",
        "vendorStatus": {
          "page": "https://status.clearbit.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T21:50:40.461420927Z"
        },
        "securityTxt": {
          "url": "https://clearbit.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:29:14.540609723Z"
        },
        "domain": {
          "domain": "clearbit.com",
          "registered": "2003-07-04",
          "source": "https://rdap.verisign.com/com/v1/domain/clearbit.com",
          "checkedAt": "2026-11-15T15:30:41.538803328Z"
        },
        "pages": [
          {
            "url": "https://clearbit.com/changelog",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-18T21:34:53.043369552Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "404e1ac5a18e"
          },
          {
            "url": "https://clearbit.com/privacy-policy",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-18T21:34:58.325861628Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d77014da379a"
          },
          {
            "url": "https://clearbit.com/legal",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-18T21:34:55.22843372Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "028252d0e504"
          }
        ],
        "updatedAt": "2026-11-18T21:50:40.461420927Z"
      }
    },
    "answer": "Retriever scores 32 (F) on agent readiness against Clearbit's 15.6 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency \u0026 trust.",
    "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": 82,
        "category": "schema",
        "leads": "retriever",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Graded on the interface an outside agent can use. The API docs sit behind the customer login (per the 17 October check) and there is no sign-up, so the contract, description, typed-input, example and versioning lines score nothing. clearbit.com/llms.txt returns 404 on 11 November (0). This says nothing about the service for existing customers.",
          "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": 0,
          "b": 82
        }
      },
      {
        "by": 75,
        "category": "ergonomics",
        "leads": "retriever",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).",
          "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": 0,
          "b": 75
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "retriever",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). No public prices, and /pricing redirected to the home page on 17 October (0). The free tools ended on 30 April 2025 (0). No sign-up route at all (0). 0+0+0+0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.",
          "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": 0,
          "b": 30
        }
      },
      {
        "by": 24,
        "category": "transparency",
        "leads": "clearbit",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service under terms last updated 30 May 2025 that name HubSpot, Inc., to which APIHub, Inc. dba Clearbit assigned them, re-read on 11 November (15). The privacy policy, last updated 31 August 2026, lists public, customer and third-party sources, and the trust page commits to deleting a terminated customer's account associations within 90 days (22 of 30). Dated sunset notices with months of warning, such as the Logo API announced in February 2025 for December (16 of 20). The sub-processor page, updated as of May 2026, names nine sub-processors (AWS, Google Cloud, FullStory, Hotjar, Mailgun, Mode Analytics, SquadCast, Sentry, Zendesk) with purpose and country, all in the United States, and promises 30 days' notice before a new one starts (20 of 20). 15 + 22 + 16 + 20 = 73.",
          "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": 73,
          "b": 49
        }
      },
      {
        "by": 18,
        "category": "security",
        "leads": "retriever",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Graded on the interface an outside agent can use, so the credential, least-privilege, injection and audit lines score nothing (0). The trust page, re-read on 11 November, says an independent auditor assessed the programme against the SOC 2 Trust Services Criteria, that Clearbit is SOC 2 Type 2 compliant, and that third-party experts run penetration tests every year. No report is published, security.txt returns 404, and no bug bounty, disclosure policy or reporting route was found, so the claim is a bare SOC 2 claim, scored 5 of 20 as for AssemblyAI (a SOC 2 Type II claim with penetration tests and no route), Fabric and OneUp. 0+0+0+0+5 = 5.",
          "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": 5,
          "b": 23
        }
      },
      {
        "by": 5,
        "category": "reliability",
        "leads": "retriever",
        "name": "Reliability",
        "reasons": {
          "a": "Read with the hosted lines. An Atlassian Statuspage with 22 components and incident history, all operational on 11 November (20). In the 90 days from 13 August its feed has two incidents. On 1 September, for 20 minutes, \"some users experienced authentication errors that prevented them from logging in or using the Clearbit platform and APIs\", partial by its own text. From 18 to 23 September Salesforce syncs failed, one integration. Both read as minor, so minor only (20 of 30, the checklist value; the earlier 10 was reduced from 20 because the history covers a service closed to new users, which the checklist has no step for). No published limits for an outside agent (0). No overload or retry guidance on a public page (0). No SLA found (0). The standalone service is closed to new sign-ups, so the general-availability line scores nothing (0). 20+20+0+0+0+0 = 40.",
          "b": "No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10)."
        },
        "scores": {
          "a": 40,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "HubSpot",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.retriever.run/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2025-12-08",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2025-05-30",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-31",
        "b": "2026-08-30",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "1.5/5 (4)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Retriever scores 32 (F) on agent readiness against Clearbit's 15.6 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency \u0026 trust.",
        "question": "Which is better for AI agents, Clearbit or Retriever?"
      },
      {
        "answer": "Clearbit needs an API key. Retriever takes an API key or an OAuth sign-in.",
        "question": "Do Clearbit and Retriever need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Clearbit. Retriever has a hosted endpoint at https://api.retriever.run/mcp.",
        "question": "Can an agent call Clearbit and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Transparency \u0026 trust, 73 against 49"
        ],
        "also": [
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "Only for teams that already hold a Clearbit contract.",
        "slug": "clearbit",
        "watchFor": "No public API or MCP server an outside agent can call"
      },
      {
        "aheadOn": [
          "Reliability, 45 against 40",
          "Schema \u0026 documentation, 82 against 0",
          "Agent ergonomics, 75 against 0",
          "Security \u0026 auth, 23 against 5",
          "Payments \u0026 pricing, 30 against 0"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "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": {
      "clearbit": [
        {
          "causes": [
            "correction"
          ],
          "date": "2026-11-11",
          "delta": 1.5,
          "from": 14.1,
          "fromGrade": "F",
          "to": 15.6,
          "toGrade": "F"
        },
        {
          "causes": [
            "correction"
          ],
          "date": "2026-10-28",
          "delta": -0.1,
          "from": 14.2,
          "fromGrade": "F",
          "to": 14.1,
          "toGrade": "F"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.1,
          "from": 14.1,
          "fromGrade": "F",
          "to": 14.2,
          "toGrade": "F"
        }
      ],
      "retriever": null
    },
    "job": {
      "capability": "lead.enrichment",
      "name": "Lead enrichment"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-retriever.json",
        "title": "Apollo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-retriever.json",
        "title": "Clay vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
        "title": "Coresignal API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-retriever.json",
        "title": "Crustdata API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-retriever.json",
        "title": "Dievio vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json",
        "title": "Enrich Layer API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.json",
        "title": "Explorium AgentSource vs Retriever",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json",
        "title": "FullEnrich API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json",
        "title": "Fuse MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json",
        "title": "Gojiberry vs Retriever",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json",
        "title": "LeadMagic API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-retriever.json",
        "title": "Lusha API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-retriever.json",
        "title": "Prospeo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach.json",
        "title": "Retriever vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo.json",
        "title": "Retriever vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-clearbit.json",
        "title": "Apollo API + MCP vs Clearbit",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-clearbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-clearbit.json",
        "title": "Clay vs Clearbit",
        "url": "https://www.anchorterminal.com/compare/clay-vs-clearbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal.json",
        "title": "Clearbit vs Coresignal API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-coresignal"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-crustdata.json",
        "title": "Clearbit vs Crustdata API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-crustdata"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-databar.json",
        "title": "Clearbit vs Databar",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-databar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-dievio.json",
        "title": "Clearbit vs Dievio",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-dievio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.json",
        "title": "Clearbit vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer.json",
        "title": "Clearbit vs Enrich Layer API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.json",
        "title": "Clearbit vs Explorium AgentSource",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.json",
        "title": "Clearbit vs FullContact",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.json",
        "title": "Clearbit vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.json",
        "title": "Clearbit vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-gojiberry.json",
        "title": "Clearbit vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-gojiberry"
      },
      {
        "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-leadmagic.json",
        "title": "Clearbit vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-lusha.json",
        "title": "Clearbit vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.json",
        "title": "Clearbit vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-prospeo.json",
        "title": "Clearbit vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-rocketreach.json",
        "title": "Clearbit vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-rocketreach"
      },
      {
        "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/clearbit-vs-zoominfo.json",
        "title": "Clearbit vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json",
        "title": "FullContact vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
        "title": "Retriever vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 5,
        "clearbit": 40,
        "edge": "retriever",
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 82,
        "clearbit": 0,
        "edge": "retriever",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 75,
        "clearbit": 0,
        "edge": "retriever",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 18,
        "clearbit": 5,
        "edge": "retriever",
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 30,
        "clearbit": 0,
        "edge": "retriever",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "clearbit": 4,
        "edge": "retriever",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 24,
        "clearbit": 73,
        "edge": "clearbit",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "Retriever scores 32 (F) on agent readiness against Clearbit's 15.6 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency \u0026 trust. Both do lead enrichment.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "clearbit": "There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.",
      "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/clearbit-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.min.md"
  },
  "markdown": "Retriever scores 32 (F) on agent readiness against Clearbit's 15.6 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency \u0026 trust. Both do lead enrichment.\n\n- Clearbit: grade F, 15.6/100, rank #1515 of 1557. Markdown https://www.anchorterminal.com/tools/clearbit.md · JSON https://www.anchorterminal.com/api/v1/tools/clearbit.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### Clearbit (F)\n\nGood for: Only for teams that already hold a Clearbit contract.\n\nAhead on:\n- Transparency \u0026 trust, 73 against 49\n\nAlso in its favour:\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: No public API or MCP server an outside agent can call\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- Reliability, 45 against 40\n- Schema \u0026 documentation, 82 against 0\n- Agent ergonomics, 75 against 0\n- Security \u0026 auth, 23 against 5\n- Payments \u0026 pricing, 30 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\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### Schema \u0026 documentation: Retriever +82\n\n- Clearbit (0): Graded on the interface an outside agent can use. The API docs sit behind the customer login (per the 17 October check) and there is no sign-up, so the contract, description, typed-input, example and versioning lines score nothing. clearbit.com/llms.txt returns 404 on 11 November (0). This says nothing about the service for existing customers.\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### Agent ergonomics: Retriever +75\n\n- Clearbit (0): Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).\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### Payments \u0026 pricing: Retriever +30\n\n- Clearbit (0): No x402, MPP or L402 (0). No public prices, and /pricing redirected to the home page on 17 October (0). The free tools ended on 30 April 2025 (0). No sign-up route at all (0). 0+0+0+0 = 0. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.\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: Clearbit +24\n\n- Clearbit (73): Closed service under terms last updated 30 May 2025 that name HubSpot, Inc., to which APIHub, Inc. dba Clearbit assigned them, re-read on 11 November (15). The privacy policy, last updated 31 August 2026, lists public, customer and third-party sources, and the trust page commits to deleting a terminated customer's account associations within 90 days (22 of 30). Dated sunset notices with months of warning, such as the Logo API announced in February 2025 for December (16 of 20). The sub-processor page, updated as of May 2026, names nine sub-processors (AWS, Google Cloud, FullStory, Hotjar, Mailgun, Mode Analytics, SquadCast, Sentry, Zendesk) with purpose and country, all in the United States, and promises 30 days' notice before a new one starts (20 of 20). 15 + 22 + 16 + 20 = 73.\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### Security \u0026 auth: Retriever +18\n\n- Clearbit (5): Graded on the interface an outside agent can use, so the credential, least-privilege, injection and audit lines score nothing (0). The trust page, re-read on 11 November, says an independent auditor assessed the programme against the SOC 2 Trust Services Criteria, that Clearbit is SOC 2 Type 2 compliant, and that third-party experts run penetration tests every year. No report is published, security.txt returns 404, and no bug bounty, disclosure policy or reporting route was found, so the claim is a bare SOC 2 claim, scored 5 of 20 as for AssemblyAI (a SOC 2 Type II claim with penetration tests and no route), Fabric and OneUp. 0+0+0+0+5 = 5.\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### Reliability: Retriever +5\n\n- Clearbit (40): Read with the hosted lines. An Atlassian Statuspage with 22 components and incident history, all operational on 11 November (20). In the 90 days from 13 August its feed has two incidents. On 1 September, for 20 minutes, \"some users experienced authentication errors that prevented them from logging in or using the Clearbit platform and APIs\", partial by its own text. From 18 to 23 September Salesforce syncs failed, one integration. Both read as minor, so minor only (20 of 30, the checklist value; the earlier 10 was reduced from 20 because the history covers a service closed to new users, which the checklist has no step for). No published limits for an outside agent (0). No overload or retry guidance on a public page (0). No SLA found (0). The standalone service is closed to new sign-ups, so the general-availability line scores nothing (0). 20+20+0+0+0+0 = 40.\n- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).\n\n## Score by category\n\n| Category | Weight | Clearbit | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 40 | 45 | Retriever +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 0 | 82 | Retriever +82 |\n| Agent ergonomics | 13% | 0 | 75 | Retriever +75 |\n| Security \u0026 auth | 14% | 5 | 23 | Retriever +18 |\n| Payments \u0026 pricing | 10% | 0 | 30 | Retriever +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 4 | 5 | Retriever +1 |\n| Transparency \u0026 trust | 7% | 73 | 49 | Clearbit +24 |\n| Negative events | ≤15 | 0 | -15 | |\n| **Total** | | **15.6 · F** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | Clearbit | Retriever |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HubSpot | Retriever |\n| Hosted endpoint | no (local only) | `https://api.retriever.run/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand | none |\n| Tools exposed | none | 67 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2025-12-08 | none |\n| Terms last updated | 2025-05-30 | 2026-08-30 |\n| Privacy policy last updated | 2026-08-31 | 2026-08-30 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | 1.5/5 (4) | none |\n\n## How the scores have moved\n\n### Clearbit\n\n- +1.5 on 11 November 2026: correction\n- -0.1 on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n### Retriever\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Clearbit.** There is no public API or MCP server an outside agent can call today. Clearbit's APIs still run for existing customers behind a login, and its free tools and Logo API were retired in 2025. HubSpot's Breeze Intelligence is the route for new buyers, through HubSpot rather than Clearbit.\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### Clearbit\n\n1. Don't plan to call Clearbit. Hand the task to a person with an existing Clearbit account, or use HubSpot's Breeze Intelligence through HubSpot\n2. Replace logo.clearbit.com links, which stopped working after 8 December 2025\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, Clearbit or Retriever?\n\nRetriever scores 32 (F) on agent readiness against Clearbit's 15.6 (F), and leads in 6 of 7 scored categories. Clearbit leads on transparency \u0026 trust.\n\n### Do Clearbit and Retriever need an API key?\n\nClearbit needs an API key. Retriever takes an API key or an OAuth sign-in.\n\n### Can an agent call Clearbit and Retriever without installing anything?\n\nNo hosted endpoint is listed for Clearbit. Retriever has a hosted endpoint at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clearbit-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clearbit-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clearbit\", \"b\": \"retriever\"}`. From a terminal: `anchor compare clearbit retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clearbit.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with Clearbit or Retriever\n\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)\n- [Crustdata API + MCP vs Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)\n- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)\n- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)\n- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)\n- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)\n- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md)\n- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)\n- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)\n- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)\n- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)\n- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)\n- [Apollo API + MCP vs Clearbit](https://www.anchorterminal.com/compare/apollo-vs-clearbit.md)\n- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)\n- [Clearbit vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-coresignal.md)\n- [Clearbit vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-crustdata.md)\n- [Clearbit vs Databar](https://www.anchorterminal.com/compare/clearbit-vs-databar.md)\n- [Clearbit vs Dievio](https://www.anchorterminal.com/compare/clearbit-vs-dievio.md)\n- [Clearbit vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-dropcontact.md)\n- [Clearbit vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-enrich-layer.md)\n- [Clearbit vs Explorium AgentSource](https://www.anchorterminal.com/compare/clearbit-vs-explorium-agentsource.md)\n- [Clearbit vs FullContact](https://www.anchorterminal.com/compare/clearbit-vs-fullcontact.md)\n- [Clearbit vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-fullenrich.md)\n- [Clearbit vs Fuse MCP](https://www.anchorterminal.com/compare/clearbit-vs-fuse-mcp.md)\n- [Clearbit vs Gojiberry](https://www.anchorterminal.com/compare/clearbit-vs-gojiberry.md)\n- [Clearbit vs Hunter API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-hunter.md)\n- [Clearbit vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-leadmagic.md)\n- [Clearbit vs Lusha API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-lusha.md)\n- [Clearbit vs People Data Labs](https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.md)\n- [Clearbit vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-prospeo.md)\n- [Clearbit vs RocketReach API](https://www.anchorterminal.com/compare/clearbit-vs-rocketreach.md)\n- [Clearbit vs ZeroBounce](https://www.anchorterminal.com/compare/clearbit-vs-zerobounce.md)\n- [Clearbit vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-zoominfo.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Clearbit vs Retriever",
        "url": ""
      }
    ],
    "description": "Retriever scores 32 (F) to Clearbit's 15.6 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Clearbit F 15.6",
      "Retriever F 32",
      "scores"
    ],
    "h1": "Clearbit vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/clearbit-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Clearbit vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/clearbit-vs-retriever"
  },
  "tokens": {
    "markdown": 4500,
    "slim": 980
  },
  "version": 1
}
