Head to head · Lead search · October 2026 research run

Leadsets vs RocketReach API

Leadsets scores 62.9 (B) on agent readiness against RocketReach API's 49.5 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and schema & documentation. Both do lead search.

Best lead, contact and company data APIs for AI agents · All 276 leads comparisons

Which one, for what

Leadsets B

Best for Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.

Ahead on

  • Agent ergonomics, 90 against 72
  • Security & auth, 67 against 30
  • Payments & pricing, 50 against 15
  • Maintenance & community, 80 against 11
  • Transparency & trust, 67 against 59

Also in its favour

  • Free to start without a card

Watch for

No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing

RocketReach API D

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 40
  • Schema & documentation, 72 against 58

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.

Maintenance & community Leadsets +69

Leadsets 80

The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80.

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.

Security & auth Leadsets +37

Leadsets 67

Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional X-Leadsets-Client label, rate-limit headers and request_id on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67.

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.

Payments & pricing Leadsets +35

Leadsets 50

No x402, MPP or L402. An exhausted Free meter answers 402 free_records_exhausted with no payment requirements (0). Plan prices and their per-window limits are public, with no per-record price, and scraping units are priced per pack ($9 for 1,000, $19 for 5,000, $49 for 20,000), so plan-only pricing with a per-unit add-on (20 of 30). Free plan of 1,000 enrichment records, 100 search records and 1,000 data calls, one time, "no card required" (30). A person signs up in a browser and makes the key in the dashboard (0). 0 + 20 + 30 + 0 = 50.

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.

Reliability RocketReach API +24

Leadsets 40

No status page found, and the support page answers "Where can I check if Leadsets is down?" by pointing to the 503 error and support email (0). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an Idempotency-Key on paid calls that makes retries safe for 24 hours (15). The terms say "We aim for high availability but don't guarantee uninterrupted service unless agreed in writing", and no SLA is published (0). No page calls the service beta or preview, but the changelog says "No releases yet. Release notes start at launch.", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.

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.

Agent ergonomics Leadsets +18

Leadsets 90

Eight MCP tools per the docs, with sizes unread, and REST responses sized by limit and a count_only mode that returns only a count, but no field selection found (20 of 25). Cursor pagination, typed filters, max_age_days, exclude_stale and has_verified_email (20). Every error has a status, a type, a request_id, the meter and charged, and the docs say whether to retry each one (20). Idempotency-Key on every paid call for 24 hours, with 409 idempotency_conflict for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as limit 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90.

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. The MCP server documents nine tools. We read the docs page and did not connect, so the size of the live definitions is unread (22 of 25). start, page_size up to 100, order_by, an exclude object and about 50 search facets, with a ceiling of 10,000 results a query (18 of 20). MCP errors carry error_code in _meta with retry_after_seconds, credit_type or field and reason. On REST only the 402 from email verification is structured, and running out of lookup credits returns a 403 with a text detail (15 of 20). Repeat lookups and polling are free and terminal errors are named. No idempotency keys, and MCP tool annotations were not read (9 of 20). Few parameters are needed for a call. One official SDK, Python 2.1.8, whose last code change is dated 26 March 2025 (8 of 15). Total 72.

Schema & documentation RocketReach API +14

Leadsets 58

No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers initialize with 401 without a key, so its tool schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for limit (1 to 100) and max_age_days, ISO country codes and booleans, with one nested priorities object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58.

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.

Score by category

CategoryWeightLeadsetsRocketReach APIEdge
Reliability16%4064RocketReach API +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5872RocketReach API +14
Agent ergonomics13%9072Leadsets +18
Security & auth14%6730Leadsets +37
Payments & pricing10%5015Leadsets +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8011Leadsets +69
Transparency & trust7%6759Leadsets +8
Negative events≤1500
TotalB 62.9/100D 49.5/100

Facts side by side

FactLeadsetsRocketReach API
KindHTTP APIHTTP API
VendorLeadsetsRocketReach, LLC
Hosted endpointhttps://mcp.leadsets.aihttps://api.rocketreach.co/api/v2
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicencenoneProprietary service under RocketReach's Terms of Service. The Python SDK on GitHub is MIT
Tools exposed89
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.leadsets/leadsetsnot listed
Last release2026-11-22none
Terms last updated2026-11-152024-01-31
Privacy policy last updated2026-11-192026-09-30
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes

How the scores have moved

Verdicts

Leadsets

Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.

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

Leadsets

  1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time
  2. Send an Idempotency-Key on every paid call, and reuse it on a retry so records are counted once
  3. If a 429 has type weekly_limit, stop until resets_at. For window_full and too_many_concurrent, wait for Retry-After
  4. Use a read-level key for monitoring only. Data tools answer 403 forbidden to it
  5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found

RocketReach API

  1. Search first with person_search or company_search, which cost no credits, then look up only the profile IDs needed
  2. Treat status: "pending" as normal. Poll check_person_status after at least 3 seconds, and polling is free
  3. Do not echo the account tool's output to users or logs. It includes the account's API key
  4. Send the key in the Api-Key header. The api_key query parameter is deprecated
  5. Bulk lookup takes 1 to 100 queries and needs a webhook. Results arrive at the webhook, signed in X-RocketReach-Signature
  6. Do not loop on unknown from email_verify, or on lookup_failed and not_found. The last two are terminal

Questions

Which is better for AI agents, Leadsets or RocketReach API?

Leadsets scores 62.9 (B) on agent readiness against RocketReach API's 49.5 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and schema & documentation.

Do Leadsets and RocketReach API need an API key?

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

Can an agent call Leadsets and RocketReach API without installing anything?

Yes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and RocketReach API at https://api.rocketreach.co/api/v2.

Other comparisons with Leadsets or RocketReach API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.