Provided by Lusha
Reveal Mobile and Direct Dial Lines for Lusha Contact Ids (Lusha)
Reveal the mobile and direct dial lines behind up to five Lusha contact ids that Lusha people prospecting or the buying group Endpoint already handed back. Each record comes back with every line on file, typed mobile or direct, with its country. It takes Lusha contact ids only; an id with no line on file is not charged. When Lusha holds no line for a person, that is the limit of Lusha's coverage, not proof that the person has none; another provider in the catalog may still hold one.
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/enrich?reveal=phones on Glasser.glasser run -p lusha -e '/v3/contacts/enrich?reveal=phones' -i '{"ids":["v1.example-contact-id"]}' --endpoint-version 2Uses endpoint version 2. 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/enrich?reveal=phones","input":{"ids":["v1.example-contact-id"]},"endpoint_version":2}'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 2; inspect the current price before running.
Step 2Try a specific example task
When you need to assess a prospect for outreach, you might compare their profile with your criteria and note which details still need verification.
Copy this prompt into your agent to review a profile against your outreach criteria.
Use lusha:/v3/contacts/enrich?reveal=phones on Glasser.
Check this profile against my outreach criteria and flag facts I still need to verify.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"maxLength": 200,
"minLength": 3
},
"maxItems": 5,
"minItems": 1
}
},
"additionalProperties": false
}{
"ids": [
"v1.example-contact-id"
]
}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.686125 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $4.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 |