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.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"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 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 Hunter Endpoint /v2/multi-domain-search/reveal on Glasser with input {"handles":["<reveal_handle from a masked search>"]}glasser run -p hunter -e '/v2/multi-domain-search/reveal' -i '{"handles":["<reveal_handle from a masked search>"]}' --endpoint-version 1Pinned to version 1, 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":"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. Pinned to version 1 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 |