Provided by Lusha
Find the Buying Committee at One Company by Domain or Lusha Id (Lusha)
Find the people who take part in a purchase at one company, named by its domain or its Lusha company id: up to ten person previews grouped by role, each carrying a Lusha contact id, name, title, a priority value and a canReveal flag. Optional personas narrow the roles. One company per call, never a list of companies, and no contact details in the rows; pass the ids to a Lusha reveal Endpoint for them. A company with no matching people is not charged.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"companies",
"contactsLimit"
],
"properties": {
"personas": {
"type": "array",
"items": {
"enum": [
"decision_maker",
"potential_champion",
"end_user"
],
"type": "string"
},
"maxItems": 3,
"minItems": 1,
"description": "Buying-group roles to keep: decision_maker (budget or sign-off authority), potential_champion (likely internal advocate), end_user (likely day-to-day user). These are roles, not departments or job titles. Omit to get all three."
},
"companies": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"maxLength": 200,
"minLength": 3
},
"domain": {
"type": "string",
"maxLength": 253,
"minLength": 3
}
},
"additionalProperties": false
},
"maxItems": 1,
"minItems": 1
},
"contactsLimit": {
"type": "integer",
"maximum": 10,
"minimum": 1
}
},
"additionalProperties": false
}{
"companies": [
{
"domain": "example.com"
}
],
"contactsLimit": 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 Lusha Endpoint /v3/contacts/buying-group on Glasser with input {"companies":[{"domain":"example.com"}],"contactsLimit":3}glasser run -p lusha -e '/v3/contacts/buying-group' -i '{"companies":[{"domain":"example.com"}],"contactsLimit":3}' --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":"lusha","endpoint":"/v3/contacts/buying-group","input":{"companies":[{"domain":"example.com"}],"contactsLimit":3},"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 |