# Enrich Layer API + MCP vs Retriever (slim)

> Enrich Layer scores 61.2 (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/enrich-layer-vs-retriever.md (~5,050 tokens) · this version ~1,080 tokens · JSON https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json · canonical https://www.anchorterminal.com/compare/enrich-layer-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)

Enrich Layer API + MCP scores 61.2 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on agent ergonomics. Both do lead search.

- Enrich Layer API + MCP: C 61.2, rank #737 of 1557 · https://www.anchorterminal.com/tools/enrich-layer.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Enrich Layer API + MCP, good for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription. Ahead on Reliability, 77 against 45; Security & auth, 40 against 23; Payments & pricing, 60 against 30; Maintenance & community, 26 against 5; Transparency & trust, 59 against 49. Also Runs on your own machine; Free to start without a card; 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 Agent ergonomics, 75 against 68.

| Category | Enrich Layer API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 77 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 82 |
| Agent ergonomics (13%) | 68 | 75 |
| Security & auth (14%) | 40 | 23 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 26 | 5 |
| Transparency & trust (7%) | 59 | 49 |

| Fact (where they differ) | Enrich Layer API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Enrich Layer | Retriever |
| Hosted endpoint | `https://enrichlayer.com/api/v2` | `https://api.retriever.run/mcp` |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Paid |
| Licence | MIT | none |
| Tools exposed | 25 | 67 |
| Read-only variant documented | no | yes |
| Last release | 2026-06-19 | none |
| Terms last updated | 2025-06-09 | 2026-08-30 |
| Privacy policy last updated | 2025-06-09 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 0 stars, 26 npm/wk | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, Enrich Layer API + MCP +32: Enrich Layer API + MCP 77 (Cachet status page at status.enrichlayer.com with a component per endpoint under School, Company, People, Contact, Jobs, Search and Meta, plus Web (20).); Retriever 45 (No status page found, linked from neither the site nor the docs (0), so no incident history to read (5).)
- Payments & pricing, Enrich Layer API + MCP +30: Enrich Layer API + MCP 60 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Maintenance & community, Enrich Layer API + MCP +21: Enrich Layer API + MCP 26 (Newest MCP release 0.3.0, tagged on 12 June and published to npm on 19 June 2026 per the 1 October check, 138 days before this check (10).); 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, Enrich Layer API + MCP +17: Enrich Layer API + MCP 40 (One secret key per user, sent as a bearer token.); 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…)
- Transparency & trust, Enrich Layer API + MCP +10: Enrich Layer API + MCP 59 (The MCP server is MIT, the API is closed with terms (9 June 2025) naming Vertical Int, Inc.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Agent ergonomics, Retriever +7: Enrich Layer API + MCP 68 (25 MCP tools, all compact, no toolsets.); 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…)
