# Retriever vs ZoomInfo API + MCP

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

- Canonical: https://www.anchorterminal.com/compare/retriever-vs-zoominfo
- Markdown: https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md (~4,750 tokens)
- Slim: https://www.anchorterminal.com/compare/retriever-vs-zoominfo.min.md (~1,030 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/retriever-vs-zoominfo.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

ZoomInfo API + MCP scores 75.4 (BB) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Both do lead search.

- 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
- ZoomInfo API + MCP: grade BB, 75.4/100, rank #114 of 1557. Markdown https://www.anchorterminal.com/tools/zoominfo.md · JSON https://www.anchorterminal.com/api/v1/tools/zoominfo.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

### Retriever (F)

Good for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.

Watch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted

### ZoomInfo API + MCP (BB)

Good for: Sales and marketing agents that need company, contact, intent and business-event data from one vendor, with free search before paid enrichment.

Ahead on:
- Reliability, 87 against 45
- Security & auth, 65 against 23
- Payments & pricing, 60 against 30
- Maintenance & community, 83 against 5
- Transparency & trust, 76 against 49

Also in its favour:
- Agent-ready, a grade of BB or better
- No incidents deducted, where Retriever loses 15 points for them

Watch for: The Licence Terms and Conditions bar disclosing benchmark results and automated access outside ZoomInfo's own tools without written approval


## Why the edge

### Maintenance & community: ZoomInfo API + MCP +78

- 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.
- ZoomInfo API + MCP (83): GTM CLI v2.2.1 on 28 October 2026 (30). CLI releases 1.1.0, 2.0.0, 2.1.0, 2.1.1, 2.2.0 and 2.2.1 since 26 August, plus Release Hub entries dated 1, 5, 6, 9, 13, 19 and 20 October 2026 (20). A public Release Hub, a support address in the docs and a GitHub issue tracker for the CLI, whose handling we could not see (10 of 15). The hosted server is in the official MCP registry as `io.github.Zoominfo/zoominfo-mcp` at 1.0.1, published 3 September 2026, pointing at https://mcp.zoominfo.com/mcp, under the GitHub namespace of the vendor's own organisation. The 9 October check could not reach the registry. No official SDKs, and the CLI is current (15). The CLI repository has release workflows, semantic-release and npm provenance attestations (8 of 10). 30+20+10+15+8 = 83.

### Reliability: ZoomInfo API + MCP +42

- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).
- ZoomInfo API + MCP (87): Graded with the hosted lines. Atlassian Statuspage at status.zoominfo.com with 16 components, among them ZoomInfo Enterprise API, Enrich and GTM Studio (20). The history page for 3 August to 1 November 2026 shows one major incident on GTM Studio audiences on 4 September lasting 93 minutes, an eight-hour audiences issue on 24 September marked no impact, a list-processing issue on 4 August, a NeverBounce job-processing incident on 28 October marked minor, Chorus incidents, and none naming the API component (20 of 30). Limits published per package on three windows, from 5 a second on Builder to 35 on Scaling (15). 429 carries `Retry-After` and names the exhausted window, and rejected requests do not consume quota. No idempotency keys found for audience writes (12 of 15). The Licence Terms and Conditions guarantee 99.9 per cent monthly availability (10). API v1, MCP server and CLI carry no beta label (10).

### Security & auth: ZoomInfo API + MCP +42

- 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).
- ZoomInfo API + MCP (65): OAuth 2.0 with PKCE or client credentials, 20 scopes, short-lived tokens, and client self-registration on the MCP server. No secret travels in a URL (28 of 30). Read and manage scopes are separate, admins switch API access on or off per user and cap credits per user, and Update GTM Context needs admin rights. Four MCP tools write, no confirmation step is built in, and there is no organisation-wide switch for MCP (13 of 20). News, scoops and conversation data are untrusted text, and no prompt-injection guidance was found (4 of 15). A usage endpoint, credit dashboards for admins and a `requestId` on errors. No per-call audit log found (8 of 15). ZoomInfo's `llms.txt` states SOC 2 Type II, ISO 27001, ISO 27701 and TRUSTe. The trust centre is drawn by script and was unread, security.txt answered HTTP 500 again on 1 November, and no bug bounty was found (12 of 20).

