Person Profile Lookup · People Data Labs

Start with an email or social profile you already have, or a full name with known background details, to match one person record. A successful match can provide a name, job information and work history, with a 1–10 confidence score. Your Agent can turn available details into a profile summary.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu’s enrich-person-people-data-labs, catalog ID 46ca9555-0d88-40f1-882d-0d4676a3f4cc, to find the person profile for my supplied identifier and prepare the summary I need. Reuse my Toolmu connection; when setup is needed, follow https://toolmu.com/SKILL.md. Read get_tool for this exact Tool, check current availability and price, and work within my existing authorization and budget. Use a known social profile, email, phone, email hash, LinkedIn ID or PDL ID. For name-based matching, use a full name, or first and last names, together with known company, school, location, address or birth-date context. Ask only for missing information needed to identify the target. A supplied pdl_id takes precedence over other matching inputs. Apply my chosen likelihood threshold and profile-field options. Read the returned data, likelihood and any matched-input list requested with include_if_matched. Treat confidence as a matching score rather than a percentage or independent verification. Preserve available names, roles and work-history details; keep unknown values and excluded fields distinct. Prepare the profile summary as separate Agent work, without presenting old employment information as confirmed current employment or an input email as verified contact information.

Task:
Look up [a LinkedIn profile link] or [a work email address]. Summarize the available role and work history, confirm the result is the person I mean, and mark missing details.

Paste into your connected AI's conversation.

Connection guide

Up to 0.36 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

People Data Labs

Person Profile Lookup · People Data Labs

You receive

When a person is matched, the response contains a profile in data and a likelihood score. Available details can include a full name, job title, company information and work experience. You may select profile fields and request the names of inputs that matched. Your Agent can organize the returned career information and distinguish source details from its own interpretation.

Start with your task

Look up [a LinkedIn profile link] or [a work email address]. Summarize the available role and work history, confirm the result is the person I mean, and mark missing details.

What to know

