{
  "data": {
    "a": {
      "slug": "leadsets",
      "name": "Leadsets",
      "vendor": "Leadsets",
      "vendorUrl": "https://www.leadsets.ai",
      "company": "leadsets.ai",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Leadsets is a B2B data API and remote MCP server from Mobylogix LLC. Agents search people and companies, enrich them with verified work emails, verify addresses and scrape company websites over REST or eight MCP tools.",
      "url": "https://www.anchorterminal.com/tools/leadsets",
      "markdownUrl": "https://www.anchorterminal.com/tools/leadsets.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/leadsets.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/leadsets.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/leadsets.json",
      "dns": "leadsets.grade.anchorterminal.com",
      "repo": "https://github.com/leadsets/sdk",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.leadsets.ai",
      "packages": [
        {
          "registry": "npm",
          "name": "@leadsetsai/sdk"
        },
        {
          "registry": "pypi",
          "name": "leadsets"
        }
      ],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ls_live_...`) in the `Authorization` header for REST and MCP, made in the dashboard after a browser signup. Each key has one access level (full, data or read) and an expiry of never, 30, 90 or 365 days. Keys are stored as hashes, shown once and revoked within a minute. MCP clients that support it sign in with OAuth (authorisation code with PKCE S256 and dynamic client registration, no scopes listed in the server metadata).",
      "pricing": "freemium",
      "pricingNotes": "Free plan with 1,000 enrichment records, 100 search records and 1,000 data calls, one time, no card. Flat monthly plans at $29, $99, $399 and $999 with no per-record bill and fair-use limits per rolling five hours and per week. Scraping is an add-on in units, from $9 for 1,000. No machine payment protocol.",
      "priceSummary": "$29 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on the pricing page, the docs, the errors page or llms.txt (checked 2026-11-22). An exhausted Free meter returns 402 `free_records_exhausted` with no payment requirements, and the docs tell the agent to ask the user to upgrade.",
        "endpoints": []
      },
      "toolCount": 8,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-22"
      },
      "docsUrl": "https://www.leadsets.ai/docs",
      "llmsTxt": "https://www.leadsets.ai/llms.txt",
      "registryName": "io.github.leadsets/leadsets",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.verification",
        "email.finder",
        "data.person",
        "data.company",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "remote-mcp",
        "mcp-registry",
        "oauth",
        "api-key",
        "llms-txt",
        "typescript",
        "python",
        "closed-source",
        "no-status-page",
        "new",
        "lead-search",
        "enrichment",
        "email-verification"
      ],
      "lastRelease": "2026-11-22",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.9,
        "grade": "B",
        "agentReady": false,
        "rank": 661,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 90,
          "maintenance": 80,
          "payments": 50,
          "reliability": 40,
          "schema": 58,
          "security": 67,
          "transparency": 67
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-22"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.",
        "strengths": [
          "Errors carry a machine-readable `type` and `request_id`, and the docs say for each of 11 types whether to retry",
          "`Idempotency-Key` on paid calls lasts 24 hours, and a retry with the same key never counts records twice",
          "Keys carry a full, data or read access level and an optional expiry, and are revoked within a minute",
          "Free plan of 1,000 enrichment and 100 search records with no card, and empty results use no records",
          "TypeScript and Python SDKs that retry 429 and 5xx with Retry-After, and an entry in the official MCP registry"
        ],
        "weaknesses": [
          "No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing",
          "No OpenAPI file found, and the MCP tool definitions can't be read without an account",
          "The API changelog said on 22 November 2026 \"No releases yet. Release notes start at launch.\"",
          "Data comes from licensed suppliers that the pages don't name, and SOC 2 is a target for Q3 2027",
          "Signup and paid plans need a person in a browser, and there is no machine payment protocol"
        ],
        "agentNotes": [
          "Call get_usage before a large run. It costs nothing and returns every meter with its reset time",
          "Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once",
          "If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After",
          "Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it",
          "Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.9
          }
        ],
        "editorialScores": {
          "ergonomics": 90,
          "maintenance": 80,
          "payments": 50,
          "reliability": 40,
          "schema": 58,
          "security": 67,
          "transparency": 68
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-22",
            "maintenance": "2026-11-22",
            "payments": "2026-11-22",
            "reliability": "2026-11-22",
            "schema": "2026-11-22",
            "security": "2026-11-22",
            "transparency": "2026-11-22"
          },
          "last": "2026-11-22",
          "oldest": "2026-11-22",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm i @leadsetsai/sdk",
        "http": "curl https://api.leadsets.ai/v1/usage -H \"Authorization: Bearer $LEADSETS_KEY\"",
        "claudeCode": "claude mcp add --transport http leadsets https://mcp.leadsets.ai --header \"Authorization: Bearer $LEADSETS_KEY\"",
        "config": {
          "mcpServers": {
            "leadsets": {
              "headers": {
                "Authorization": "Bearer YOUR_LEADSETS_API_KEY"
              },
              "url": "https://mcp.leadsets.ai"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/leadsets"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Solo plan",
          "unit": "month",
          "usd": 29,
          "note": "1,000 enrichments per five hours, 5,000 a week"
        },
        {
          "item": "Pro plan",
          "unit": "month",
          "usd": 99,
          "note": "15,000 enrichments per five hours, 75,000 a week"
        },
        {
          "item": "Team plan",
          "unit": "month",
          "usd": 399,
          "note": "150,000 enrichments per five hours, 750,000 a week"
        },
        {
          "item": "Max plan",
          "unit": "month",
          "usd": 999,
          "note": "225,000 enrichments per five hours, 1.125 million a week"
        },
        {
          "item": "Scraping, 1,000-unit pack",
          "unit": "1k-pages",
          "usd": 9,
          "note": "One unit is one standard page"
        },
        {
          "item": "Scraping, 20,000-unit pack",
          "unit": "1k-pages",
          "usd": 2.45,
          "note": "$49 for 20,000 units"
        }
      ],
      "provenance": {
        "legalEntity": "Mobylogix LLC",
        "domain": "leadsets.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.leadsets.ai/terms",
        "privacy": "https://www.leadsets.ai/privacy",
        "statusPage": "",
        "changelog": "https://www.leadsets.ai/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-11-22",
        "notes": [
          "Mobylogix LLC is named on the terms (updated 15 November 2026), the privacy policy (updated 19 November 2026), llms.txt and the SDK's MIT licence. The terms say it is based in Austin, Texas, and choose Texas law and the courts of Travis County. The privacy policy's contact address is 10160 hwy 242, Conroe, TX 77385.",
          "www.leadsets.ai/robots.txt allows ClaudeBot, Claude-User and anthropic-ai except /app, /onboarding, /api/, /dev/, /md/, /auth/, /search and a few account pages. mcp.leadsets.ai/robots.txt answered 404, so that host publishes no rules.",
          "The terms forbid reselling or rebuilding the data and evading limits. No clause on automated reading of the website was found.",
          "RDAP for leadsets.ai answered 429 at rdap.org, so the registration date is unchecked.",
          "/.well-known/security.txt answered 404. No status page found. The SDK repository's SECURITY.md names security@leadsets.ai."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/leadsets.json",
      "live": {
        "slug": "leadsets",
        "probe": {
          "target": "https://mcp.leadsets.ai",
          "method": "get",
          "lastAt": "2026-11-22T22:37:18.649226285Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 176,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 234,
          "p95ms24h": 325,
          "samples24h": 9,
          "samples30d": 9,
          "days": [
            {
              "date": "2026-11-22",
              "probes": 9,
              "ok": 9
            }
          ],
          "since": "2026-11-22T21:49:45.065930097Z"
        },
        "updatedAt": "2026-11-22T22:37:18.649226285Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-22",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "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 \u0026 documentation.",
    "b": {
      "slug": "people-data-labs",
      "name": "People Data Labs",
      "vendor": "People Data Labs, Inc.",
      "vendorUrl": "https://www.peopledatalabs.com",
      "company": "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",
      "cardUrl": "https://www.anchorterminal.com/tools/people-data-labs.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/people-data-labs.json",
      "dns": "people-data-labs.grade.anchorterminal.com",
      "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 (whether signup needs a card isn't stated) 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-11-02).",
      "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-10-23",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 60.5,
        "grade": "C",
        "agentReady": false,
        "rank": 771,
        "ranked": true,
        "rankOf": 1571,
        "categoryRank": 12,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 77,
          "maintenance": 79,
          "payments": 38,
          "reliability": 73,
          "schema": 70,
          "security": 43,
          "transparency": 66
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": -3,
        "negativeNotes": [
          "2026-10-20, -3. A published behaviour changed for existing clients, announced the day it took effect. The October 2026 release notes (v36.0, published 20 October) say internal executive role changes are no longer included in the documented `recent_exec_hires` field and now sit in a new `recent_exec_internal_changes` field, and that existing customers may notice changes to executive hire counts or records. The August and September release notes carry no notice of it. Read as NocoDB's and aidbox's same-day changes were. https://docs.peopledatalabs.com/changelog/october-2026-release-notes-v360"
        ],
        "verdict": "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.",
        "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 20 October 2026 (dataset v36.0), with schema changes labelled and removals announced four months ahead",
          "`data_include`, `size` and `scroll_token` let a caller limit fields and page through search results",
          "Deletions and opt-outs apply to the API dataset at once, and the Subject Request API returns them for data already held"
        ],
        "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 agreement, privacy policy and DPA are drawn by script on the privacy centre, so their terms couldn't be read on 2 November",
          "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, and the free plan's card rule isn't stated"
        ],
        "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": 4,
        "avgRating": 3.8,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.5
          }
        ],
        "editorialScores": {
          "ergonomics": 77,
          "maintenance": 79,
          "payments": 38,
          "reliability": 73,
          "schema": 70,
          "security": 43,
          "transparency": 49
        },
        "provenanceScore": 83,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-02",
            "maintenance": "2026-11-02",
            "payments": "2026-11-02",
            "reliability": "2026-11-02",
            "schema": "2026-11-02",
            "security": "2026-11-02",
            "transparency": "2026-11-02"
          },
          "last": "2026-11-02",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "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"
      },
      "area": "web-data",
      "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-11-02",
        "notes": [
          "The site footer names People Data Labs, Inc. The Services Subscription Agreement and the privacy policy on privacy.peopledatalabs.com are drawn by script from an internal data file, which this run doesn't read, so the 8 October readings of their text (the address, California law) are struck and the documents are unread on 2 November. www.peopledatalabs.com/acceptable-data-use-policy redirects there too.",
          "privacy.peopledatalabs.com answers /robots.txt with its app page, not a robots file.",
          "The API answers at api.peopledatalabs.com and the sandbox at sandbox.api.peopledatalabs.com.",
          "www.peopledatalabs.com/.well-known/security.txt returned 404 on 2 November 2026.",
          "RDAP gives a registration date of 2017-07-16 for peopledatalabs.com.",
          "The status host's robots.txt disallows /api/ and /embed/; incidents are read from history.atom."
        ],
        "score": 83
      },
      "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-11-22T22:37:30.071184541Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 613,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 607,
          "p95ms24h": 774,
          "samples24h": 242,
          "samples30d": 7788,
          "days": [
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 240,
              "ok": 240
            },
            {
              "date": "2026-11-19",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-20",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-21",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-22",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.peopledatalabs.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-22T22:31:17.654359918Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "peopledatalabs/peopledatalabs-python",
            "version": "v6.4.13",
            "released": "2026-01-12",
            "seenAt": "2026-11-21T23:18:19.039826407Z"
          },
          {
            "registry": "npm",
            "name": "peopledatalabs",
            "version": "14.8.0",
            "seenAt": "2026-11-21T23:18:18.663755719Z"
          },
          {
            "registry": "pypi",
            "name": "peopledatalabs",
            "version": "6.4.13",
            "released": "2026-01-12",
            "seenAt": "2026-11-21T23:18:18.482475577Z"
          }
        ],
        "githubStars": 41,
        "npmWeekly": 270812,
        "pypiWeekly": 27540,
        "securityTxt": {
          "url": "https://peopledatalabs.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-22T16:40:37.250632381Z"
        },
        "llmsTxt": {
          "url": "https://docs.peopledatalabs.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-22T16:31:46.138123469Z"
        },
        "domain": {
          "domain": "peopledatalabs.com",
          "registered": "2017-07-16",
          "source": "https://rdap.verisign.com/com/v1/domain/peopledatalabs.com",
          "checkedAt": "2026-11-22T15:56:02.879180841Z"
        },
        "pages": [
          {
            "url": "https://docs.peopledatalabs.com/links/release-notes",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-21T23:44:24.461711884Z",
            "changedAt": "2026-11-18T21:41:21.062245576Z",
            "fingerprint": "05d402e5a95a"
          },
          {
            "url": "https://docs.peopledatalabs.com/changelog/october-2026-release-notes-v360",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-21T23:44:22.40612359Z",
            "changedAt": "2026-11-18T21:41:18.868831266Z",
            "fingerprint": "6c456281e90b"
          },
          {
            "url": "https://www.peopledatalabs.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-22T00:10:13.084723333Z",
            "changedAt": "2026-11-11T17:23:20.97713825Z",
            "fingerprint": "91716b4a5822"
          },
          {
            "url": "https://privacy.peopledatalabs.com/policies?name=privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-21T23:54:37.355762429Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          },
          {
            "url": "https://privacy.peopledatalabs.com/policies?name=services-subscription-agreement",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-21T23:54:39.689787604Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          }
        ],
        "github": {
          "repo": "peopledatalabs/peopledatalabs-python",
          "checkedAt": "2026-11-16T12:44:12.504642146Z",
          "stars": 41,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-06-04T15:31:50Z",
          "openIssues": 2,
          "openPRs": 6,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 0,
          "ci": {
            "branch": "main",
            "runs": 7,
            "success": 7,
            "failure": 0,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-04-21T12:42:30Z"
          },
          "replies": {
            "sampled": 11,
            "unanswered": 2,
            "medianDays": 2.8
          }
        },
        "updatedAt": "2026-11-22T22:37:30.071184541Z"
      },
      "streak": {
        "days": 44,
        "from": "2026-10-09",
        "sinceWatching": true,
        "next": {
          "kind": "breaking",
          "date": "2027-02-16",
          "what": "Company fields `funding_details.investing_companies` and `affiliated_profiles` are removed in v37.1. Use `investing_companies_details` and `affiliated_entities[].affiliated_id`",
          "source": "https://docs.peopledatalabs.com/changelog/october-2026-release-notes-v360"
        },
        "best": 44
      }
    },
    "edges": [
      {
        "by": 33,
        "category": "reliability",
        "leads": "people-data-labs",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 40,
          "b": 73
        }
      },
      {
        "by": 24,
        "category": "security",
        "leads": "leadsets",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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)."
        },
        "scores": {
          "a": 67,
          "b": 43
        }
      },
      {
        "by": 13,
        "category": "ergonomics",
        "leads": "leadsets",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "`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)."
        },
        "scores": {
          "a": 90,
          "b": 77
        }
      },
      {
        "by": 12,
        "category": "schema",
        "leads": "people-data-labs",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "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)."
        },
        "scores": {
          "a": 58,
          "b": 70
        }
      },
      {
        "by": 12,
        "category": "payments",
        "leads": "leadsets",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 50,
          "b": 38
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Leadsets",
        "b": "People Data Labs, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.leadsets.ai",
        "b": "https://api.peopledatalabs.com/v5",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Proprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT",
        "name": "Licence"
      },
      {
        "a": "8",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "io.github.leadsets/leadsets",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-22",
        "b": "2026-10-23",
        "name": "Last release"
      },
      {
        "a": "2026-11-15",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-19",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "40 stars, 133k npm/wk, 30k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3.8/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 documentation.",
        "question": "Which is better for AI agents, Leadsets or People Data Labs?"
      },
      {
        "answer": "Leadsets takes an API key or an OAuth sign-in. People Data Labs needs an API key.",
        "question": "Do Leadsets and People Data Labs need an API key?"
      },
      {
        "answer": "Yes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and People Data Labs at https://api.peopledatalabs.com/v5.",
        "question": "Can an agent call Leadsets and People Data Labs without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 90 against 77",
          "Security \u0026 auth, 67 against 43",
          "Payments \u0026 pricing, 50 against 38"
        ],
        "also": [
          "Free to start without a card",
          "No incidents deducted, where People Data Labs loses 3 points for them"
        ],
        "goodFor": "Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.",
        "slug": "leadsets",
        "watchFor": "No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing"
      },
      {
        "aheadOn": [
          "Reliability, 73 against 40",
          "Schema \u0026 documentation, 70 against 58"
        ],
        "also": null,
        "goodFor": "Products and pipelines that enrich or search person and company records at volume and can write Elasticsearch or SQL queries.",
        "slug": "people-data-labs",
        "watchFor": "No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings"
      }
    ],
    "history": {
      "leadsets": null,
      "people-data-labs": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.7,
          "from": 58.8,
          "fromGrade": "C",
          "to": 60.5,
          "toGrade": "C"
        },
        {
          "causes": [
            "correction",
            "event"
          ],
          "date": "2026-11-02",
          "delta": -5.5,
          "from": 64.3,
          "fromGrade": "B",
          "to": 58.8,
          "toGrade": "C"
        },
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-10-28",
          "delta": 0.1,
          "from": 64.2,
          "fromGrade": "B",
          "to": 64.3,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-leadsets.json",
        "title": "Apollo API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-people-data-labs.json",
        "title": "Apollo API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-leadsets.json",
        "title": "Clay vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs.json",
        "title": "Clay vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets.json",
        "title": "Coresignal API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.json",
        "title": "Coresignal API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-leadsets.json",
        "title": "Crustdata API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-people-data-labs.json",
        "title": "Crustdata API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-leadsets.json",
        "title": "Dievio vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-people-data-labs.json",
        "title": "Dievio vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.json",
        "title": "Enrich Layer API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-people-data-labs.json",
        "title": "Enrich Layer API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.json",
        "title": "Explorium AgentSource vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs.json",
        "title": "Explorium AgentSource vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.json",
        "title": "FullEnrich API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.json",
        "title": "FullEnrich API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.json",
        "title": "Fuse MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs.json",
        "title": "Fuse MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.json",
        "title": "Gojiberry vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-people-data-labs.json",
        "title": "Gojiberry vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-people-data-labs.json",
        "title": "Hunter API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.json",
        "title": "LeadMagic API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-people-data-labs.json",
        "title": "LeadMagic API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-lusha.json",
        "title": "Leadsets vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-prospeo.json",
        "title": "Leadsets vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-retriever.json",
        "title": "Leadsets vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.json",
        "title": "Leadsets vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.json",
        "title": "Leadsets vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-people-data-labs.json",
        "title": "Lusha API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.json",
        "title": "People Data Labs vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach.json",
        "title": "People Data Labs vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-zoominfo.json",
        "title": "People Data Labs vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-leadsets.json",
        "title": "Clearbit vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.json",
        "title": "Clearbit vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-leadsets.json",
        "title": "Databar vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/databar-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-people-data-labs.json",
        "title": "Databar vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/databar-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.json",
        "title": "Dropcontact API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.json",
        "title": "Dropcontact API + MCP vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.json",
        "title": "FullContact vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs.json",
        "title": "FullContact vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.json",
        "title": "People Data Labs vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-leadsets.json",
        "title": "Hunter API + MCP vs Leadsets",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-leadsets"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.json",
        "title": "Leadsets vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/leadsets-vs-zerobounce"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 33,
        "edge": "people-data-labs",
        "key": "reliability",
        "leadsets": 40,
        "name": "Reliability",
        "people-data-labs": 73,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "edge": "people-data-labs",
        "key": "schema",
        "leadsets": 58,
        "name": "Schema \u0026 documentation",
        "people-data-labs": 70,
        "weight": 13
      },
      {
        "by": 13,
        "edge": "leadsets",
        "key": "ergonomics",
        "leadsets": 90,
        "name": "Agent ergonomics",
        "people-data-labs": 77,
        "weight": 13
      },
      {
        "by": 24,
        "edge": "leadsets",
        "key": "security",
        "leadsets": 67,
        "name": "Security \u0026 auth",
        "people-data-labs": 43,
        "weight": 14
      },
      {
        "by": 12,
        "edge": "leadsets",
        "key": "payments",
        "leadsets": 50,
        "name": "Payments \u0026 pricing",
        "people-data-labs": 38,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "leadsets",
        "key": "maintenance",
        "leadsets": 80,
        "name": "Maintenance \u0026 community",
        "people-data-labs": 79,
        "weight": 7
      },
      {
        "by": 1,
        "edge": "leadsets",
        "key": "transparency",
        "leadsets": 67,
        "name": "Transparency \u0026 trust",
        "people-data-labs": 66,
        "weight": 7
      }
    ],
    "summary": "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 \u0026 documentation. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs",
    "json": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.min.md"
  },
  "markdown": "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 \u0026 documentation. Both do lead search.\n\n- Leadsets: grade B, 62.9/100, rank #661 of 1571. Markdown https://www.anchorterminal.com/tools/leadsets.md · JSON https://www.anchorterminal.com/api/v1/tools/leadsets.json\n- People Data Labs: grade C, 60.5/100, rank #771 of 1571. Markdown https://www.anchorterminal.com/tools/people-data-labs.md · JSON https://www.anchorterminal.com/api/v1/tools/people-data-labs.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 276 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Leadsets (B)\n\nGood for: Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.\n\nAhead on:\n- Agent ergonomics, 90 against 77\n- Security \u0026 auth, 67 against 43\n- Payments \u0026 pricing, 50 against 38\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where People Data Labs loses 3 points for them\n\nWatch for: No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing\n\n### People Data Labs (C)\n\nGood for: Products and pipelines that enrich or search person and company records at volume and can write Elasticsearch or SQL queries.\n\nAhead on:\n- Reliability, 73 against 40\n- Schema \u0026 documentation, 70 against 58\n\nWatch for: No OpenAPI file was found. The machine-readable material is a Postman collection and Elasticsearch mappings\n\n\n## Why the edge\n\n### Reliability: People Data Labs +33\n\n- 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.\n- 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.\n\n### Security \u0026 auth: Leadsets +24\n\n- 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.\n- 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).\n\n### Agent ergonomics: Leadsets +13\n\n- 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.\n- 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).\n\n### Schema \u0026 documentation: People Data Labs +12\n\n- 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.\n- 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).\n\n### Payments \u0026 pricing: Leadsets +12\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Leadsets | People Data Labs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 40 | 73 | People Data Labs +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 58 | 70 | People Data Labs +12 |\n| Agent ergonomics | 13% | 90 | 77 | Leadsets +13 |\n| Security \u0026 auth | 14% | 67 | 43 | Leadsets +24 |\n| Payments \u0026 pricing | 10% | 50 | 38 | Leadsets +12 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 80 | 79 | Leadsets +1 |\n| Transparency \u0026 trust | 7% | 67 | 66 | Leadsets +1 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **62.9 · B** | **60.5 · C** | |\n\n## Facts side by side\n\n| Fact | Leadsets | People Data Labs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Leadsets | People Data Labs, Inc. |\n| Hosted endpoint | `https://mcp.leadsets.ai` | `https://api.peopledatalabs.com/v5` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | none | Proprietary service under the Services Subscription Agreement. The Python and JavaScript SDKs are MIT |\n| Tools exposed | 8 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.leadsets/leadsets` | not listed |\n| Last release | 2026-11-22 | 2026-10-23 |\n| Terms last updated | 2026-11-15 | couldn't be read |\n| Privacy policy last updated | 2026-11-19 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 40 stars, 133k npm/wk, 30k PyPI/wk |\n| Agent reviews | none | 3.8/5 (4) |\n\n## How the scores have moved\n\n### Leadsets\n\nNo score change since it was listed.\n\n### People Data Labs\n\n- +1.7 on 13 November 2026: checklist\n- -5.5 on 2 November 2026 (B to C): correction, negative event\n- +0.1 on 28 October 2026: new evidence\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Leadsets\n\n1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time\n2. Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once\n3. If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After\n4. Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it\n5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found\n\n### People Data Labs\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## Questions\n\n### Which is better for AI agents, Leadsets or People Data Labs?\n\nLeadsets 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 \u0026 documentation.\n\n### Do Leadsets and People Data Labs need an API key?\n\nLeadsets takes an API key or an OAuth sign-in. People Data Labs needs an API key.\n\n### Can an agent call Leadsets and People Data Labs without installing anything?\n\nYes. Leadsets has a hosted endpoint at https://mcp.leadsets.ai and People Data Labs at https://api.peopledatalabs.com/v5.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.json, and with the fewest tokens: https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"leadsets\", \"b\": \"people-data-labs\"}`. From a terminal: `anchor compare leadsets people-data-labs`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/leadsets.json and https://www.anchorterminal.com/api/v1/tools/people-data-labs.json\n\n## Other comparisons with Leadsets or People Data Labs\n\n- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)\n- [Apollo API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/apollo-vs-people-data-labs.md)\n- [Clay vs Leadsets](https://www.anchorterminal.com/compare/clay-vs-leadsets.md)\n- [Clay vs People Data Labs](https://www.anchorterminal.com/compare/clay-vs-people-data-labs.md)\n- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)\n- [Coresignal API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/coresignal-vs-people-data-labs.md)\n- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)\n- [Crustdata API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/crustdata-vs-people-data-labs.md)\n- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)\n- [Dievio vs People Data Labs](https://www.anchorterminal.com/compare/dievio-vs-people-data-labs.md)\n- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)\n- [Enrich Layer API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/enrich-layer-vs-people-data-labs.md)\n- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.md)\n- [Explorium AgentSource vs People Data Labs](https://www.anchorterminal.com/compare/explorium-agentsource-vs-people-data-labs.md)\n- [FullEnrich API + MCP vs Leadsets](https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.md)\n- [FullEnrich API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/fullenrich-vs-people-data-labs.md)\n- [Fuse MCP vs Leadsets](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.md)\n- [Fuse MCP vs People Data Labs](https://www.anchorterminal.com/compare/fuse-mcp-vs-people-data-labs.md)\n- [Gojiberry vs Leadsets](https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.md)\n- [Gojiberry vs People Data Labs](https://www.anchorterminal.com/compare/gojiberry-vs-people-data-labs.md)\n- [Hunter API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/hunter-vs-people-data-labs.md)\n- [LeadMagic API + MCP vs Leadsets](https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.md)\n- [LeadMagic API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/leadmagic-vs-people-data-labs.md)\n- [Leadsets vs Lusha API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-lusha.md)\n- [Leadsets vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-prospeo.md)\n- [Leadsets vs Retriever](https://www.anchorterminal.com/compare/leadsets-vs-retriever.md)\n- [Leadsets vs RocketReach API](https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.md)\n- [Leadsets vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.md)\n- [Lusha API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/lusha-vs-people-data-labs.md)\n- [People Data Labs vs Prospeo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [People Data Labs vs RocketReach API](https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach.md)\n- [People Data Labs vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-zoominfo.md)\n- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)\n- [Clearbit vs People Data Labs](https://www.anchorterminal.com/compare/clearbit-vs-people-data-labs.md)\n- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)\n- [Databar vs People Data Labs](https://www.anchorterminal.com/compare/databar-vs-people-data-labs.md)\n- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md)\n- [Dropcontact API + MCP vs People Data Labs](https://www.anchorterminal.com/compare/dropcontact-vs-people-data-labs.md)\n- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md)\n- [FullContact vs People Data Labs](https://www.anchorterminal.com/compare/fullcontact-vs-people-data-labs.md)\n- [People Data Labs vs ZeroBounce](https://www.anchorterminal.com/compare/people-data-labs-vs-zerobounce.md)\n- [Hunter API + MCP vs Leadsets](https://www.anchorterminal.com/compare/hunter-vs-leadsets.md)\n- [Leadsets vs ZeroBounce](https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-22",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Leadsets vs People Data Labs",
        "url": ""
      }
    ],
    "description": "Leadsets scores 62.9 (B) to People Data Labs's 60.5 (C) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Leadsets B 62.9",
      "People Data Labs C 60.5",
      "scores"
    ],
    "h1": "Leadsets vs People Data Labs",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/leadsets-vs-people-data-labs",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Leadsets vs People Data Labs for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-22",
    "url": "https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs"
  },
  "tokens": {
    "markdown": 5100,
    "slim": 1180
  },
  "version": 1
}
