> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asteragents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# People Data Labs

> Connect People Data Labs to resolve individuals from a name + home address and return their personal email and phone

## Overview

The People Data Labs (PDL) integration lets your agents resolve a **person** from a name plus a home/mailing address and return their **personal** email(s) and phone. It's built for the consumer / skip-trace case — brand-new solo business owners, homeowners, individuals with no business web footprint — exactly where B2B contact tools (like Apollo) come up empty.

The single tool, **PDL Enrich**, takes what you already have on an individual (name + address) and fills in reachable contact details, so it pairs naturally with sources that give you a name and address but no way to reach the person (e.g. business-registration filings).

## Prerequisites

* A **People Data Labs Pro plan** — Free plans **mask contact fields**: emails and phones come back as `true`/`false` availability flags instead of real values. Pro is required to return actual addresses. See [Plan types: Free vs Pro](https://support.peopledatalabs.com/hc/en-us/articles/27546010665115-Plan-types-Free-Pro-and-Enterprise).
* A PDL **API key** from your PDL dashboard.

## Setup Guide

<Steps>
  <Step title="Get Your API Key">
    In your People Data Labs dashboard, copy your **API key**. Confirm your account is on a **Pro** plan so contact fields are returned as values, not booleans.
  </Step>

  <Step title="Connect People Data Labs in Aster Agents">
    Navigate to **Control Hub > Integrations**, locate the **People Data Labs** card, click **Connect**, and paste your API key.
  </Step>

  <Step title="Add the Tool to Your Agent">
    Edit your agent and enable **People Data Labs Enrich**. Pair it with **Verify Emails** so returned personal emails are deliverability-checked before any outreach.
  </Step>
</Steps>

## Available Tools

* **[People Data Labs Enrich](/tools/pdl_enrich)** — Resolve a person from name + home address and return their personal email(s) and optional phone. Defaults to only matching (and only billing) when a personal email exists.

## How Credits Work

PDL bills **1 credit per successful match** (HTTP 200). A no-match is **free** (HTTP 404):

| Action                                                      | Credits |
| ----------------------------------------------------------- | ------- |
| Successful person match                                     | 1       |
| No match found                                              | 0       |
| No match met the `required` filter (e.g. no personal email) | 0       |

By default the tool sends `required=personal_emails`, so PDL only returns — and only charges for — records that actually carry a personal email. Lookups with no personal email 404 for free, which keeps cost-per-usable-lead low.

| Plan          | Price      | Person-enrich credits        |
| ------------- | ---------- | ---------------------------- |
| Pro (monthly) | \$98 / mo  | 350 (then \~\$0.28 / credit) |
| Pro (annual)  | discounted | \~\$0.20 / credit            |

<Note>
  On **Free** plans, PDL returns contact fields as boolean availability flags (`true`/`false`) rather than actual emails and phones. The tool will report matches but no usable addresses until the account is upgraded to **Pro**.
</Note>

<Note>
  The connected API key is shared by all agents in your organization and draws from your organization's PDL credit balance. Use agent-level tool permissions to control which agents can spend credits.
</Note>

## Best Practices

* **Always verify before sending.** Pass returned personal emails through [Verify Emails](/tools/verify_emails) (Bouncer) and only send to deliverable ones.
* **Prefer name-matched results.** The tool returns a `name_match` flag; forcing a personal-email match can surface associated/household emails, so favor candidates whose record name matches the person.
* **Provide the full address.** Street + city + state + ZIP improves match precision. Keep `min_likelihood` low (default 2) — name + address alone yields low likelihood even on correct matches.

## Security Considerations

* **Protect your API key** — it can spend your PDL credits and access personal contact data
* **Rotate API keys** periodically from your PDL dashboard
* **Grant the PDL tool only to agents that need it** to control credit usage and PII access
* **Personal data:** results include personal emails and phones — handle in line with your outreach-compliance obligations (e.g. CAN-SPAM, applicable DNC rules)

## Troubleshooting

<AccordionGroup>
  <Accordion title="Emails/phones come back as true or false instead of addresses">
    * The account is on a **Free** plan, which masks contact fields as availability flags
    * Upgrade to **Pro** to return actual email and phone values
  </Accordion>

  <Accordion title="Authentication failed (401)">
    * Verify the API key is correct and active in your PDL dashboard
    * Re-paste the key in **Control Hub > Integrations**
  </Accordion>

  <Accordion title="Payment required (402)">
    * The PDL account is out of credits or the plan doesn't include Person Enrich — top up credits or upgrade
  </Accordion>

  <Accordion title="Rate limit hit (429)">
    * PDL enforces a per-minute request cap (Pro default 500/min) — slow the request rate
  </Accordion>

  <Accordion title="No match returned">
    * Add or correct the street address, city, state, and ZIP — precision improves with a complete address
    * The person may not be in PDL's data, or may have no personal email (which, with the default `required=personal_emails`, returns a free no-match)
  </Accordion>
</AccordionGroup>