Provided by Prospeo
Find a Verified Mobile Phone Number from a LinkedIn URL, an Email or a Name and Employer (Prospeo)
Find one person's verified mobile phone number, returned with their profile. Identify them by LinkedIn profile URL, by an email address you already hold, or by a name together with their employer. It costs ten times the address lookup because Prospeo charges ten times as much to reveal a number — that is why it is a separate Endpoint and not a flag. Nothing is charged when no number is found.
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 Prospeo endpoint /enrich-person?enrich_mobile=true on Glasser.glasser run -p prospeo -e '/enrich-person?enrich_mobile=true' -i '{"linkedin_url":"https://www.linkedin.com/in/ivanhzhao"}' --endpoint-version 1Uses endpoint version 1. 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":"prospeo","endpoint":"/enrich-person?enrich_mobile=true","input":{"linkedin_url":"https://www.linkedin.com/in/ivanhzhao"},"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. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to build an outreach shortlist, you might review available people records for prospects who match your targeting criteria.
Copy this prompt into your agent to find prospects matching your outreach criteria.
Use prospeo:/enrich-person?enrich_mobile=true on Glasser.
Find people matching my outreach criteria within the records returned by this endpoint.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"email": {
"type": "string",
"maxLength": 254,
"minLength": 5
},
"full_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"last_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"first_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"company_name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"linkedin_url": {
"type": "string",
"pattern": "^https:\\/\\/(www\\.)?linkedin\\.com\\/",
"maxLength": 300
},
"company_website": {
"type": "string",
"pattern": "^(?!-)(?:[a-z0-9-]+\\.)+[a-z]{2,}$",
"maxLength": 253,
"minLength": 3
}
},
"additionalProperties": false
}{
"linkedin_url": "https://www.linkedin.com/in/ivanhzhao"
}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.2695 |
|---|---|---|
| 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 |