Provided by People Data Labs
Enrich up to 10 People in One Call by Email, Phone, Name or Profile URL (PDL)
Enrich up to 10 known people in one call: each entry gives an email address, a phone number, a name with a company, or a social profile URL, and comes back with that person's identity, employment history, location and public profiles. Each entry carries its own match status, so one batch can be part matched and part missed; only matched records are charged.
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/bulk on Glasser.glasser run -p pdl -e '/v5/person/bulk' -i '{"requests":[{"params":{"profile":["linkedin.com/in/seanthorne"]}},{"params":{"email":["someone@example.com"]}}]}' --endpoint-version 1Uses endpoint version 1. 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/bulk","input":{"requests":[{"params":{"profile":["linkedin.com/in/seanthorne"]}},{"params":{"email":["someone@example.com"]}}]},"endpoint_version":1}'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 1; inspect the current price before running.
Step 2Try a specific example task
When you need to assess a prospect for outreach, you might compare their profile with your criteria and note which details still need verification.
Copy this prompt into your agent to review a profile against your outreach criteria.
Use pdl:/v5/person/bulk on Glasser.
Check this profile against my outreach criteria and flag facts I still need to verify.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"requests"
],
"properties": {
"requests": {
"type": "array",
"items": {
"type": "object",
"required": [
"params"
],
"properties": {
"params": {
"type": "object"
}
},
"additionalProperties": false
},
"maxItems": 10,
"minItems": 1
}
},
"additionalProperties": false
}{
"requests": [
{
"params": {
"profile": [
"linkedin.com/in/seanthorne"
]
}
},
{
"params": {
"email": [
"someone@example.com"
]
}
}
]
}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
| Per result returned | Charged for each result returned. No charge when no data is returned. | $0.308 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $3.00 |
| 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 |