Search users on LinkedIn
4 tools offer Search users on LinkedIn, cheapest first. Pick by price, success rate and latency: every one takes a call with one OrcaRouter API key.
Tools, cheapest first
| Tool | Price | Success (7 days) | Median latency | Runs (30 days) | Tier |
|---|---|---|---|---|---|
| Search LinkedIn profilesSearch LinkedIn profiles by name, company, location, and more | $0.0044 / call | — | — | — | bridged |
| LinkedIn Profile Search (basic)Cheap people search: name/handle, headline, VANITY profile URL, location. No full profile or email - for full profiles per hit use linkedin.search_profiles, add emails with linkedin.search_profiles_email. | $0.0396 / call | 100.0% | 7.9 s | 9 | bridged |
| LinkedIn Profile SearchSearch LinkedIn profiles by keyword with optional location and job-title filters. Each match returns a full profile record: name, headline, location, current position, work experience, education, and skills, plus the profile URL, handle, and id. For a cheaper name/headline/URL-only search use linkedin.search_profiles_thin; add emails with linkedin.search_profiles_email. | $0.198 / call | — | — | — | bridged |
| LinkedIn Profile Search + EmailPeople search returning a full profile AND a verified work email for each hit. Search LinkedIn profiles by keyword with optional location and job-title filters; each match returns the full profile record (name, headline, location, current position, work experience, education, and skills, plus the profile URL, handle, and id) together with an emails array carrying the discovered work email and its | $0.37 / call | — | — | — | bridged |
Find them from an agent
curl https://api.orcarouter.ai/v1/tools/discover \
-H "Authorization: Bearer $ORCAROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q":"LinkedIn Search users"}'Questions
How much does Search users on LinkedIn cost?
4 tools offer it, from $0.0044 per call.
How fast are these tools?
Their median response time is 7895 ms.
How does an agent use these tools?
With one OrcaRouter API key: POST /v1/tools/discover finds them and POST /v1/tools/{id}/run calls one, with the same request shape for every tool here.
