Head to head · Lead search · October 2026 research run
Retriever vs RocketReach API
RocketReach API scores 49.5 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on schema & documentation and payments & pricing. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.
Ahead on
- Schema & documentation, 82 against 72
- Payments & pricing, 30 against 15
Watch for
Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted
Best for Teams that already hold a RocketReach plan and want an agent to search people and companies, reveal emails and phones, and verify single addresses over MCP.
Ahead on
- Reliability, 64 against 45
- Security & auth, 30 against 23
- Maintenance & community, 11 against 5
- Transparency & trust, 59 against 49
Also in its favour
- No incidents deducted, where Retriever loses 15 points for them
Watch for
The pricing page is drawn by script and was not read, and the docs tell users without a paid plan to email for an API plan
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability RocketReach API +19
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).
RocketReach API 64
RocketReach's terms bar automated data collection on its website and services, so rocketreach.co and its subdomains were not re-read on 4 November 2026. Per the 9 October check. Hosted lines. Status page on incident.io at status.rocketreach.co with five components, among them API and MCP (20). In the last 90 days it lists eight entries. On 20 August 2026 degraded performance ran from 12:00 AM to 10:00 AM across the site, extension, API and MCP, with a second hour that afternoon, delayed webhooks and a 29-minute outage in the evening. On 27 August elevated errors lasted 61 minutes. A 71-minute maintenance window on 27 September, in which the notice said API and MCP calls would be unresponsive or throttled, was announced on 15 September. Read as one major day and a second incident of about an hour. Both remain inside the 90 days from 6 August, and the status page after 9 October couldn't be read, so the recorded award is kept, a partial pending the founder's rule on in-between values (7 of 30). Rate limits published per plan and endpoint, plus a global 10 requests a second (15). 429 carries Retry-After and the docs show a retry example. No idempotency keys, though repeat lookups are free (12 of 15). No SLA found in the terms, the subscription agreement or the docs (0). The API and MCP server are not marked beta (10). Total 64.
Payments & pricing Retriever +15
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).
RocketReach API 15
Per the 9 October check, not re-read on 4 November 2026, because RocketReach's terms bar automated data collection on its website and services. No x402, MPP or L402 in the docs or terms (0). The docs publish credit costs per action for Universal Credits, such as 2 credits for a professional email and 6 for a phone. The pricing page is drawn by script and showed our reader only its title, so no price in dollars was read, and the docs tell users without a paid plan to email for an API plan (5 of 20). The site's description says to try for free, and the rate-limit page implies an unpaid account can call the API until throttled. What a free account gets through the API was not established (5 of 20). A person signs up in a browser, the terms say account holders warrant they are human, and MCP authorisation needs a browser login (0). Total 10. The pricing lines are scored on what could be read. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Schema & documentation Retriever +10
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).
RocketReach API 72
Per the 9 October check, not re-read on 4 November 2026, because RocketReach's terms bar automated data collection on its website and services. Each reference page's Markdown twin carries an OpenAPI 3.1 definition for its operation, 17 operations in all. No single downloadable file was found (22 of 25). llms.txt and Markdown twins on the docs host (10). The MCP tools page states what each tool returns, what it costs and which tool to call next. REST operation descriptions are thin, and Company Lookup carries the Company Search subtitle (14 of 20). Query parameters are typed, with enums on lookup_type and order_by. No lookup parameter is marked required although one identifier is needed, and metadata is a free object (10 of 15). Error table, a worked 402 body, an MCP error catalogue and response examples. Every operation lists the same generic error set (11 of 15). The version sits in the path (/api/v2), with the Universal Credits endpoints alongside. No changelog was found (5 of 15). Total 72.
Transparency & trust RocketReach API +10
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).
RocketReach API 59
Per the 9 October check, not re-read on 4 November 2026, because RocketReach's terms bar automated data collection on its website and services. Closed service with terms that name RocketReach, LLC and cover the API (15 of 30). The privacy policy, updated 30 September 2026, covers people in the database as well as customers. It names sources (public web pages, data brokers, and customers' connected email accounts by opt-in), a removal form, a DPO, EU and UK representatives, a Texas data broker notice and 2025 request counts. A DPA is public. Retention has no stated period (20 of 30). The API definitions mark deprecated fields with no dates, and no deprecation policy was found (4 of 20). The policy says data is collected and held in the US. The DPA says a sub-processor list is in a Trust Centre, which we did not find linked and did not read (6 of 20). Total 45.
Security & auth RocketReach API +7
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).
RocketReach API 30
RocketReach's terms bar automated data collection on its website and services, so rocketreach.co and its subdomains were not re-read on 4 November 2026. Per the 9 October check. REST takes one key per account in the Api-Key header. Only one key is active at a time and generating a new one invalidates the old. The MCP server uses OAuth 2.1 with PKCE, open dynamic client registration, one-hour access tokens, 30-day refresh tokens that rotate, and a revocation endpoint. The access token carries the API key inside an encrypted envelope, and the account tool returns api_key in its response, so the key reaches the model's context (18). The docs say older clients may still send the key as an api_key query parameter, marked deprecated. This run settled that a query-string credential takes the checklist's fixed 10 off, where the 9 October note took 5 (8 of 30, 13 before). One scope, rocketreach:read, covers every tool, including lookups that spend credits and add contacts to My Contacts. No read-only mode, per-key limit or confirmation step was found. The account object has an api_key_domain field (4 of 20). Results are third-party profile data. No prompt-injection guidance was found (3 of 15). Usage and rate-limit counts from the account endpoint, a recent-errors panel in account settings, RR-Request-ID on webhooks, and MCP lookups tagged with the client name. No per-call log was found (8 of 15). security.txt is valid, with a contact address and an expiry of 8 June 2029, a reporting route with no stated acknowledgement time, which this run settled at 7. The DPA lists security measures in an annex and names a Trust Centre that we did not find linked. No certification or bug bounty was found. No advisory for the rocketreach PyPI package on osv.dev on 4 November 2026 (7 of 20, 6 before). 8 + 4 + 3 + 8 + 7 = 30.
Maintenance & community RocketReach API +6
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.
RocketReach API 11
No changelog or release notes were found (9 October; rocketreach.co hosts not re-read on 4 November 2026 because the terms bar automated data collection). The 9 October note set recency at 20 on docs page update dates (8 October and 11 September 2026). Page dates that record no API change don't set recency, and a closed service's recency is its last dated API change (wrike, buttercms, everee read it so). No dated API change is on record. The Python SDK, the vendor's other dated source, read by clone on 4 November 2026, has its last code change on 26 March 2025 (a bug fix to an exception call), version 2.1.8 with no tags, and only repository housekeeping since (21 August and 5 October 2026). Over 180 days (0, 20 before). No dated changelog entries or releases in the 90 days from 6 August (0 of 20). Support by email and a status page that posts updates, per 9 October (5 of 15). The SDK isn't current, and the official MCP registry wasn't searched, since this run doesn't use its JSON API. The partial is kept pending the founder's rule on in-between values (3 of 15). The SDK repository has a Renovate configuration and states Python 3.4 or later (3 of 10). 0 + 0 + 5 + 3 + 3 = 11.
Score by category
| Category | Weight | Retriever | RocketReach API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 64 | RocketReach API +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 72 | Retriever +10 |
| Agent ergonomics | 13% | 75 | 72 | Retriever +3 |
| Security & auth | 14% | 23 | 30 | RocketReach API +7 |
| Payments & pricing | 10% | 30 | 15 | Retriever +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 5 | 11 | RocketReach API +6 |
| Transparency & trust | 7% | 49 | 59 | RocketReach API +10 |
| Negative events | ≤15 | -15 | 0 | |
| Total | F 32/100 | D 49.5/100 |
Facts side by side
| Fact | Retriever | RocketReach API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Retriever | RocketReach, LLC |
| Hosted endpoint | https://api.retriever.run/mcp | https://api.rocketreach.co/api/v2 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | none | Proprietary service under RocketReach's Terms of Service. The Python SDK on GitHub is MIT |
| Tools exposed | 67 | 9 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Terms last updated | 2026-08-30 | 2024-01-31 |
| Privacy policy last updated | 2026-08-30 | 2026-09-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | 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 | yes |
| Arbitration or class-action waiver | not found in the text | yes |
How the scores have moved
Retriever
No score change since it was listed.
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.
RocketReach API
The hosted MCP server has nine documented tools, OAuth 2.1 with dynamic client registration and machine-readable error codes, and searches cost no credits. Plan prices were not readable, the terms require a human account holder and bar automated data collection, the account tool returns the API key to the model, and no dated API change is on record.
Before you call either
Retriever
- Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
- Send an
Idempotency-Keywith each run and replay with the same key after a timeout, so a retry doesn't start a second billed run - Run
getEmail,getPhoneNumberandwebResearchthroughservice_batch_execute, even for one person;service_executerefuses them - Check
creditsbefore a paid run, and callservice_inspectfor a service'sthingsToKnowand credit cost before executing it - 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
RocketReach API
- Search first with
person_searchorcompany_search, which cost no credits, then look up only the profile IDs needed - Treat
status: "pending"as normal. Pollcheck_person_statusafter at least 3 seconds, and polling is free - Do not echo the
accounttool's output to users or logs. It includes the account's API key - Send the key in the
Api-Keyheader. Theapi_keyquery parameter is deprecated - Bulk lookup takes 1 to 100 queries and needs a webhook. Results arrive at the webhook, signed in
X-RocketReach-Signature - Do not loop on
unknownfromemail_verify, or onlookup_failedandnot_found. The last two are terminal
Questions
Which is better for AI agents, Retriever or RocketReach API?
RocketReach API scores 49.5 (D) on agent readiness against Retriever's 32 (F), and leads in 4 of 7 scored categories. Retriever leads on schema & documentation and payments & pricing.
Do Retriever and RocketReach API need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Retriever and RocketReach API without installing anything?
Yes. Retriever has a hosted endpoint at https://api.retriever.run/mcp and RocketReach API at https://api.rocketreach.co/api/v2.
Other comparisons with Retriever or RocketReach API
- Apollo API + MCP vs Retriever
- Apollo API + MCP vs RocketReach API
- Clay vs Retriever
- Clay vs RocketReach API
- Coresignal API + MCP vs Retriever
- Coresignal API + MCP vs RocketReach API
- Crustdata API + MCP vs Retriever
- Crustdata API + MCP vs RocketReach API
- Dievio vs Retriever
- Dievio vs RocketReach API
- Enrich Layer API + MCP vs Retriever
- Enrich Layer API + MCP vs RocketReach API
- Explorium AgentSource vs Retriever
- Explorium AgentSource vs RocketReach API
- FullEnrich API + MCP vs Retriever
- FullEnrich API + MCP vs RocketReach API
- Fuse MCP vs Retriever
- Fuse MCP vs RocketReach API
- Gojiberry vs Retriever
- Gojiberry vs RocketReach API
- LeadMagic API + MCP vs Retriever
- LeadMagic API + MCP vs RocketReach API
- Lusha API + MCP vs Retriever
- Lusha API + MCP vs RocketReach API
- People Data Labs vs Retriever
- People Data Labs vs RocketReach API
- Prospeo API + MCP vs Retriever
- Prospeo API + MCP vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- RocketReach API vs ZoomInfo API + MCP
- Clearbit vs Retriever
- Clearbit vs RocketReach API
- Databar vs Retriever
- Databar vs RocketReach API
- Dropcontact API + MCP vs Retriever
- Dropcontact API + MCP vs RocketReach API
- FullContact vs Retriever
- FullContact vs RocketReach API
- Retriever vs ZeroBounce
- Hunter API + MCP vs Retriever
- Hunter API + MCP vs RocketReach API
- RocketReach API vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/retriever-vs-rocketreach.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/retriever.json·/api/v1/tools/rocketreach.json - From a terminal
anchor compare retriever rocketreach(the CLI) - Over MCP
compare_tools {"a": "retriever", "b": "rocketreach"}at/mcp, no key