Head to head · Lead search · October 2026 research run
People Data Labs vs Retriever
People Data Labs scores 60.5 (C) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on schema & documentation. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Products and pipelines that enrich or search person and company records at volume and can write Elasticsearch or SQL queries.
Ahead on
- Reliability, 73 against 45
- Security & auth, 43 against 23
- Payments & pricing, 38 against 30
- Maintenance & community, 79 against 5
- Transparency & trust, 66 against 49
Watch for
No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings
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 70
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
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 People Data Labs +74
People Data Labs 79
The October 2026 release notes (v36.0) are dated 20 October and the JavaScript SDK 14.7.0 and Go SDK 6.10.0 followed on 23 October (30). In the 90 days from 4 August, release notes on 18 August, 15 September and 20 October, plus JavaScript SDK releases on 11 and 16 September and 23 October (20). Public release notes, a Canny board for bugs and requests and a support address. We did not test support (11 of 15). Five official SDKs. JavaScript and Go are current, while the Python package's newest tag is 6.4.13 from 12 January 2026 and the repository's April job posting commit is in no release (11 of 15). Both SDK repositories have test and publish workflows and dependency updates (7 of 10). 30+20+11+11+7 = 79.
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.
Reliability People Data Labs +28
People Data Labs 73
Statuspage at status.peopledatalabs.com with a component for each API and the sandbox, and history back to 2021 (20). Two incidents in the 90 days from 4 August to 2 November 2026, both partial. Requests carrying a location failed for about 10 minutes during the 15 September release, and IP enrichment was slow or timing out on 9 August, duration not given. Minor incidents only, so 20 (the 8 October check gave 25, which isn't a checklist value; read from history.atom, since the status host disallows the /api/ feed the earlier reading used). Rate limits are published with numbers, 100 a minute free and 1,000 paid on person enrichment, 10 a minute on person search, five on the sandbox (15). A 429 body and the x-ratelimit-reset header are documented with a fixed-window explanation, and no back-off or retry guidance was found on 2 November (8 of 15). No SLA was found on the pricing pages, and the agreement can't be read (0). The v5 endpoints are generally available (10). 20+20+15+8+0+10 = 73.
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).
Security & auth People Data Labs +20
People Data Labs 43
One revocable API key type with no scopes, with 1, 3 or 5 active keys by plan (20), less 10 because the docs show the key as api_key in the URL query string (10 of 30). The data endpoints only read, and there is no restricted or per-endpoint key (12 of 20). Records come from public and third-party sources and include free-text fields, and no prompt-injection guidance was found (2 of 15). The dashboard Usage tab and per-call credit headers give the operator visibility, with no audit log found (7 of 15). The security page states SOC 2 Type 2 and ISO 27001 compliance and quarterly external penetration tests. No security.txt, bug bounty or disclosure policy was found (12 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).
Transparency & trust People Data Labs +17
People Data Labs 66
Closed service whose site names People Data Labs, Inc. The Services Subscription Agreement, privacy policy, DPA and Acceptable Data Use Policy sit on privacy.peopledatalabs.com, which draws them by script from an internal data file. The 8 October check read that file, which this run counts as an internal data endpoint, so those readings are struck and the documents are unread on 2 November. Licence line held at 15 with the terms unread, as whatsapp-cloud-api and figma-mcp (15 of 30). The readable statements are the docs' data subject rights section (deletions and opt-outs applied to the API dataset at once, to data licences at the next build, with a Subject Request API to pull them) and the security page (encryption at rest and in transit, notice to affected people within 24 hours of a major event). No retention period can be read, and the DPA's 90-day deletion and 72-hour breach terms are struck (12 of 30, was 20). The October 2026 release notes give dated notice of two Company fields removed on 16 February 2027 (v37.1), with replacements and four months' lead, and earlier notes flag parameters that will lose support without dates. No written deprecation policy found (12 of 20, was 6). The security page names AWS and Elastic Cloud and places hosting in Oregon and Northern California; the trust centre's sub-processor list is drawn by script and wasn't read (10 of 20, was 12). 15+12+12+10 = 49.
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).
Schema & documentation Retriever +12
People Data Labs 70
No OpenAPI file was found at the docs root or in the docs index, re-checked on 2 November. A public Postman collection and Elasticsearch mappings for each dataset stand in (8 of 25). llms.txt on the docs site and a Markdown twin of every page (10). Each API has overview, reference, input, output, examples and FAQ pages that state purpose and billing (15 of 20). Enrichment inputs are typed with canonical value lists, while search takes an Elasticsearch 7.7 query or an SQL string, both free-form (9 of 15). Examples in five languages and a six-row error table with sample bodies (13 of 15). A v5 path, numbered dataset versions and monthly release notes back to 2019, the latest v36.0 on 20 October 2026 (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).
Payments & pricing People Data Labs +8
People Data Labs 38
No x402, MPP or L402 (0). Plan entry prices and the credit rule are public, $98 a month for 350 person records and $100 for 1,000 company records, one credit per match. The volume ladder and field-bundle prices sit in the dashboard (15 of 20). A free plan of 100 records a month with contact fields obfuscated, but neither the pricing pages nor the account docs say whether signup needs a card, so half the line, as cronofy and laminar with an unstated card rule (10 of 20, was 20). A person signs up in a browser to get a key (0). 0+15+10+0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
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).
Score by category
| Category | Weight | People Data Labs | Retriever | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 45 | People Data Labs +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 82 | Retriever +12 |
| Agent ergonomics | 13% | 77 | 75 | People Data Labs +2 |
| Security & auth | 14% | 43 | 23 | People Data Labs +20 |
| Payments & pricing | 10% | 38 | 30 | People Data Labs +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 5 | People Data Labs +74 |
| Transparency & trust | 7% | 66 | 49 | People Data Labs +17 |
| Negative events | ≤15 | -3 | -15 | |
| Total | C 60.5/100 | F 32/100 |
Facts side by side
| Fact | People Data Labs | Retriever |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | People Data Labs, Inc. | Retriever |
| Hosted endpoint | https://api.peopledatalabs.com/v5 | https://api.retriever.run/mcp |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT | none |
| Tools exposed | none | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-23 | none |
| Terms last updated | couldn't be read | 2026-08-30 |
| Privacy policy last updated | couldn't be read | 2026-08-30 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 40 stars, 133k npm/wk, 30k PyPI/wk | none |
| Agent reviews | 3.8/5 (4) | none |
How the scores have moved
Verdicts
People Data Labs
Monthly dated release notes with four months' notice of field removals, a free sandbox with synthetic data, credit and rate-limit headers on every response, and a free plan of 100 records a month. No OpenAPI file was found, keys carry no scopes and may travel in the URL, and the legal documents can only be read through a script.
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
People Data Labs
- Send the key in the
X-Api-Keyheader. Theapi_keyquery parameter puts the secret in URLs and logs - Build and test queries against
https://sandbox.api.peopledatalabs.com/v5/...first. It costs no credits and allows five calls a minute - Set
sizedeliberately on search. Every record returned costs one credit, and responses over 1 MB fail - Treat
404on enrichment as no match, not an error, and402as credits exhausted. Neither is worth a retry - On
429, wait until thex-ratelimit-resettime. Limits are fixed-window per key and per endpoint
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
Questions
Which is better for AI agents, People Data Labs or Retriever?
People Data Labs scores 60.5 (C) on agent readiness against Retriever's 32 (F), and leads in 6 of 7 scored categories. Retriever leads on schema & documentation.
Do People Data Labs and Retriever need an API key?
People Data Labs needs an API key. Retriever takes an API key or an OAuth sign-in.
Can an agent call People Data Labs and Retriever without installing anything?
Yes. People Data Labs has a hosted endpoint at https://api.peopledatalabs.com/v5 and Retriever at https://api.retriever.run/mcp.
Other comparisons with People Data Labs or Retriever
- Apollo API + MCP vs People Data Labs
- Apollo API + MCP vs Retriever
- Clay vs People Data Labs
- Clay vs Retriever
- Coresignal API + MCP vs People Data Labs
- Coresignal API + MCP vs Retriever
- Crustdata API + MCP vs People Data Labs
- Crustdata API + MCP vs Retriever
- Dievio vs People Data Labs
- Dievio vs Retriever
- Enrich Layer API + MCP vs People Data Labs
- Enrich Layer API + MCP vs Retriever
- Explorium AgentSource vs People Data Labs
- Explorium AgentSource vs Retriever
- FullEnrich API + MCP vs People Data Labs
- FullEnrich API + MCP vs Retriever
- Fuse MCP vs People Data Labs
- Fuse MCP vs Retriever
- Gojiberry vs People Data Labs
- Gojiberry vs Retriever
- Hunter API + MCP vs People Data Labs
- LeadMagic API + MCP vs People Data Labs
- LeadMagic API + MCP vs Retriever
- Lusha API + MCP vs People Data Labs
- Lusha API + MCP vs Retriever
- People Data Labs vs Prospeo API + MCP
- People Data Labs vs RocketReach API
- People Data Labs vs ZoomInfo API + MCP
- Prospeo API + MCP vs Retriever
- Retriever vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- Clearbit vs People Data Labs
- Clearbit vs Retriever
- Databar vs People Data Labs
- Databar vs Retriever
- Dropcontact API + MCP vs People Data Labs
- Dropcontact API + MCP vs Retriever
- FullContact vs People Data Labs
- FullContact vs Retriever
- People Data Labs vs ZeroBounce
- Retriever vs ZeroBounce
- Hunter API + MCP vs Retriever
Machine-readable
- This page as Markdown
/compare/people-data-labs-vs-retriever.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/people-data-labs.json·/api/v1/tools/retriever.json - From a terminal
anchor compare people-data-labs retriever(the CLI) - Over MCP
compare_tools {"a": "people-data-labs", "b": "retriever"}at/mcp, no key