Provided by People Data Labs
Search People by Job Title, Employer or Location with a SQL or Elasticsearch Query (PDL)
Find people in the PDL person dataset by writing one Elasticsearch query body or one SQL SELECT statement over person fields such as job title, seniority, employer, employer website, city, country, school and skill. Each person row carries identity, employment history, location, public social handles and the contact fields PDL holds. Up to 10 people per call, charged per record returned; one query form per call, never both.
Contract snapshot: 2026-09-24. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"sql": {
"type": "string",
"minLength": 1
},
"size": {
"type": "integer",
"maximum": 10,
"minimum": 1
},
"query": {
"type": "object"
}
},
"additionalProperties": false
}{
"sql": "SELECT * FROM person WHERE job_company_website='stripe.com' AND job_title_levels='cxo'",
"size": 3
}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 to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
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.mdThen ask for this Endpoint:
Run the People Data Labs Endpoint /v5/person/search on Glasser with input {"sql":"SELECT * FROM person WHERE job_company_website='stripe.com' AND job_title_levels='cxo'","size":3}glasser run -p pdl -e '/v5/person/search' -i '{"sql":"SELECT * FROM person WHERE job_company_website='\''stripe.com'\'' AND job_title_levels='\''cxo'\''","size":3}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. 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/search","input":{"sql":"SELECT * FROM person WHERE job_company_website='\''stripe.com'\'' AND job_title_levels='\''cxo'\''","size":3},"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. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |