Provided by Hunter
Reveal Email Addresses and Phones Behind Masked Search Handles (Hunter)
Reveal the rows of a Hunter masked people search: for each reveal handle you pass in, the person's email address, name, position, phone number and LinkedIn URL when Hunter holds them, with an outcome per handle. The handles are the only input, they must come from a masked search made by the same account, and they stay valid only for the current billing period. Up to 25 handles per call.
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 Hunter endpoint /v2/multi-domain-search/reveal on Glasser.glasser run -p hunter -e '/v2/multi-domain-search/reveal' -i '{"handles":["<reveal_handle from a masked search>"]}' --endpoint-version 1Uses endpoint version 1. 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":"hunter","endpoint":"/v2/multi-domain-search/reveal","input":{"handles":["<reveal_handle from a masked search>"]},"endpoint_version":1}'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 1; inspect the current price before running.
Step 2Try a specific example task
When you need to prepare outreach to a prospect, you might look for a contact email to complete their outreach record.
Copy this prompt into your agent to look up a prospect’s contact email.
Use hunter:/v2/multi-domain-search/reveal on Glasser.
Find the contact email for my prospect so I can prepare an outreach record.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"handles"
],
"properties": {
"handles": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512,
"minLength": 1
},
"maxItems": 25,
"minItems": 1
}
},
"additionalProperties": false
}{
"handles": [
"<reveal_handle from a masked search>"
]
}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.02695 |
|---|---|---|
| Maximum per Run | The total charge will not exceed this amount. | $1.25 |
| 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 |