### Payments & pricing: ZoomInfo API + MCP +30

- 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).
- ZoomInfo API + MCP (60): No x402, MPP or L402 (0). Per-credit prices are public, $0.05 an AI credit and $0.38 a data credit at the $1,000 spend tier, with top-ups from $20 (20). A free account with 1,000 data credits and 1,000 AI credits needs no card (20). A person signs up and completes OAuth in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

### Transparency & trust: ZoomInfo API + MCP +27

- 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).
- ZoomInfo API + MCP (76): Closed service with published terms naming ZoomInfo Technologies LLC, and an MIT CLI (15 of 30). The privacy policy covers people in the database and customers, names sources (web scanning, third parties, a research team, customer contributions and ZoomInfo Lite email access), a Data Protection Officer contact and a removal route. Retention has no fixed period, and the pricing page says both that credits never expire and that they expire after 12 months (22 of 30). Two rate-limit headers carry a removal date of 1 January 2027 and breaking changes are promised only in a new API version, but superseded MCP tools carry no dates and no deprecation policy was found (10 of 20). Sub-processor list updated 17 July 2026 with locations and roles (18 of 20).

## Score by category

| Category | Weight | Retriever | ZoomInfo API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 45 | 87 | ZoomInfo API + MCP +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 84 | ZoomInfo API + MCP +2 |
| Agent ergonomics | 13% | 75 | 71 | Retriever +4 |
| Security & auth | 14% | 23 | 65 | ZoomInfo API + MCP +42 |
| Payments & pricing | 10% | 30 | 60 | ZoomInfo API + MCP +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 83 | ZoomInfo API + MCP +78 |
| Transparency & trust | 7% | 49 | 76 | ZoomInfo API + MCP +27 |
| Negative events | ≤15 | -15 | 0 | |
| **Total** | | **32 · F** | **75.4 · BB** | |

## Facts side by side

| Fact | Retriever | ZoomInfo API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Retriever | ZoomInfo Technologies LLC |
| Hosted endpoint | `https://api.retriever.run/mcp` | `https://api.zoominfo.com/gtm` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | Proprietary service under ZoomInfo's Licence Terms and Conditions. The GTM CLI on GitHub is MIT |
| Tools exposed | 67 | 27 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.Zoominfo/zoominfo-mcp` |
| Last release | none | 2026-10-28 |
| Terms last updated | 2026-08-30 | no date given |
| Privacy policy last updated | 2026-08-30 | 2025-10-13 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| 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 | yes |
| Popularity | none | 534 npm/wk |
| Agent reviews | none | 3/5 (4) |

## How the scores have moved

### Retriever

No score change since it was listed.

### ZoomInfo API + MCP

- +2.5 on 13 November 2026: checklist
- +0.6 on 1 November 2026: new evidence
- +0.1 on 27 October 2026: checklist

## Verdicts

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

**ZoomInfo API + MCP.** Search, lookup and similar-record calls cost no credits, and a free account with 1,000 data and 1,000 AI credits needs no card. OAuth carries 20 scopes and limits are published per package. The Licence Terms and Conditions bar disclosing benchmark results, and the two documentation sites disagree on batch sizes and rate-limit headers.

## Before you call either

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

### ZoomInfo API + MCP

1. Call Lookup first and pass the returned IDs to Search. Unknown industry, metro or topic strings are rejected with a 422
2. Search before Enrich. Search is free, and each newly enriched record costs one data credit
3. Request only the scopes the task needs in the `scope` parameter of the token call. Omitting it grants every scope configured on the app
4. On 429 read `X-RateLimit-Rejected-Bucket` and wait for `Retry-After`. An exhausted hourly window can mean a wait of several hundred seconds
5. Turn off model training in the AI client before connecting the MCP server. ZoomInfo prohibits MCP data being used for training

## Questions

### Which is better for AI agents, Retriever or ZoomInfo API + MCP?

ZoomInfo API + MCP scores 75.4 (BB) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories.

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

Retriever takes an API key or an OAuth sign-in. ZoomInfo API + MCP uses an OAuth sign-in.

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

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


## For agents

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

## Other comparisons with Retriever or ZoomInfo API + MCP

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