Provided by LeadMagic
Look Up the Person Record Behind a LinkedIn Profile URL (LeadMagic)
Look up the person behind one LinkedIn profile URL: their name, title, bio, employer, location and work history. One profile URL per call, one person rather than a list of people, and no contact details in the record. A credit is spent only when a record comes back.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"profile_url"
],
"properties": {
"profile_url": {
"type": "string",
"maxLength": 512,
"minLength": 1
}
},
"additionalProperties": false
}{
"profile_url": "https://www.linkedin.com/in/patrickcollison"
}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 LeadMagic Endpoint /v1/people/profile-search on Glasser with input {"profile_url":"https://www.linkedin.com/in/patrickcollison"}glasser run -p leadmagic -e '/v1/people/profile-search' -i '{"profile_url":"https://www.linkedin.com/in/patrickcollison"}' --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":"leadmagic","endpoint":"/v1/people/profile-search","input":{"profile_url":"https://www.linkedin.com/in/patrickcollison"},"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 |