# Crustdata API + MCP vs Retriever (slim)

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

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

Crustdata API + MCP scores 52.4 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on payments & pricing. Both do lead search.

- Crustdata API + MCP: D 52.4, rank #1083 of 1557 · https://www.anchorterminal.com/tools/crustdata.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.min.md
- Crustdata API + MCP, good for Agents that monitor companies, people, jobs or posts over time and need change notifications. Ahead on Schema & documentation, 89 against 82; Security & auth, 56 against 23; Maintenance & community, 57 against 5; Transparency & trust, 56 against 49.
- 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 Payments & pricing, 30 against 8.

| Category | Crustdata API + MCP | Retriever |
| --- | --- | --- |
| Reliability (16%) | 42 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 82 |
| Agent ergonomics (13%) | 73 | 75 |
| Security & auth (14%) | 56 | 23 |
| Payments & pricing (10%) | 8 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 5 |
| Transparency & trust (7%) | 56 | 49 |

| Fact (where they differ) | Crustdata API + MCP | Retriever |
| --- | --- | --- |
| Vendor | Crustdata | Retriever |
| Hosted endpoint | `https://api.crustdata.com` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Pricing | Pay per use | Paid |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| Terms last updated | no date given | 2026-08-30 |
| Privacy policy last updated | 2025-05-19 | 2026-08-30 |
| Terms restrict automated access | not found in the text | yes |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Maintenance & community, Crustdata API + MCP +52: Crustdata API + MCP 57 (The changelog labels every entry by month only, newest "October 2026" (NAICS and SIC on company search, `geo_polygon`, research profiles, the Usage API), with n…); 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, Crustdata API + MCP +33: Crustdata API + MCP 56 (Bearer keys, several named keys per account with active, inactive and deleted states, per-key endpoint restrictions and monthly credit caps since July 2026. OAu…); 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, Retriever +22: Crustdata API + MCP 8 (No x402, MPP or L402 (0).); Retriever 30 (No x402, MPP or L402 (0).)
- Schema & documentation, Crustdata API + MCP +7: Crustdata API + MCP 89 (Eight OpenAPI YAML files for version 2025-11-01, one per API group (account, batch, company, job, person, social_post, watch, web) (25).); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Transparency & trust, Crustdata API + MCP +7: Crustdata API + MCP 56 (Closed service.); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
