Provided by Hunter
Look Up a Person from an Email Address or LinkedIn Handle (Hunter)
Look up who is behind one email address or one LinkedIn handle and get Hunter's profile of that person: their name, location, short bio, current employer and role, and their social handles. Email addresses and LinkedIn handles are the only two inputs — a person's name will not do, and it is one person per call, never a list of people. An address Hunter does not hold is a clean no-result with no Charge.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"email": {
"type": "string",
"pattern": "^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$",
"maxLength": 254,
"minLength": 3,
"description": "A work email address on the company's own domain, e.g. alexis@reddit.com. Personal webmail such as gmail.com or outlook.com is rejected by Hunter."
},
"linkedin_handle": {
"type": "string",
"maxLength": 100,
"minLength": 1
}
},
"additionalProperties": false
}{
"linkedin_handle": "williamhgates"
}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/people/find on Glasser with input {"linkedin_handle":"williamhgates"}glasser run -p hunter -e '/v2/people/find' -i '{"linkedin_handle":"williamhgates"}' --endpoint-version 4Pinned to version 4, 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/people/find","input":{"linkedin_handle":"williamhgates"},"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. Pinned to version 4 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 |