Provided by Crustdata
List Accepted Filter Values for a Person Search Field (Crustdata)
List the values Crustdata accepts for one person search field — current title, employer name, city, country, school and skill among them — matched against a partial string you type, or ranked by how often each value occurs when you send no string. Use a returned value verbatim in a person search filter, so a search is not rejected for a value the dataset does not hold. One field per call.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"field",
"query"
],
"properties": {
"field": {
"type": "string",
"pattern": "^[a-z0-9_]+(\\.[a-z0-9_]+)*$",
"maxLength": 512,
"minLength": 1,
"description": "Dot-path of one person field whose indexed values to list. Common fields: experience.employment_details.current.title, experience.employment_details.current.name (current employer), experience.employment_details.current.seniority_level, experience.employment_details.current.function_category, experience.employment_details.current.company_industries, experience.employment_details.current.company_headcount_range (swap current for past to list past roles), basic_profile.name, basic_profile.headline, basic_profile.languages, basic_profile.location.country, basic_profile.location.state, basic_profile.location.city, education.schools.school, education.schools.degree, education.schools.field_of_study, skills.professional_network_skills, certifications.name, honors.title, open_to_cards, employment_type. Crustdata can accept more fields than this list: https://docs.crustdata.com/person-docs/autocomplete/introduction"
},
"limit": {
"type": "integer",
"maximum": 100,
"minimum": 1
},
"query": {
"type": "string",
"maxLength": 200
}
},
"additionalProperties": false
}{
"field": "experience.employment_details.current.title",
"limit": 5,
"query": "VP"
}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 Crustdata Endpoint /person/search/autocomplete on Glasser with input {"field":"experience.employment_details.current.title","limit":5,"query":"VP"}glasser run -p crustdata -e '/person/search/autocomplete' -i '{"field":"experience.employment_details.current.title","limit":5,"query":"VP"}' --endpoint-version 5Pinned to version 5, 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":"crustdata","endpoint":"/person/search/autocomplete","input":{"field":"experience.employment_details.current.title","limit":5,"query":"VP"},"endpoint_version":5}'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 5 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 |