Provided by Lusha
List the Values a Lusha Company Prospecting Filter Accepts (Lusha)
List every value one Lusha company prospecting filter accepts: size bands, revenue bands, SIC and NAICS codes, industry labels, intent topics, or the names, technologies and locations of companies that match a typed query. Use the values verbatim in the include and exclude filters of Lusha company prospecting; the names dimension also hands back the Lusha company id. One filter dimension per call, free of charge.
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/companies/prospecting/filters/{filterType} on Glasser.glasser run -p lusha -e '/v3/companies/prospecting/filters/{filterType}' -i '{"filterType":"sizes"}' --endpoint-version 4Uses endpoint version 4. 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/companies/prospecting/filters/{filterType}","input":{"filterType":"sizes"},"endpoint_version":4}'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 4; inspect the current price before running.
Step 2Try a specific example task
When you need to qualify potential customers, you might compare company information with your ideal-customer criteria to decide which accounts to research next.
Copy this prompt into your agent to review companies against your ideal-customer criteria.
Use lusha:/v3/companies/prospecting/filters/{filterType} on Glasser.
Check the returned company data against my ideal-customer criteria.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"filterType"
],
"properties": {
"query": {
"type": "string",
"maxLength": 256,
"minLength": 2,
"description": "Search text, 2 to 256 characters. Required for filterType names, technologies and locations; not allowed for any other filterType, which returns its whole list."
},
"filterType": {
"enum": [
"names",
"sizes",
"revenues",
"locations",
"sics",
"naics",
"industriesLabels",
"intentTopics",
"technologies"
],
"type": "string"
}
},
"additionalProperties": false
}{
"filterType": "sizes"
}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
| Data returned or no match | The same price with or without matching data. | $0.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 |