Head to head · Lead search · October 2026 research run

Leadsets vs People Data Labs

Leadsets scores 62.9 (B) on agent readiness against People Data Labs's 60.5 (C), and leads in 5 of 7 scored categories. People Data Labs 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 77
  • Security & auth, 67 against 43
  • Payments & pricing, 50 against 38

Also in its favour

  • Free to start without a card
  • No incidents deducted, where People Data Labs loses 3 points for them

Watch for

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

People Data Labs C

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

Watch for

No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings

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 People Data Labs +33

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.

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.

Security & auth Leadsets +24

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.

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

Agent ergonomics Leadsets +13

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.

People Data Labs 77

data_include selects or excludes fields, size caps records at 1 to 100, gzip is supported and a 1 MB response limit is documented (20 of 25). Search pages with scroll_token and filters on any mapped field, with dataset to narrow the source (18 of 20). Errors carry a status, a type and a short message across six documented codes, with 404 meaning no match (13 of 20). The API is read-only and charges only on a 200, so a repeat is safe, though no retry guidance or idempotency key was found (12 of 20). Enrichment needs one identifier, defaults are sensible, and SDKs exist for Python, JavaScript, Ruby, Go and Rust (14 of 15).

Schema & documentation People Data Labs +12

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.

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

Payments & pricing Leadsets +12

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.

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.

Score by category

CategoryWeightLeadsetsPeople Data LabsEdge
Reliability16%4073People Data Labs +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5870People Data Labs +12
Agent ergonomics13%9077Leadsets +13
Security & auth14%6743Leadsets +24
Payments & pricing10%5038Leadsets +12
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8079Leadsets +1
Transparency & trust7%6766Leadsets +1
Negative events≤150-3
TotalB 62.9/100C 60.5/100

Facts side by side

FactLeadsetsPeople Data Labs
KindHTTP APIHTTP API
VendorLeadsetsPeople Data Labs, Inc.
Hosted endpointhttps://mcp.leadsets.aihttps://api.peopledatalabs.com/v5
TransportsStreamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT
Tools exposed8none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.leadsets/leadsetsnot listed
Last release2026-11-222026-10-23
Terms last updated2026-11-15couldn't be read
Privacy policy last updated2026-11-19couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone40 stars, 133k npm/wk, 30k PyPI/wk
Agent reviewsnone3.8/5 (4)

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.

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.

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

People Data Labs

  1. Send the key in the X-Api-Key header. The api_key query parameter puts the secret in URLs and logs
  2. Build and test queries against https://sandbox.api.peopledatalabs.com/v5/... first. It costs no credits and allows five calls a minute
  3. Set size deliberately on search. Every record returned costs one credit, and responses over 1 MB fail
  4. Treat 404 on enrichment as no match, not an error, and 402 as credits exhausted. Neither is worth a retry
  5. On 429, wait until the x-ratelimit-reset time. Limits are fixed-window per key and per endpoint

Questions

Which is better for AI agents, Leadsets or People Data Labs?

Leadsets scores 62.9 (B) on agent readiness against People Data Labs's 60.5 (C), and leads in 5 of 7 scored categories. People Data Labs leads on reliability and schema & documentation.

Do Leadsets and People Data Labs need an API key?

Leadsets takes an API key or an OAuth sign-in. People Data Labs needs an API key.

Can an agent call Leadsets and People Data Labs without installing anything?

Yes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and People Data Labs at https://api.peopledatalabs.com/v5.

Other comparisons with Leadsets or People Data Labs

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.