{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/zoominfo.json", "name": "ZoomInfo API + MCP", "score": 72.2, "shared": [ "lead.search", "lead.enrichment", "data.company", "data.person" ], "slug": "zoominfo" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/apollo.json", "name": "Apollo API + MCP", "score": 63.3, "shared": [ "lead.search", "lead.enrichment", "data.company", "data.person" ], "slug": "apollo" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/coresignal.json", "name": "Coresignal API + MCP", "score": 62.9, "shared": [ "lead.search", "lead.enrichment", "data.company", "data.person" ], "slug": "coresignal" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/lusha.json", "name": "Lusha API + MCP", "score": 62.3, "shared": [ "lead.search", "lead.enrichment", "data.person", "data.company" ], "slug": "lusha" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/leadmagic.json", "name": "LeadMagic API + MCP", "score": 60.2, "shared": [ "lead.search", "lead.enrichment", "data.person", "data.company" ], "slug": "leadmagic" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/fullenrich.json", "name": "FullEnrich API + MCP", "score": 59.6, "shared": [ "lead.search", "lead.enrichment", "data.person", "data.company" ], "slug": "fullenrich" } ], "tool": { "slug": "people-data-labs", "name": "People Data Labs", "vendor": "People Data Labs, Inc.", "vendorUrl": "https://www.peopledatalabs.com", "kind": "http-api", "category": "lead-data", "summary": "People Data Labs sells person, company and job posting data through a REST API. Agents enrich a known person or company, resolve an identity, or search the datasets with Elasticsearch or SQL queries, using an API key.", "url": "https://www.anchorterminal.com/tools/people-data-labs", "markdownUrl": "https://www.anchorterminal.com/tools/people-data-labs.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/people-data-labs.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/people-data-labs.json", "repo": "https://github.com/peopledatalabs/peopledatalabs-python", "license": "Proprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT", "transports": [ "http" ], "remoteUrl": "https://api.peopledatalabs.com/v5", "packages": [ { "registry": "pypi", "name": "peopledatalabs" }, { "registry": "npm", "name": "peopledatalabs" }, { "registry": "go", "name": "github.com/peopledatalabs/peopledatalabs-go" } ], "auth": "api-key", "authNotes": "Self-serve API key from the dashboard after a free signup, sent in the `X-Api-Key` header or as an `api_key` query parameter. Keys have no scopes. A Free account holds 1 active key, Pro 3 and Enterprise 5. Webhooks and data licence deliveries are arranged through sales.", "pricing": "freemium", "pricingNotes": "Free plan with up to 100 records a month and emails, phone numbers and addresses obfuscated. Pro starts at $98 a month for 350 person records or $100 for 1,000 company records, with 20 per cent off on annual terms. Enterprise is priced by sales. One credit per match or per search record returned, and requests without a match are not charged. The sandbox is free. Higher volume steps and field-bundle prices are shown in the dashboard only (https://www.peopledatalabs.com/pricing, https://docs.peopledatalabs.com/docs/create-an-account, checked 2026-10-08).", "priceSummary": "$98 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the pricing page or the Services Subscription Agreement (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 40, "npmWeekly": 132937, "pypiWeekly": 29514, "asOf": "2026-10-08" }, "docsUrl": "https://docs.peopledatalabs.com", "llmsTxt": "https://docs.peopledatalabs.com/llms.txt", "capabilities": [ "lead.search", "lead.enrichment", "data.company", "data.person" ], "tags": [ "lead-search", "enrichment", "hosted", "api-key", "free-tier", "sandbox", "llms-txt", "python", "javascript", "go", "ruby", "rust", "status-page", "soc2", "closed-source" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 64.2, "grade": "B", "agentReady": false, "rank": 326, "ranked": true, "rankOf": 842, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 79, "payments": 35, "reliability": 78, "schema": 70, "security": 43, "transparency": 67 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 78, "points": 15.6, "reason": "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 to 8 October 2026, both minor. 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 (25 of 30). 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 (8 of 15). No SLA was found in the agreement or on the pricing page (0). The v5 endpoints are generally available (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 70, "points": 11.38, "reason": "No OpenAPI file was found at the docs root or in the docs index. 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 (15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 77, "points": 12.51, "reason": "`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)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 43, "points": 7.53, "reason": "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)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 35, "points": 4.38, "reason": "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, and the quickstart's signup steps name no card. Contact fields are obfuscated on it (20). A person signs up in a browser to get a key (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 79, "points": 6.91, "reason": "The latest release notes are dated 15 September 2026 and the JavaScript SDK 14.6.0 followed on 16 September (30). Release notes on 21 July, 18 August and 15 September, plus three JavaScript SDK releases in the same 90 days (20). Public release notes, a Canny board for bugs and feature requests and a support address. We did not test support (11 of 15). Five official SDKs. JavaScript is current, while the Python package on PyPI is 6.4.13 from 12 January 2026 and the repository's April job posting commit is not published (11 of 15). Both SDK repositories have test and publish workflows and dependency updates (7 of 10)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 67, "points": 5.86, "note": "editorial 53, provenance 80", "reason": "Closed service under a published Services Subscription Agreement and Acceptable Data Use Policy that name People Data Labs, Inc. (15 of 30). The privacy policy, a GDPR Article 14 notice and a DPA are published. The DPA commits to deleting customer personal data within 90 days of termination and to breach notice within 72 hours, and describes blind logging of API inputs. Retention in the privacy policy is described by criteria with no periods, and the text we read carried no effective date (20 of 30). The agreement says data and services may be modified without prior notice. Release notes flag parameters that will lose support, such as `from` on search, with no dates or policy (6 of 20). The DPA names Amazon Web Services and points to the trust centre for other sub-processors, which our reader could not load. The security page places hosting in Oregon and Northern California (12 of 20)." } ], "assessment": { "date": "2026-10-08", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "`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).", "maintenance": "The latest release notes are dated 15 September 2026 and the JavaScript SDK 14.6.0 followed on 16 September (30). Release notes on 21 July, 18 August and 15 September, plus three JavaScript SDK releases in the same 90 days (20). Public release notes, a Canny board for bugs and feature requests and a support address. We did not test support (11 of 15). Five official SDKs. JavaScript is current, while the Python package on PyPI is 6.4.13 from 12 January 2026 and the repository's April job posting commit is not published (11 of 15). Both SDK repositories have test and publish workflows and dependency updates (7 of 10).", "payments": "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, and the quickstart's signup steps name no card. Contact fields are obfuscated on it (20). A person signs up in a browser to get a key (0).", "reliability": "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 to 8 October 2026, both minor. 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 (25 of 30). 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 (8 of 15). No SLA was found in the agreement or on the pricing page (0). The v5 endpoints are generally available (10).", "schema": "No OpenAPI file was found at the docs root or in the docs index. 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 (15).", "security": "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).", "transparency": "Closed service under a published Services Subscription Agreement and Acceptable Data Use Policy that name People Data Labs, Inc. (15 of 30). The privacy policy, a GDPR Article 14 notice and a DPA are published. The DPA commits to deleting customer personal data within 90 days of termination and to breach notice within 72 hours, and describes blind logging of API inputs. Retention in the privacy policy is described by criteria with no periods, and the text we read carried no effective date (20 of 30). The agreement says data and services may be modified without prior notice. Release notes flag parameters that will lose support, such as `from` on search, with no dates or policy (6 of 20). The DPA names Amazon Web Services and points to the trust centre for other sub-processors, which our reader could not load. The security page places hosting in Oregon and Northern California (12 of 20)." }, "sources": [ { "what": "docs index (llms.txt)", "url": "https://docs.peopledatalabs.com/llms.txt", "seen": "2026-10-08" }, { "what": "authentication", "url": "https://docs.peopledatalabs.com/docs/authentication", "seen": "2026-10-08" }, { "what": "usage limits and response headers", "url": "https://docs.peopledatalabs.com/docs/usage-limits", "seen": "2026-10-08" }, { "what": "errors and status codes", "url": "https://docs.peopledatalabs.com/docs/errors", "seen": "2026-10-08" }, { "what": "account, plans and credits", "url": "https://docs.peopledatalabs.com/docs/create-an-account", "seen": "2026-10-08" }, { "what": "person search reference", "url": "https://docs.peopledatalabs.com/docs/reference-person-search-api", "seen": "2026-10-08" }, { "what": "person enrichment reference", "url": "https://docs.peopledatalabs.com/docs/reference-person-enrichment-api", "seen": "2026-10-08" }, { "what": "sandbox reference", "url": "https://docs.peopledatalabs.com/docs/sandbox-apis-reference", "seen": "2026-10-08" }, { "what": "September 2026 release notes", "url": "https://docs.peopledatalabs.com/changelog/september-2026-release-notes-v352", "seen": "2026-10-08" }, { "what": "August 2026 release notes", "url": "https://docs.peopledatalabs.com/changelog/august-2026-release-notes-v351", "seen": "2026-10-08" }, { "what": "July 2026 release notes", "url": "https://docs.peopledatalabs.com/changelog/july-2026-release-notes-v350", "seen": "2026-10-08" }, { "what": "data sources and compliance", "url": "https://docs.peopledatalabs.com/docs/data-sources", "seen": "2026-10-08" }, { "what": "pricing", "url": "https://www.peopledatalabs.com/pricing", "seen": "2026-10-08" }, { "what": "security page", "url": "https://www.peopledatalabs.com/security", "seen": "2026-10-08" }, { "what": "website llms.txt", "url": "https://www.peopledatalabs.com/llms.txt", "seen": "2026-10-08" }, { "what": "status incidents feed", "url": "https://status.peopledatalabs.com/api/v2/incidents.json", "seen": "2026-10-08" }, { "what": "Services Subscription Agreement, Acceptable Data Use Policy, privacy policy and DPA, read from the data file the privacy centre loads", "url": "https://privacy.peopledatalabs.com/static/privacy.peopledatalabs.com/privacyCenterMessages-en.json", "seen": "2026-10-08" }, { "what": "JavaScript SDK repository and changelog", "url": "https://github.com/peopledatalabs/peopledatalabs-js", "seen": "2026-10-08" }, { "what": "Python SDK repository", "url": "https://github.com/peopledatalabs/peopledatalabs-python", "seen": "2026-10-08" }, { "what": "PyPI package", "url": "https://pypi.org/project/peopledatalabs/", "seen": "2026-10-08" }, { "what": "npm package", "url": "https://registry.npmjs.org/peopledatalabs/latest", "seen": "2026-10-08" } ], "openQuestions": [ "unchecked: the sub-processor list and any report details on trust.peopledatalabs.com, which is drawn by script and showed our reader only its title", "unchecked: whether the free signup asks for a card. The quickstart names no card step and we did not open the dashboard signup form", "unchecked: the Pro volume ladder, overage price for self-serve accounts and field-bundle prices, which are shown in the dashboard", "The privacy policy text we read refers to an effective date above it, and the data file carried no date", "The company enrichment reference states the free rate limit as 10 a minute, the person enrichment reference as 100. We recorded both", "No OpenAPI file and no MCP server were found in the docs index. We did not search beyond the vendor's docs and GitHub SDK repositories", "The lead was right on the interface. It left out the job posting search, IP enrichment and sandbox endpoints" ] }, "negative": 0, "verdict": "Monthly dated release notes, a free sandbox with synthetic data, response headers that report credits and rate limits, and a free plan of 100 records a month make the API easy to start with. No OpenAPI file was found, keys carry no scopes and may travel in the URL, and the agreement allows changes without notice.", "bestFor": "Products and pipelines that enrich or search person and company records at volume and can write Elasticsearch or SQL queries.", "strengths": [ "Credits are charged only on a match (a `200`), and each response reports credits spent and remaining in headers", "Seven sandbox endpoints at `sandbox.api.peopledatalabs.com` return synthetic records at no charge on every plan", "Release notes are dated monthly, the latest on 15 September 2026 (dataset v35.2), with schema changes labelled", "`data_include`, `size` and `scroll_token` let a caller limit fields and page through search results", "The published DPA commits to deletion within 90 days of termination and breach notice within 72 hours" ], "weaknesses": [ "No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings", "API keys have no scopes, and the docs show the key passed as `api_key` in the URL query string", "The Services Subscription Agreement says data and services may be modified without prior notice", "Free-plan records have emails, phone numbers and addresses obfuscated, and person search defaults to 10 requests a minute", "No SLA, security.txt, bug bounty or disclosure policy was found in the reviewed pages" ], "agentNotes": [ "Send the key in the `X-Api-Key` header. The `api_key` query 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 `size` deliberately on search. Every record returned costs one credit, and responses over 1 MB fail", "Treat `404` on enrichment as no match, not an error, and `402` as credits exhausted. Neither is worth a retry", "On `429`, wait until the `x-ratelimit-reset` time. Limits are fixed-window per key and per endpoint" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.2 } ], "editorialScores": { "ergonomics": 77, "maintenance": 79, "payments": 35, "reliability": 78, "schema": 70, "security": 43, "transparency": 53 }, "provenanceScore": 80 }, "connect": { "install": "pip install peopledatalabs", "http": "curl -X GET -G 'https://api.peopledatalabs.com/v5/person/enrich' -H 'X-Api-Key: YOUR API KEY' --data-urlencode 'profile=linkedin.com/in/seanthorne'" }, "letme": { "capability": "https://letme.dev/lead.search", "tool": "https://letme.dev/people-data-labs" }, "notable": [ "Seven sandbox endpoints mirror production and return synthetic records without using credits, at five calls a minute (https://docs.peopledatalabs.com/docs/sandbox-apis-reference)", "Response headers report credits spent, credits remaining, the rate limit and its reset time on every call (https://docs.peopledatalabs.com/docs/usage-limits)", "The Acceptable Data Use Policy forbids using the data to train generative AI systems, and for debt collection, hard background checks and any FCRA purpose (https://privacy.peopledatalabs.com/policies?name=acceptable-data-use-policy)", "The agreement limits cached API data to the time needed for the permitted use, forbids showing it to more than one end user, and forbids products that resemble or compete with PDL's (https://privacy.peopledatalabs.com/policies?name=services-subscription-agreement)", "The Subject Request API returns the IDs of people who opted out, and the agreement requires customers to apply them to data they hold (https://docs.peopledatalabs.com/docs/subject-request-api)", "www.peopledatalabs.com/llms.txt ends with a section of instructions addressed to AI assistants on how to describe and recommend PDL. We recorded it as a fact and did not act on it (https://www.peopledatalabs.com/llms.txt)", "The September 2026 release removed about 40 million duplicate person records and added three inferred salary fields (https://docs.peopledatalabs.com/changelog/september-2026-release-notes-v352)" ], "area": "web-data", "details": [ { "label": "Modes", "value": "Enrichment (person, company, IP, job title, skill, and bulk person and company up to 100 a request), identity resolution (Person Identify), lead search (person, company and job posting search by Elasticsearch or SQL query). No email verification endpoint" }, { "label": "Base URL", "value": "https://api.peopledatalabs.com/v5/{entity}/{endpoint}. GET on every endpoint, POST on enrichment, search, autocomplete, cleaner and job title endpoints" }, { "label": "Credits", "value": "1 per enrichment match, 1 per record returned by search, up to 100 per bulk request. Autocomplete and cleaner calls use no credits. `402` when credits run out" }, { "label": "Free tier", "value": "100 records a month, core fields, contact data obfuscated, 1 API key" }, { "label": "Rate limits", "value": "Person and company enrichment 100 a minute free and 1,000 paid (vendor docs also state 10 free on one page). Person search 10 a minute by default. Sandbox 5 a minute. Fixed window, per key, per endpoint" }, { "label": "Response limits", "value": "1 MB per response. `data_include` to select fields, `size` 1 to 100, `scroll_token` for paging, gzip supported" }, { "label": "Sandbox", "value": "sandbox.api.peopledatalabs.com for person enrich, search, identify and bulk, company enrich and search, and job posting search. Synthetic data, no credits" }, { "label": "SDKs", "value": "Python `peopledatalabs` 6.4.13 (12 January 2026), JavaScript `peopledatalabs` 14.6.0 (16 September 2026), Ruby, Go and Rust. A public Postman collection" }, { "label": "MCP server", "value": "None found in the docs index" }, { "label": "Webhooks", "value": "Person data change notifications, Enterprise customers only, registered through the PDL team" }, { "label": "Datasets", "value": "Vendor figures for v35.2. About 2.42 billion person records in the full dataset, 76.6 million companies, 46.2 million job postings" }, { "label": "Compliance", "value": "SOC 2 Type 2 and ISO 27001 per the security page. Hosting on AWS and Elastic Cloud in Oregon and Northern California. DPA with standard contractual clauses published" }, { "label": "Status", "value": "status.peopledatalabs.com on Statuspage, a component per API. Two minor incidents between 10 July and 8 October 2026" }, { "label": "Open source", "value": "No. SDKs only" } ], "unitPrices": [ { "item": "Pro plan, person data", "unit": "month", "usd": 98, "note": "350 person records a month, entry step" }, { "item": "Pro plan, company data", "unit": "month", "usd": 100, "note": "1,000 company records a month, entry step" }, { "item": "Person record", "unit": "record", "usd": 0.28, "note": "Derived from $98 for 350 records at the Pro entry step" }, { "item": "Company record", "unit": "record", "usd": 0.1, "note": "Derived from $100 for 1,000 records at the Pro entry step" } ], "provenance": { "legalEntity": "People Data Labs, Inc.", "domain": "peopledatalabs.com", "domainRegistered": "2017-07-16", "endpointOnVendorDomain": true, "terms": "https://privacy.peopledatalabs.com/policies?name=services-subscription-agreement", "privacy": "https://privacy.peopledatalabs.com/policies?name=privacy-policy", "statusPage": "https://status.peopledatalabs.com", "changelog": "https://docs.peopledatalabs.com/links/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Services Subscription Agreement names People Data Labs, Inc., 455 Market St Ste 1940, PMB 25778, San Francisco, CA 94105, and is governed by California law. It applies to accounts opened on peopledatalabs.com as well as order forms.", "The legal pages on privacy.peopledatalabs.com are drawn by script. We read their text from the data file the page itself loads, `/static/privacy.peopledatalabs.com/privacyCenterMessages-en.json`. A plain HTML reader sees only the page title.", "The API answers at api.peopledatalabs.com and the sandbox at sandbox.api.peopledatalabs.com.", "www.peopledatalabs.com/.well-known/security.txt and the same path on the docs host return 404.", "RDAP gives a registration date of 2017-07-16 for peopledatalabs.com.", "The privacy policy says PDL is registered as a data broker in Texas and has certified to the EU-U.S., UK and Swiss-U.S. Data Privacy Frameworks." ], "score": 80, "checks": [ { "check": "Legal entity named", "value": "People Data Labs, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "peopledatalabs.com, registered 2017-07-16 (9 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "api.peopledatalabs.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.peopledatalabs.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://privacy.peopledatalabs.com/policies?name=services-subscription-agreement", "state": "unreadable", "reason": "the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-10-08", "points": 7, "max": 10 }, { "kind": "privacy", "url": "https://privacy.peopledatalabs.com/policies?name=privacy-policy", "state": "unreadable", "reason": "the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-10-08", "points": 7, "max": 10 } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/people-data-labs.json", "live": { "slug": "people-data-labs", "probe": { "target": "https://api.peopledatalabs.com/v5", "method": "get", "lastAt": "2026-10-09T09:27:00.534146752Z", "lastOk": true, "lastStatus": 404, "lastMs": 643, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 592, "p95ms24h": 640, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.peopledatalabs.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:27.85956589Z" }, "updatedAt": "2026-10-09T09:27:00.534146752Z" } }, "verify": { "accepts": "a page on peopledatalabs.com or one of its subdomains, or the README of github.com/peopledatalabs/peopledatalabs-python", "badgeUrl": "https://www.anchorterminal.com/badges/people-data-labs.svg", "body": { "slug": "people-data-labs", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/people-data-labs", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/people-data-labs\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/people-data-labs.svg\" alt=\"People Data Labs on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![People Data Labs on Anchor Terminal](https://www.anchorterminal.com/badges/people-data-labs.svg)](https://www.anchorterminal.com/tools/people-data-labs)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/people-data-labs\"\u003ePeople Data Labs on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/people-data-labs", "json": "https://www.anchorterminal.com/tools/people-data-labs.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/people-data-labs.md", "slim": "https://www.anchorterminal.com/tools/people-data-labs.min.md" }, "markdown": "## Overview\n\n**Grade B · 64.2/100 · rank #326 of 842 · #2 in Lead \u0026 company data · not agent-ready · confidence medium**\n\n\n## Assessment\n\nMonthly dated release notes, a free sandbox with synthetic data, response headers that report credits and rate limits, and a free plan of 100 records a month make the API easy to start with. No OpenAPI file was found, keys carry no scopes and may travel in the URL, and the agreement allows changes without notice.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | People Data Labs, Inc. (https://www.peopledatalabs.com) |\n| Kind | HTTP API |\n| Category | Lead \u0026 company data (https://www.anchorterminal.com/categories/lead-data) |\n| Transport | HTTP |\n| Endpoint | `https://api.peopledatalabs.com/v5` |\n| Auth | API key · Self-serve API key from the dashboard after a free signup, sent in the `X-Api-Key` header or as an `api_key` query parameter. Keys have no scopes. A Free account holds 1 active key, Pro 3 and Enterprise 5. Webhooks and data licence deliveries are arranged through sales. |\n| Pricing | Freemium ($98 / mo) · Free plan with up to 100 records a month and emails, phone numbers and addresses obfuscated. Pro starts at $98 a month for 350 person records or $100 for 1,000 company records, with 20 per cent off on annual terms. Enterprise is priced by sales. One credit per match or per search record returned, and requests without a match are not charged. The sandbox is free. Higher volume steps and field-bundle prices are shown in the dashboard only (https://www.peopledatalabs.com/pricing, https://docs.peopledatalabs.com/docs/create-an-account, checked 2026-10-08). |\n| x402 | No · No x402, MPP or L402 in the docs index, the pricing page or the Services Subscription Agreement (checked 2026-10-08). |\n| Licence | Proprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT |\n| Packages | pypi: `peopledatalabs`; npm: `peopledatalabs`; go: `github.com/peopledatalabs/peopledatalabs-go` |\n| Source | https://github.com/peopledatalabs/peopledatalabs-python |\n| Docs | https://docs.peopledatalabs.com |\n| llms.txt | https://docs.peopledatalabs.com/llms.txt |\n| Last release | 2026-09-16 |\n| GitHub stars | 40 (as of 2026-10-08) |\n| npm downloads / week | 132,937 |\n| PyPI downloads / week | 29,514 |\n| Modes | Enrichment (person, company, IP, job title, skill, and bulk person and company up to 100 a request), identity resolution (Person Identify), lead search (person, company and job posting search by Elasticsearch or SQL query). No email verification endpoint |\n| Base URL | https://api.peopledatalabs.com/v5/{entity}/{endpoint}. GET on every endpoint, POST on enrichment, search, autocomplete, cleaner and job title endpoints |\n| Credits | 1 per enrichment match, 1 per record returned by search, up to 100 per bulk request. Autocomplete and cleaner calls use no credits. `402` when credits run out |\n| Free tier | 100 records a month, core fields, contact data obfuscated, 1 API key |\n| Rate limits | Person and company enrichment 100 a minute free and 1,000 paid (vendor docs also state 10 free on one page). Person search 10 a minute by default. Sandbox 5 a minute. Fixed window, per key, per endpoint |\n| Response limits | 1 MB per response. `data_include` to select fields, `size` 1 to 100, `scroll_token` for paging, gzip supported |\n| Sandbox | sandbox.api.peopledatalabs.com for person enrich, search, identify and bulk, company enrich and search, and job posting search. Synthetic data, no credits |\n| SDKs | Python `peopledatalabs` 6.4.13 (12 January 2026), JavaScript `peopledatalabs` 14.6.0 (16 September 2026), Ruby, Go and Rust. A public Postman collection |\n| MCP server | None found in the docs index |\n| Webhooks | Person data change notifications, Enterprise customers only, registered through the PDL team |\n| Datasets | Vendor figures for v35.2. About 2.42 billion person records in the full dataset, 76.6 million companies, 46.2 million job postings |\n| Compliance | SOC 2 Type 2 and ISO 27001 per the security page. Hosting on AWS and Elastic Cloud in Oregon and Northern California. DPA with standard contractual clauses published |\n| Status | status.peopledatalabs.com on Statuspage, a component per API. Two minor incidents between 10 July and 8 October 2026 |\n| Open source | No. SDKs only |\n| Capabilities | lead.search, lead.enrichment, data.company, data.person |\n| Tags | lead-search, enrichment, hosted, api-key, free-tier, sandbox, llms-txt, python, javascript, go, ruby, rust, status-page, soc2, closed-source |\n| JSON | https://www.anchorterminal.com/api/v1/tools/people-data-labs.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 78 | 15.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 70 | 11.4 |\n| Agent ergonomics | 13% | 16.2 | 77 | 12.5 |\n| Security \u0026 auth | 14% | 17.5 | 43 | 7.5 |\n| Payments \u0026 pricing | 10% | 12.5 | 35 | 4.4 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 79 | 6.9 |\n| Transparency \u0026 trust (editorial 53, provenance 80) | 7% | 8.8 | 67 | 5.9 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **64.2 → B** |\n\n### Why each score\n\n- Reliability 78: 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 to 8 October 2026, both minor. 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 (25 of 30). 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 (8 of 15). No SLA was found in the agreement or on the pricing page (0). The v5 endpoints are generally available (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 70: No OpenAPI file was found at the docs root or in the docs index. 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 (15).\n- Agent ergonomics 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).\n- Security \u0026 auth 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).\n- Payments \u0026 pricing 35: 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, and the quickstart's signup steps name no card. Contact fields are obfuscated on it (20). A person signs up in a browser to get a key (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 79: The latest release notes are dated 15 September 2026 and the JavaScript SDK 14.6.0 followed on 16 September (30). Release notes on 21 July, 18 August and 15 September, plus three JavaScript SDK releases in the same 90 days (20). Public release notes, a Canny board for bugs and feature requests and a support address. We did not test support (11 of 15). Five official SDKs. JavaScript is current, while the Python package on PyPI is 6.4.13 from 12 January 2026 and the repository's April job posting commit is not published (11 of 15). Both SDK repositories have test and publish workflows and dependency updates (7 of 10).\n- Transparency \u0026 trust 67: Closed service under a published Services Subscription Agreement and Acceptable Data Use Policy that name People Data Labs, Inc. (15 of 30). The privacy policy, a GDPR Article 14 notice and a DPA are published. The DPA commits to deleting customer personal data within 90 days of termination and to breach notice within 72 hours, and describes blind logging of API inputs. Retention in the privacy policy is described by criteria with no periods, and the text we read carried no effective date (20 of 30). The agreement says data and services may be modified without prior notice. Release notes flag parameters that will lose support, such as `from` on search, with no dates or policy (6 of 20). The DPA names Amazon Web Services and points to the trust centre for other sub-processors, which our reader could not load. The security page places hosting in Oregon and Northern California (12 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/people-data-labs.md (JSON https://www.anchorterminal.com/fixes/people-data-labs.json)\n\n### What we couldn't check\n\n- unchecked: the sub-processor list and any report details on trust.peopledatalabs.com, which is drawn by script and showed our reader only its title\n- unchecked: whether the free signup asks for a card. The quickstart names no card step and we did not open the dashboard signup form\n- unchecked: the Pro volume ladder, overage price for self-serve accounts and field-bundle prices, which are shown in the dashboard\n- The privacy policy text we read refers to an effective date above it, and the data file carried no date\n- The company enrichment reference states the free rate limit as 10 a minute, the person enrichment reference as 100. We recorded both\n- No OpenAPI file and no MCP server were found in the docs index. We did not search beyond the vendor's docs and GitHub SDK repositories\n- The lead was right on the interface. It left out the job posting search, IP enrichment and sandbox endpoints\n\n### Sources\n\n- docs index (llms.txt): \u003chttps://docs.peopledatalabs.com/llms.txt\u003e (seen 2026-10-08)\n- authentication: \u003chttps://docs.peopledatalabs.com/docs/authentication\u003e (seen 2026-10-08)\n- usage limits and response headers: \u003chttps://docs.peopledatalabs.com/docs/usage-limits\u003e (seen 2026-10-08)\n- errors and status codes: \u003chttps://docs.peopledatalabs.com/docs/errors\u003e (seen 2026-10-08)\n- account, plans and credits: \u003chttps://docs.peopledatalabs.com/docs/create-an-account\u003e (seen 2026-10-08)\n- person search reference: \u003chttps://docs.peopledatalabs.com/docs/reference-person-search-api\u003e (seen 2026-10-08)\n- person enrichment reference: \u003chttps://docs.peopledatalabs.com/docs/reference-person-enrichment-api\u003e (seen 2026-10-08)\n- sandbox reference: \u003chttps://docs.peopledatalabs.com/docs/sandbox-apis-reference\u003e (seen 2026-10-08)\n- September 2026 release notes: \u003chttps://docs.peopledatalabs.com/changelog/september-2026-release-notes-v352\u003e (seen 2026-10-08)\n- August 2026 release notes: \u003chttps://docs.peopledatalabs.com/changelog/august-2026-release-notes-v351\u003e (seen 2026-10-08)\n- July 2026 release notes: \u003chttps://docs.peopledatalabs.com/changelog/july-2026-release-notes-v350\u003e (seen 2026-10-08)\n- data sources and compliance: \u003chttps://docs.peopledatalabs.com/docs/data-sources\u003e (seen 2026-10-08)\n- pricing: \u003chttps://www.peopledatalabs.com/pricing\u003e (seen 2026-10-08)\n- security page: \u003chttps://www.peopledatalabs.com/security\u003e (seen 2026-10-08)\n- website llms.txt: \u003chttps://www.peopledatalabs.com/llms.txt\u003e (seen 2026-10-08)\n- status incidents feed: \u003chttps://status.peopledatalabs.com/api/v2/incidents.json\u003e (seen 2026-10-08)\n- Services Subscription Agreement, Acceptable Data Use Policy, privacy policy and DPA, read from the data file the privacy centre loads: \u003chttps://privacy.peopledatalabs.com/static/privacy.peopledatalabs.com/privacyCenterMessages-en.json\u003e (seen 2026-10-08)\n- JavaScript SDK repository and changelog: \u003chttps://github.com/peopledatalabs/peopledatalabs-js\u003e (seen 2026-10-08)\n- Python SDK repository: \u003chttps://github.com/peopledatalabs/peopledatalabs-python\u003e (seen 2026-10-08)\n- PyPI package: \u003chttps://pypi.org/project/peopledatalabs/\u003e (seen 2026-10-08)\n- npm package: \u003chttps://registry.npmjs.org/peopledatalabs/latest\u003e (seen 2026-10-08)\n\n## Who's behind it (provenance 80/100, checked 2026-10-08)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | People Data Labs, Inc. | 20/20 |\n| Domain age | peopledatalabs.com, registered 2017-07-16 (9 years) | 11/15 |\n| Endpoint on the vendor's domain | api.peopledatalabs.com | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | published, but our reader couldn't read it | 7/10 |\n| Status page | status.peopledatalabs.com | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n\nThe Services Subscription Agreement names People Data Labs, Inc., 455 Market St Ste 1940, PMB 25778, San Francisco, CA 94105, and is governed by California law. It applies to accounts opened on peopledatalabs.com as well as order forms.\n\nThe legal pages on privacy.peopledatalabs.com are drawn by script. We read their text from the data file the page itself loads, `/static/privacy.peopledatalabs.com/privacyCenterMessages-en.json`. A plain HTML reader sees only the page title.\n\nThe API answers at api.peopledatalabs.com and the sandbox at sandbox.api.peopledatalabs.com.\n\nwww.peopledatalabs.com/.well-known/security.txt and the same path on the docs host return 404.\n\nRDAP gives a registration date of 2017-07-16 for peopledatalabs.com.\n\nThe privacy policy says PDL is registered as a data broker in Texas and has certified to the EU-U.S., UK and Swiss-U.S. Data Privacy Frameworks.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://privacy.peopledatalabs.com/policies?name=services-subscription-agreement), read 2026-10-08. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n**Privacy policy** (https://privacy.peopledatalabs.com/policies?name=privacy-policy), read 2026-10-08. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n## Live (updated 2026-10-09 09:27 UTC)\n\n- Right now: up, HTTP 404, 643 ms, checked 2026-10-09 09:27 UTC (get on `https://api.peopledatalabs.com/v5`)\n- Uptime 24h 100.0% (20 probes) · 30 days 100.0% (20 probes) · p50 592 ms · p95 640 ms\n- Vendor status page: none, All Systems Operational\n- Always current: https://www.anchorterminal.com/api/v1/live/people-data-labs.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Pro plan, person data | $98 | per month (plan) | 350 person records a month, entry step |\n| Pro plan, company data | $100 | per month (plan) | 1,000 company records a month, entry step |\n| Person record | $0.28 | per record | Derived from $98 for 350 records at the Pro entry step |\n| Company record | $0.10 | per record | Derived from $100 for 1,000 records at the Pro entry step |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Credits are charged only on a match (a `200`), and each response reports credits spent and remaining in headers\n- Seven sandbox endpoints at `sandbox.api.peopledatalabs.com` return synthetic records at no charge on every plan\n- Release notes are dated monthly, the latest on 15 September 2026 (dataset v35.2), with schema changes labelled\n- `data_include`, `size` and `scroll_token` let a caller limit fields and page through search results\n- The published DPA commits to deletion within 90 days of termination and breach notice within 72 hours\n\n## Weaknesses\n\n- No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings\n- API keys have no scopes, and the docs show the key passed as `api_key` in the URL query string\n- The Services Subscription Agreement says data and services may be modified without prior notice\n- Free-plan records have emails, phone numbers and addresses obfuscated, and person search defaults to 10 requests a minute\n- No SLA, security.txt, bug bounty or disclosure policy was found in the reviewed pages\n\n## Before you call it (notes for agents)\n\n1. Send the key in the `X-Api-Key` header. The `api_key` query parameter puts the secret in URLs and logs\n2. Build and test queries against `https://sandbox.api.peopledatalabs.com/v5/...` first. It costs no credits and allows five calls a minute\n3. Set `size` deliberately on search. Every record returned costs one credit, and responses over 1 MB fail\n4. Treat `404` on enrichment as no match, not an error, and `402` as credits exhausted. Neither is worth a retry\n5. On `429`, wait until the `x-ratelimit-reset` time. Limits are fixed-window per key and per endpoint\n\n## Connect\n\nInstall:\n\n```bash\npip install peopledatalabs\n```\n\nFirst request:\n\n```bash\ncurl -X GET -G 'https://api.peopledatalabs.com/v5/person/enrich' -H 'X-Api-Key: YOUR API KEY' --data-urlencode 'profile=linkedin.com/in/seanthorne'\n```\n\nThrough letme (picks today, calling later): https://letme.dev/people-data-labs. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| ZoomInfo API + MCP | BB | 72.2 | 106 | lead.search, lead.enrichment, data.company, data.person | no | https://www.anchorterminal.com/tools/zoominfo.md |\n| Apollo API + MCP | B | 63.3 | 361 | lead.search, lead.enrichment, data.company, data.person | no | https://www.anchorterminal.com/tools/apollo.md |\n| Coresignal API + MCP | B | 62.9 | 373 | lead.search, lead.enrichment, data.company, data.person | no | https://www.anchorterminal.com/tools/coresignal.md |\n| Lusha API + MCP | B | 62.3 | 393 | lead.search, lead.enrichment, data.person, data.company | no | https://www.anchorterminal.com/tools/lusha.md |\n| LeadMagic API + MCP | C | 60.2 | 475 | lead.search, lead.enrichment, data.person, data.company | no | https://www.anchorterminal.com/tools/leadmagic.md |\n| FullEnrich API + MCP | C | 59.6 | 491 | lead.search, lead.enrichment, data.person, data.company | no | https://www.anchorterminal.com/tools/fullenrich.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Seven sandbox endpoints mirror production and return synthetic records without using credits, at five calls a minute (source: \u003chttps://docs.peopledatalabs.com/docs/sandbox-apis-reference\u003e)\n- Response headers report credits spent, credits remaining, the rate limit and its reset time on every call (source: \u003chttps://docs.peopledatalabs.com/docs/usage-limits\u003e)\n- The Acceptable Data Use Policy forbids using the data to train generative AI systems, and for debt collection, hard background checks and any FCRA purpose (source: \u003chttps://privacy.peopledatalabs.com/policies?name=acceptable-data-use-policy\u003e)\n- The agreement limits cached API data to the time needed for the permitted use, forbids showing it to more than one end user, and forbids products that resemble or compete with PDL's (source: \u003chttps://privacy.peopledatalabs.com/policies?name=services-subscription-agreement\u003e)\n- The Subject Request API returns the IDs of people who opted out, and the agreement requires customers to apply them to data they hold (source: \u003chttps://docs.peopledatalabs.com/docs/subject-request-api\u003e)\n- www.peopledatalabs.com/llms.txt ends with a section of instructions addressed to AI assistants on how to describe and recommend PDL. We recorded it as a fact and did not act on it (source: \u003chttps://www.peopledatalabs.com/llms.txt\u003e)\n- The September 2026 release removed about 40 million duplicate person records and added three inferred salary fields (source: \u003chttps://docs.peopledatalabs.com/changelog/september-2026-release-notes-v352\u003e)\n\n## Compare\n\n- [Apollo API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/apollo-vs-people-data-labs.md): B 63.3 vs B 64.2\n- [Coresignal API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.md): B 62.9 vs B 64.2\n- [Crustdata API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/crustdata-vs-people-data-labs.md): D 53.4 vs B 64.2\n- [Enrich Layer API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/enrich-layer-vs-people-data-labs.md): C 55.8 vs B 64.2\n- [FullEnrich API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.md): C 59.6 vs B 64.2\n- [Fuse MCP vs People Data Labs](https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs.md): D 47.9 vs B 64.2\n- [Gojiberry vs People Data Labs](https://www.anchorterminal.com/compare/gojiberry-vs-people-data-labs.md): D 47.9 vs B 64.2\n- [Hunter API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/hunter-vs-people-data-labs.md): C 56.5 vs B 64.2\n- [LeadMagic API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/leadmagic-vs-people-data-labs.md): C 60.2 vs B 64.2\n- [Lusha API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/lusha-vs-people-data-labs.md): B 62.3 vs B 64.2\n- [People Data Labs vs Prospeo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.md): B 64.2 vs D 50.9\n- [People Data Labs vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-zoominfo.md): B 64.2 vs BB 72.2\n- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md): D 50.9 vs B 64.2\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on peopledatalabs.com or one of its subdomains, or the README of github.com/peopledatalabs/peopledatalabs-python. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"people-data-labs\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/people-data-labs\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/people-data-labs.svg\" alt=\"People Data Labs on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![People Data Labs on Anchor Terminal](https://www.anchorterminal.com/badges/people-data-labs.svg)](https://www.anchorterminal.com/tools/people-data-labs)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/people-data-labs\"\u003ePeople Data Labs on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say People Data Labs is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/people-data-labs-dark.png\n- Light: https://www.anchorterminal.com/assets/share/people-data-labs-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Lead \u0026 company data", "url": "https://www.anchorterminal.com/categories/lead-data" }, { "name": "People Data Labs", "url": "" } ], "description": "People Data Labs sells person, company and job posting data through a REST API. Agents enrich a known person or company, resolve an identity, or search the datasets with Elasticsearch or SQL queries, using an API key.", "facts": [ "rank #326 of 842", "API key auth", "0 desk reviews" ], "h1": "People Data Labs", "image": "https://www.anchorterminal.com/assets/og/tools-people-data-labs.png", "path": "/tools/people-data-labs", "published": "2026-10-01", "section": "tools", "title": "People Data Labs review for AI agents, grade B (64.2/100)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/tools/people-data-labs" }, "tokens": { "markdown": 6800, "slim": 1780 }, "version": 1 }