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.
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 Lusha endpoint /v3/contacts/buying-group on Glasser.glasser run -p lusha -e '/v3/contacts/buying-group' -i '{"companies":[{"domain":"example.com"}],"contactsLimit":3}' --endpoint-version 5Uses endpoint version 5. 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":"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. Uses endpoint version 5; inspect the current price before running.
Step 2Try a specific example task
When you need to build an outreach shortlist, you might review available people records for prospects who match your targeting criteria.
Copy this prompt into your agent to find prospects matching your outreach criteria.
Use lusha:/v3/contacts/buying-group on Glasser.
Find people matching my outreach criteria within the records returned by this endpoint.Endpoint structure
{
"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 pricing works
| Per result returned | Charged for each result returned. No charge when no data is returned. | $0.137225 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $2.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 |