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. When you send both, Hunter uses the LinkedIn handle and ignores the email address: if they belong to two different people, you get the handle's person and the call is charged.
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/people/find on Glasser.glasser run -p hunter -e '/v2/people/find' -i '{"linkedin_handle":"williamhgates"}' --endpoint-version 4Uses endpoint version 4. 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/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. Uses endpoint version 4; 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/people/find 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#",
"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 pricing works
| Data returned | Charged only when data is returned. | $0.0049 |
|---|---|---|
| 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 |