# Retriever (slim)

> Retriever is a hosted prospecting agent that finds and qualifies companies and contacts, enriches them with emails and phone numbers, and runs email and LinkedIn outreach, through a REST API and a remote MCP server.

- Full: https://www.anchorterminal.com/tools/retriever.md (~7,150 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/tools/retriever.json · canonical https://www.anchorterminal.com/tools/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 · pricing https://www.anchorterminal.com/tools/retriever#pricing · reviews https://www.anchorterminal.com/tools/retriever#reviews
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

**F · 32/100 · rank #1455 of 1557 · #21 in Lead & company data · not agent-ready · confidence medium** · WARNING: Breaks the rules of the platforms it acts on


Assessment: 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.

## Facts

- Kind: HTTP API · vendor: Retriever · category: Lead & company data · legal entity: Retriever · provenance 54/100
- Endpoint: `https://api.retriever.run/mcp` (Streamable HTTP)
- Auth: OAuth or key · pricing: Paid · x402: no · licence: unknown
- Benchmark probes: not run yet, so Performance is pending
- Live, from our pollers (not part of the score): up at 2026-11-18 21:51 UTC · uptime 30 days 100.0% (172 probes) · p50 201 ms · p95 385 ms over 24 hours
- Surface listed: The REST API at api.retriever.run and the remote MCP server at api.retriever.run/mcp, read from docs.retriever.run, its llms.txt and OpenAPI file, and retriever.run on 18 November 2026. No account was made and no tool was called. An unauthenticated GET to the MCP endpoint answered 401 with OAuth metadata
- Which Retriever: retriever.run, a go-to-market agent sold to B2B sales teams. Not NVIDIA NeMo Retriever, which is listed separately, and not an Anthropic product, whatever its launch announcement called it
- Runs, Go and Services: Runs build qualified tables of companies or people in a workspace; Go answers one question in a JSON Schema you give; Services are single calls such as finding an email, searching LinkedIn people or scraping a page
- Plays and sequences: A play finds leads on a cadence, qualifies them and contacts one person per account through a sequence of LinkedIn and email steps, with autopilot delivery or a review queue
- Data sources: 30 or more sources named on its pages, among them Hunter, FullEnrich, Lusha, Fiber AI, Crustdata and Exa, with LinkedIn, X, Instagram, Reddit and TikTok searches
- Rate limits: Per key and per class over a one-minute window, 30 heavy (runs and Go), 120 services and 600 reads or MCP messages, all keys of a user capped at twice one key's budget, 5 runs at once per organisation and 5 Go jobs per user
- Data retention: Account data and tables kept while the account is active, deleted or anonymised within 30 days of closing it or a deletion request, per the privacy policy of 30 August 2026
- Legal entity: Only "Retriever" is named, in the terms and privacy policy of 30 August 2026, under French law with the Paris courts, contact emma@retriever.run. No company number or address found
- Prices: Credit, Starter plan $0.0134 per credit; Work email found $0.06 per transaction; Phone number found $0.22 per transaction; LinkedIn sender $10 per connected account per month

- Scores: Reliability 45, Performance not tested, Schema & documentation 82, Agent ergonomics 75, Security & auth 23, Payments & pricing 30, Task success not tested, Maintenance & community 5, Transparency & trust 49 · negative events -15
- Why: Reliability, No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). · Schema & documentation, OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25). · Agent ergonomics, 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 switch… · Security & auth, 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: pla… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release not… · Transparency & trust, Closed source with clear terms, last updated 30 August 2026 (15).
- Sources: 14, open questions: 5, both in the full twin
- Capabilities: lead.search, lead.enrichment, email.finder, data.company, web.search, web.scrape
- JSON: https://www.anchorterminal.com/api/v1/tools/retriever.json
- Its vendor verifies the listing with `verify_listing` or `POST https://www.anchorterminal.com/api/v1/verify` (the full twin says how); no effect on the grade.
- Support: emma@retriever.run; https://docs.retriever.run; https://retriever.run/book-a-demo; more in the full twin

## Before you call it

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

## Connect

```bash
curl -s https://api.retriever.run/credits -H "Authorization: Bearer $RETRIEVER_API_KEY"
```

```bash
claude mcp add --transport http --scope user retriever https://api.retriever.run/mcp
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/retriever

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Apollo API + MCP | B | 67.3 | lead.search, lead.enrichment, email.finder, data.company | https://www.anchorterminal.com/tools/apollo.min.md |
| SpecStream | B | 65.8 | web.search, lead.enrichment, data.company, email.finder | https://www.anchorterminal.com/tools/specstream.min.md |
| Lusha API + MCP | B | 64.8 | lead.search, lead.enrichment, email.finder, data.company | https://www.anchorterminal.com/tools/lusha.min.md |
| FullEnrich API + MCP | B | 64.7 | lead.search, lead.enrichment, email.finder, data.company | https://www.anchorterminal.com/tools/fullenrich.min.md |
| LeadMagic API + MCP | B | 64.5 | lead.search, lead.enrichment, email.finder, data.company | https://www.anchorterminal.com/tools/leadmagic.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)