Matching does not independently verify identity, current employment or whether an email or phone is reachable. Profile coverage depends on the available information, and unknown attributes can be null. A higher confidence threshold can leave no accepted match; an unmatched request does not prove the person has no profile.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Person matching request`body`	`object`	Optional	Object containing a person’s known identifiers, matching context and response options. Use an identifier such as email or profile, or a full name with known work, school, location or birth-date context.
LinkedIn person ID`body.lid`	`string`	Optional	Known LinkedIn ID of the person, supplied as a string. This is distinct from the person’s social-profile URL and PDL Persistent ID.
Full name`body.name`	`string`	Optional	Person’s full name, including first and last names. For name-based matching, provide at least one known company, school, location, address or birth-date detail as well.
Known email address`body.email`	`string`	Optional	An email the person has used, supplied for matching. Its use as an identifier does not verify that the address is currently reachable.
Known phone number`body.phone`	`string`	Optional	A phone number the person has used. PDL’s input guide requires a leading + and country code for matching; the number is an identifier, not a contactability check.
PDL Persistent person ID`body.pdl_id`	`string`	Optional	Persistent ID of a person record in PDL. If supplied, only this ID is used for matching and other matching inputs are ignored.
Response indentation`body.pretty`	`boolean`	Optional	Add human-readable JSON indentation when true. Defaults to false and affects formatting only. Default `false`
Residential state or region`body.region`	`string`	Optional	Known state or region where the person lives, used as matching background. It can accompany a full name.
School attended`body.school`	`string`	Optional	Known name, website or social URL of a university or college the person attended. It supplies education context for a match, not confirmation of current enrollment.
Company worked at`body.company`	`string`	Optional	Known name, website or social URL of a company where the person has worked. It helps match a person and does not require that the role is current.
Residential country`body.country`	`string`	Optional	Known country where the person lives, supplied as matching context rather than a search for everyone in that country.
Person social profile`body.profile`	`string`	Optional	Known social profile the person has used, such as a LinkedIn personal profile. Supply one reference as a string.
Residential locality`body.locality`	`string`	Optional	Known locality where the person lives. Use it to help distinguish people with the same or similar names.
Residence location text`body.location`	`string`	Optional	One string describing where the person lives, from a street address to a country name. Use known information as matching context.
Profile availability condition`body.required`	`string`	Optional	Boolean expression over available top-level profile fields, using AND, OR and parentheses. Exclude matching input fields and fields unavailable to the request. This accepts matches with the information needed; it does not create missing data.
Last name`body.last_name`	`string`	Optional	Known last name. Combine it with first_name and at least one known background detail when using the name-based matching route.
Title-case text formatting`body.titlecase`	`boolean`	Optional	Use title case for response text when true. Defaults to false; it changes presentation, not the matched person. Default `false`
Birth year or full date`body.birth_date`	`string`	Optional	Known birth year or full birth date written as YYYY-MM-DD. Supply it as a string to add background for identifying the person.
Email hash`body.email_hash`	`string`	Optional	Known SHA-256 or MD5 hash of the person’s email, used as a matching identifier. It is not a request to recover the email address.
First name`body.first_name`	`string`	Optional	Known first name. For a name-based request, also provide last_name and a known company, school, location, address or birth-date detail.
Middle name`body.middle_name`	`string`	Optional	Known middle name, if applicable. It adds name context but does not replace first and last names in a name-based match.
Residential postal code`body.postal_code`	`string`	Optional	Known residential postal code as text. PDL’s input guide assumes US when country is omitted; supply the known country to clarify the location.
Person fields to include or exclude`body.data_include`	`string`	Optional	Comma-separated profile fields to include, with dot notation for nested fields. One leading minus excludes the following field list; an empty string hides all profile data. Omission requests the full available person profile.
Minimum match confidence`body.min_likelihood`	`integer`	Optional	Integer from 1 to 10, default 2. Matches must meet this confidence threshold to be accepted. A stricter threshold may leave no match; the score is not a percentage. Default `2` Minimum `1` Maximum `10`
Residential street address`body.street_address`	`string`	Optional	Known street address where the person lives. Supply one address as text for matching context.
Return matched-input names`body.include_if_matched`	`boolean`	Optional	When true, add matched with the input names that aligned with the returned profile. Defaults to false; it does not certify all supplied information. Default `false`

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "body": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      },
      "properties": {
        "lid": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "phone": {
          "type": "string"
        },
        "pdl_id": {
          "type": "string"
        },
        "pretty": {
          "type": "boolean",
          "default": false
        },
        "region": {
          "type": "string"
        },
        "school": {
          "type": "string"
        },
        "company": {
          "type": "string"
        },
        "country": {
          "type": "string"
        },
        "profile": {
          "type": "string"
        },
        "locality": {
          "type": "string"
        },
        "location": {
          "type": "string"
        },
        "required": {
          "type": "string"
        },
        "last_name": {
          "type": "string"
        },
        "titlecase": {
          "type": "boolean",
          "default": false
        },
        "birth_date": {
          "type": "string"
        },
        "email_hash": {
          "type": "string"
        },
        "first_name": {
          "type": "string"
        },
        "middle_name": {
          "type": "string"
        },
        "postal_code": {
          "type": "string"
        },
        "data_include": {
          "type": "string"
        },
        "min_likelihood": {
          "type": "integer",
          "default": 2,
          "maximum": 10,
          "minimum": 1
        },
        "street_address": {
          "type": "string"
        },
        "include_if_matched": {
          "type": "boolean",
          "default": false
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Choose a matching route before adding details. A social profile, email, phone, email hash, LinkedIn ID or PDL ID can identify the target. A full name, or first and last names together, needs at least one company, school, location, street address, locality, region, country, postal code or birth-date detail. Middle name alone does not replace that combination. If pdl_id is supplied, it alone is used for matching; response options still apply.

Read the returned person profile inside data, alongside likelihood. Names, job titles, company details and experience are useful when provided, but a record can contain unknown attributes. A company input may refer to somewhere the person has worked, and a school input to somewhere they attended; neither input by itself confirms a current role or enrollment.

Shape the information with data_include. Omission requests the full available person profile; comma-separated names choose fields, and dot notation can select nested fields. Put one minus at the start to exclude the following field list. An empty string hides all profile data. A returned null means the source lacks that attribute, while an excluded field was left out of the requested view.

Use required to accept a match only when specified top-level profile information is available. Combine field names with AND, OR and parentheses. Choose fields available to the request and leave out fields already used as matching inputs. For example, matching by email with required=experience asks for available work-history information; it does not generate missing experience or verify the email.

Likelihood is a 1–10 matching-confidence score. min_likelihood defaults to 2; a stricter threshold may reject a weaker match. include_if_matched defaults to false and can add the names of inputs that aligned with the profile. pretty and titlecase also default to false and affect presentation. Your Agent can arrange the information into a brief, but confidence and formatting do not establish that every attribute is accurate or current.

People Data Labs: person inputs and matching combinations

People Data Labs: person profile, likelihood and matched inputs

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

The documented name route combines a full name, or first and last names, with at least one known company, school, location, address or birth-date detail. Alternatively, use a known email, phone, social profile, email hash, LinkedIn ID or PDL ID. Add facts you already know rather than guessing context to force a match.

Person Profile Lookup · People Data Labs

Person Profile Lookup · People Data Labs

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give us a familiar link or name

Choose what to include

Check that it is the right person

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Give us a familiar link or name

Choose what to include

Check that it is the right person

Questions about this tool.

Can I match a person using only a name?

How do profile, lid and pdl_id differ?

Does an email or phone match verify that I can contact the person?

What changes when I raise min_likelihood?

How can I request a profile with work history?

Is a null or omitted field evidence that the detail does not exist?