Head to head · Lead enrichment · October 2026 research run

Clearbit vs Retriever

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 & trust. Both do lead enrichment.

Best lead, contact and company data APIs for AI agents · All 253 leads comparisons

Which one, for what

Clearbit F

Best for Only for teams that already hold a Clearbit contract.

Ahead on

  • Transparency & trust, 73 against 49

Also in its favour

  • No incidents deducted, where Retriever loses 15 points for them

Watch for

No public API or MCP server an outside agent can call

Retriever F

Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

Ahead on

  • Reliability, 45 against 40
  • Schema & documentation, 82 against 0
  • Agent ergonomics, 75 against 0
  • Security & auth, 23 against 5
  • Payments & pricing, 30 against 0

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Retriever +82

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.

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).

Agent ergonomics Retriever +75

Clearbit 0

Graded on the interface an outside agent can use. With none open to a new user, every line scores nothing (0).

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).

Payments & pricing Retriever +30

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.

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).

Transparency & trust Clearbit +24

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.

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).

Security & auth Retriever +18

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.

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).

Reliability Retriever +5

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.

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 & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).

Score by category

CategoryWeightClearbitRetrieverEdge
Reliability16%4045Retriever +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%082Retriever +82
Agent ergonomics13%075Retriever +75
Security & auth14%523Retriever +18
Payments & pricing10%030Retriever +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%45Retriever +1
Transparency & trust7%7349Clearbit +24
Negative events≤150-15
TotalF 15.6/100F 32/100

Facts side by side

FactClearbitRetriever
KindHTTP APIHTTP API
VendorHubSpotRetriever
Hosted endpointno (local only)https://api.retriever.run/mcp
TransportsHTTPStreamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brandnone
Tools exposednone67
Read-only variant documentednoyes
llms.txtnoyes
Last release2025-12-08none
Terms last updated2025-05-302026-08-30
Privacy policy last updated2026-08-312026-08-30
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews1.5/5 (4)none

How the scores have moved

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.

Before you call either

Clearbit

  1. 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
  2. Replace logo.clearbit.com links, which stopped working after 8 December 2025

Retriever

  1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
  2. 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
  3. Run getEmail, getPhoneNumber and webResearch through service_batch_execute, even for one person; service_execute refuses them
  4. Check credits before a paid run, and call service_inspect for a service's thingsToKnow and credit cost before executing it
  5. 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

Questions

Which is better for AI agents, Clearbit or Retriever?

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 & trust.

Do Clearbit and Retriever need an API key?

Clearbit needs an API key. Retriever takes an API key or an OAuth sign-in.

Can an agent call Clearbit and Retriever without installing anything?

No hosted endpoint is listed for Clearbit. Retriever has a hosted endpoint at https://api.retriever.run/mcp.

Other comparisons with Clearbit or Retriever

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.