Provided by People Data Labs
Find Candidate People from a Name with a Company, School or Location (PDL)
Find up to 20 candidate person profiles that match broad clues: a name together with a company, school or location, or a phone number, an email address, a LinkedIn numeric id or a profile URL. Each candidate carries a match score and the clues it matched on, so the caller picks the right one out of the people returned. One fixed charge per call, charged even when nothing matches; use the PDL person lookup Endpoint when one exact match is wanted.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the People Data Labs endpoint /v5/person/identify on Glasser.glasser run -p pdl -e '/v5/person/identify' -i '{"name":"Sean Thorne","company":"peopledatalabs"}' --endpoint-version 2Uses endpoint version 2. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"pdl","endpoint":"/v5/person/identify","input":{"name":"Sean Thorne","company":"peopledatalabs"},"endpoint_version":2}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 2; inspect the current price before running.
Step 2Try a specific example task
When you need to build an outreach shortlist, you might review available people records for prospects who match your targeting criteria.
Copy this prompt into your agent to find prospects matching your outreach criteria.
Use pdl:/v5/person/identify on Glasser.
Find people matching my outreach criteria within the records returned by this endpoint.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"lid": {
"type": "string",
"maxLength": 40,
"minLength": 1
},
"name": {
"type": "string",
"maxLength": 200,
"minLength": 1
},
"email": {
"type": "string",
"maxLength": 320,
"minLength": 1
},
"phone": {
"type": "string",
"maxLength": 40,
"minLength": 1
},
"school": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"company": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"profile": {
"type": "string",
"maxLength": 512,
"minLength": 1
},
"location": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"last_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"first_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
}
},
"additionalProperties": false
}{
"name": "Sean Thorne",
"company": "peopledatalabs"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Data returned or no match | The same price with or without matching data. | $0.38 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |