Provided by Hunter
Find a Person's Work Email from Their Name and Company Domain (Hunter)
Find the most likely work email address for one named person at a company domain, derived from Hunter's address pattern for that domain and from the pages its addresses were seen on. Returns one address with a confidence score and a verification status. A pattern-derived guess is returned, and charged, even when Hunter has never seen that person — read the score before you trust it.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"maxLength": 255,
"minLength": 3,
"description": "The company's own domain, e.g. \"stripe.com\"."
},
"full_name": {
"type": "string",
"maxLength": 100,
"minLength": 3,
"description": "First and last name in one string, e.g. \"Patrick Collison\". A single word is rejected by Hunter."
},
"last_name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The person's spelled-out last name, e.g. \"Collison\". Initials only (such as \"P G\") are rejected by Hunter."
},
"first_name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The person's first name. Give it together with last_name, or use full_name."
},
"max_duration": {
"type": "integer",
"maximum": 20,
"minimum": 3
}
},
"additionalProperties": false
}{
"domain": "stripe.com",
"last_name": "Collison",
"first_name": "Patrick"
}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/email-finder on Glasser with input {"domain":"stripe.com","last_name":"Collison","first_name":"Patrick"}glasser run -p hunter -e '/v2/email-finder' -i '{"domain":"stripe.com","last_name":"Collison","first_name":"Patrick"}' --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/email-finder","input":{"domain":"stripe.com","last_name":"Collison","first_name":"Patrick"},"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 |