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.
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/search on Glasser.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 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/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. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to shortlist jobs, you might compare the available roles with your skills to find opportunities worth reviewing more closely.
Copy this prompt into your agent to review job matches for your skills.
Use pdl:/v5/person/search on Glasser.
Find roles matching my skills in the returned job data and explain each match.Endpoint structure
{
"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 pricing works
| Per result returned | Charged for each result returned. No charge when no data is returned. | $0.30 |
|---|---|---|
| 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 |