# Crustdata API + MCP vs Retriever

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

- Canonical: https://www.anchorterminal.com/compare/crustdata-vs-retriever
- Markdown: https://www.anchorterminal.com/compare/crustdata-vs-retriever.md (~4,500 tokens)
- Slim: https://www.anchorterminal.com/compare/crustdata-vs-retriever.min.md (~930 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/crustdata-vs-retriever.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

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: grade D, 52.4/100, rank #1083 of 1557. Markdown https://www.anchorterminal.com/tools/crustdata.md · JSON https://www.anchorterminal.com/api/v1/tools/crustdata.json
- Retriever: grade F, 32/100, rank #1455 of 1557. Markdown https://www.anchorterminal.com/tools/retriever.md · JSON https://www.anchorterminal.com/api/v1/tools/retriever.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 253 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Crustdata API + MCP (D)

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

Watch for: No status page and no SLA

### Retriever (F)

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

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

### 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 no exact dates or feed, and Crustdata publishes no SDK, MCP package or other dated source of its own. Read as the Zoho listings read month-only entries, dated to the month, all of October lies 4 to 34 days back, within 90 days but not shown within 30 (20). Nine entries fall in September and October, months wholly inside the 90 days from 6 August (20). Detailed public changelog, and we didn't test support (12 of 15). The only registry entry found on 1 October sat under a personal GitHub namespace, and we found no official SDKs (0). Versioned specs are current. No packages to judge (5 of 10). 20 + 20 + 12 + 0 + 5 = 57.
- 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). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.

### 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. OAuth for the MCP (28 of 30). Per-key endpoint limits give least privilege. Watchers create standing jobs, and the MCP docs don't separate read and write tools or ask for confirmation (12 of 20). Live web fetch, web search and social posts return untrusted text, and we found no prompt-injection guidance (2 of 15). Usage and logs filterable by key, a usage events API from October 2026, and `X-Credits-Used` on every response (14 of 15). No security.txt, bug bounty, disclosure policy or certification found (0 of 20).
- 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).

### Payments & pricing: Retriever +22

- Crustdata API + MCP (8): No x402, MPP or L402 (0). Credit costs per endpoint and field are public, but no dollar price per credit is, and enterprise plans start at "four figures a month" through sales. We gave 5 rather than 0 because an agent can work out relative cost from the public credit table (5). Every new self-serve account now starts with $20 in free credits, but no page we read says whether signing up needs a card, so the line isn't met on the evidence (0). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
- 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).

### 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). llms.txt with Markdown twins (10). Endpoint pages explain cost and when to search versus enrich (17 of 20). Typed filter trees with documented operators (12 of 15). Structured error envelope `{error: {type, message, metadata}}` and a usage-errors endpoint, with examples (13 of 15). Date-pinned API versions and a detailed changelog. Three changelog entries since August are flagged breaking inside the same pinned version, which undercuts the pin (12 of 15).
- 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).

### Transparency & trust: Crustdata API + MCP +7

- Crustdata API + MCP (56): Closed service. The terms are a website-use notice naming CrustData Inc. (California), while the privacy policy names Crustdata Technologies Inc., and we found no API terms (8 of 30). The privacy policy (updated 19 May 2025) covers people in the datasets, cites consent, contract and legitimate interests, and runs an opt-out portal that removes data within 30 days and blocks it from coming back. Retention has no periods and no DPA is mentioned (15 of 30). Date-pinned versions and migration guides, but breaking changes inside the pinned version with no dated notice (8 of 20). US transfers stated, no subprocessor list (5 of 20).
- 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).

## Score by category

| Category | Weight | Crustdata API + MCP | Retriever | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 42 | 45 | Retriever +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 82 | Crustdata API + MCP +7 |
| Agent ergonomics | 13% | 73 | 75 | Retriever +2 |
| Security & auth | 14% | 56 | 23 | Crustdata API + MCP +33 |
| Payments & pricing | 10% | 8 | 30 | Retriever +22 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 57 | 5 | Crustdata API + MCP +52 |
| Transparency & trust | 7% | 56 | 49 | Crustdata API + MCP +7 |
| Negative events | ≤15 | -3 | -15 | |
| **Total** | | **52.4 · D** | **32 · F** | |

## Facts side by side

| Fact | Crustdata API + MCP | Retriever |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Crustdata | Retriever |
| Hosted endpoint | `https://api.crustdata.com` | `https://api.retriever.run/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Terms last updated | no date given | 2026-08-30 |
| Privacy policy last updated | 2025-05-19 | 2026-08-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Crustdata API + MCP

- +0.4 on 13 November 2026: checklist
- -1.5 on 4 November 2026: correction, time
- +0.1 on 28 October 2026: checklist

### Retriever

No score change since it was listed.

## Verdicts

**Crustdata API + MCP.** Per-field credit prices readable per account, `X-Credits-Used` on every response, per-key caps and $20 in free credits for new self-serve accounts. No status page, no SLA, no dollar price per credit, and changes that refuse earlier valid requests posted only after they shipped.

**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

### Crustdata API + MCP

1. Always send `x-api-version: 2025-11-01`. Unpinned calls get the latest version
2. Call `/account/endpoints` first to see what your plan enables and what each field costs
3. Ask only for the premium field groups you need, since each one bills
4. Poll `GET /batch/{id}` before submitting more batch jobs. Active jobs count against a cap of 5 to 30
5. Read the `crustdata://catalog` resource before calling MCP tools

### 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, Crustdata API + MCP or Retriever?

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.

### Do Crustdata API + MCP and Retriever need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Crustdata API + MCP and Retriever without installing anything?

Yes. Crustdata API + MCP has a hosted endpoint at https://api.crustdata.com and Retriever at https://api.retriever.run/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/crustdata-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crustdata-vs-retriever.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "crustdata", "b": "retriever"}`. From a terminal: `anchor compare crustdata retriever`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crustdata.json and https://www.anchorterminal.com/api/v1/tools/retriever.json

## Other comparisons with Crustdata API + MCP or Retriever

- [Apollo API + MCP vs Crustdata API + MCP](https://www.anchorterminal.com/compare/apollo-vs-crustdata.md)
- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)
- [Clay vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clay-vs-crustdata.md)
- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)
- [Coresignal API + MCP vs Crustdata API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-crustdata.md)
- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)
- [Crustdata API + MCP vs Databar](https://www.anchorterminal.com/compare/crustdata-vs-databar.md)
- [Crustdata API + MCP vs Dievio](https://www.anchorterminal.com/compare/crustdata-vs-dievio.md)
- [Crustdata API + MCP vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-enrich-layer.md)
- [Crustdata API + MCP vs Explorium AgentSource](https://www.anchorterminal.com/compare/crustdata-vs-explorium-agentsource.md)
- [Crustdata API + MCP vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-fullenrich.md)
- [Crustdata API + MCP vs Fuse MCP](https://www.anchorterminal.com/compare/crustdata-vs-fuse-mcp.md)
- [Crustdata API + MCP vs Gojiberry](https://www.anchorterminal.com/compare/crustdata-vs-gojiberry.md)
- [Crustdata API + MCP vs Hunter API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-hunter.md)
- [Crustdata API + MCP vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-leadmagic.md)
- [Crustdata API + MCP vs Lusha API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-lusha.md)
- [Crustdata API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/crustdata-vs-people-data-labs.md)
- [Crustdata API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-prospeo.md)
- [Crustdata API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/crustdata-vs-rocketreach.md)
- [Crustdata API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-zoominfo.md)
- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)
- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)
- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)
- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)
- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md)
- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)
- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)
- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)
- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)
- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)
- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)
- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)
- [Clearbit vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-crustdata.md)
- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)
- [Crustdata API + MCP vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-dropcontact.md)
- [Crustdata API + MCP vs FullContact](https://www.anchorterminal.com/compare/crustdata-vs-fullcontact.md)
- [Crustdata API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/crustdata-vs-zerobounce.md)
- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)
- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)
- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)
- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)
- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
