# Clay vs Retriever (slim)

> Clay scores 58.3 (C) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clay-vs-retriever.md (~4,800 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/clay-vs-retriever.json · canonical https://www.anchorterminal.com/compare/clay-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)

Clay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics. Both do lead search.

- Clay: C 58.3, rank #857 of 1557 · https://www.anchorterminal.com/tools/clay.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Clay, good for Agents building prospect lists and enriching contacts or accounts through many providers at once. Ahead on Security & auth, 48 against 23; Payments & pricing, 45 against 30; Maintenance & community, 75 against 5; Transparency & trust, 61 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; Agent ergonomics, 75 against 66.

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

| Fact (where they differ) | Clay | Retriever |
| --- | --- | --- |
| Vendor | Clay Labs Inc. | Retriever |
| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.retriever.run/mcp` |
| Transports | HTTP | Streamable HTTP |
| Pricing | Freemium | Paid |
| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | none |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| Last release | 2026-11-04 | none |
| Terms last updated | not read yet | 2026-08-30 |
| Privacy policy last updated | 2020-09-11 | 2026-08-30 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |

Why the edge:
- Maintenance & community, Clay +70: Clay 75 (clay plugin 2.35.0 on 4 November 2026, requiring CLI 1.14.0, whose tag sits on the 3 November release commit (30).); 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).)
- Security & auth, Clay +25: Clay 48 (A personal API key tied to the user's workspace access, with no scopes documented.); 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…)
- Payments & pricing, Clay +15: Clay 45 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Transparency & trust, Clay +12: Clay 61 (Closed service under the Clay Services Agreement, last updated 1 November 2026 (New York law), and a plugin repository with no licence (12 of 30).); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Agent ergonomics, Retriever +9: Clay 66 (Table queries select fields and take a limit, and searches return up to 500 per request (20 of 25).); 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…)
- Reliability, Retriever +5: Clay 40 (Graded with the hosted lines on the Public API.); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
