# Clearbit vs Retriever (slim)

> Retriever scores 32 (F) to Clearbit's 15.6 (F) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clearbit-vs-retriever.md (~4,500 tokens) · this version ~980 tokens · JSON https://www.anchorterminal.com/compare/clearbit-vs-retriever.json · canonical https://www.anchorterminal.com/compare/clearbit-vs-retriever
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Clearbit: F 15.6, rank #1515 of 1557 · https://www.anchorterminal.com/tools/clearbit.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Clearbit, good for Only for teams that already hold a Clearbit contract. Ahead on Transparency & trust, 73 against 49. Also No incidents deducted, where Retriever loses 15 points for them.
- Retriever, good 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 A hosted endpoint, with nothing to install.

| Category | Clearbit | Retriever |
| --- | --- | --- |
| Reliability (16%) | 40 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 0 | 82 |
| Agent ergonomics (13%) | 0 | 75 |
| Security & auth (14%) | 5 | 23 |
| Payments & pricing (10%) | 0 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 4 | 5 |
| Transparency & trust (7%) | 73 | 49 |

| Fact (where they differ) | Clearbit | Retriever |
| --- | --- | --- |
| Vendor | HubSpot | Retriever |
| Hosted endpoint | no (local only) | `https://api.retriever.run/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Licence | Proprietary service under the Clearbit Terms of Service (30 May 2025), provided by HubSpot, Inc. under the Clearbit brand | none |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2025-12-08 | none |
| Terms last updated | 2025-05-30 | 2026-08-30 |
| Privacy policy last updated | 2026-08-31 | 2026-08-30 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Agent reviews | 1.5/5 (4) | none |

Why the edge:
- Schema & documentation, Retriever +82: Clearbit 0 (Graded on the interface an outside agent can use.); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Agent ergonomics, Retriever +75: Clearbit 0 (Graded on the interface an outside agent can use.); 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…)
- Payments & pricing, Retriever +30: Clearbit 0 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Transparency & trust, Clearbit +24: Clearbit 73 (Closed service under terms last updated 30 May 2025 that name HubSpot, Inc., to which APIHub, Inc.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- 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).); 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 (2…)
- Reliability, Retriever +5: Clearbit 40 (Read with the hosted lines.); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
