Get a profile from a LinkedIn URL
One company's docs show a full fit.
What counts as done
Name, headline, current and past roles, education and company details for the URL, with a collection timestamp and a stated longer bound for live lookups.
Measured, for our own tests: within 10 seconds for a cached record. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: pull the work history for this LinkedIn profile
, enrich these 300 LinkedIn URLs
, what does this company's LinkedIn page say
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Crustdata API + MCP D Crustdata Inc. | Person enrich takes profile URLs, 25 a request, and returns roles, education and updated_at; the indexed record refreshes every 1 to 30 days and a live enrich exists on enterprise plans or the live add-on. source |
Does the job, with a limit 13
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Apollo API + MCP B ZenLeads Inc. d/b/a Apollo.io | people/match accepts linkedin_url and returns current and past roles from Apollo's index, but no collection timestamp or education field was found and there is no live-fetch mode. source |
| Coresignal API + MCP B Deeptrace Inc. | Collect takes a profile URL or shorthand name from the index, and the Real-time Employee API fetches live at 12 credits, but real-time is on request and no latency bound was read. source |
| Databar C Databar, Inc. | The Email by link waterfall takes a LinkedIn URL for work and personal emails, but a profile-history lookup from a URL and any collection timestamp weren't found in the pages read. source |
| Enrich Layer API + MCP C Vertical Int, Inc. | /profile takes a profile URL and returns headline, experiences, education and last_updated; use_cache=if-recent promises under 29 days and live_fetch=force costs 9 more, but the map's blockers apply: 30 to 100 second responses and 2 requests a minute on trial keys. source |
| Explorium AgentSource E Explorium Ltd. | A LinkedIn URL is the first identifier match tries, and Profiles enrichment returns the record, but no collection timestamp or latency bound was found in the pages read. source |
| FullContact E J2 Martech Corp. | A LinkedIn URL is a documented input and the Employment History bundle returns current and past roles, but no collection timestamp is shown and bundles depend on the contract. source |
| FullEnrich API + MCP B FullEnrich Corp | Look Up People accepts a LinkedIn URL or ID, but no collection timestamp or latency bound was read; the search docs say the database updates monthly. source |
| Fuse MCP D FuseAI, LLC | LinkedIn profile scrapes cost 50 credits a profile, but no collection timestamp or time bound was found, and scraping carries the legal exposure the map names. source |
| LeadMagic API + MCP B Lead Magic Corporation | profile-search takes a profile URL and returns work history, education and certifications at 1 credit, but no collection timestamp or latency bound was found. source |
| Lusha API + MCP B Lusha Systems Inc. | A LinkedIn URL is a search identifier and Enrich returns previous employment, but no education field or collection timestamp was found in the guides read. source |
| People Data Labs C People Data Labs, Inc. | A LinkedIn profile URL or lid is a documented input and returns the person record on a match, but no collection timestamp or refresh statement was found in the reference read. source |
| Prospeo API + MCP D Defastra Tech Inc. | linkedin_url is a matching input and the record carries a jobs history, but no collection timestamp or education was found in the reference read. source |
| RocketReach API D RocketReach, LLC | A LinkedIn URL is a lookup identifier and person_enrich returns profile metadata, but no collection timestamp was found. source |
Couldn't check 3
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Clay C Clay Labs Inc. | Company search results carry linkedin_url, but no function that takes a LinkedIn person URL and returns roles and education is documented on the pages read. |
| Gojiberry D SUPERFRUITS SAS | Contacts carry a LinkedIn identifier, but whether a contact can be created from any profile URL and what history comes back wasn't read. |
| ZoomInfo API + MCP BB ZoomInfo Technologies LLC | Social URLs appear in enrich output, but whether a LinkedIn URL is accepted as the match input wasn't found in the schema read. |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Clearbit F HubSpot, Inc. | No public API takes a LinkedIn URL for a new customer; docs redirect to login. source |
| Dievio F Dievio | LinkedIn Lookup takes up to 100,000 URLs but returns emails and optional phones, not headline, roles or education, and no collection timestamp. source |
| Dropcontact API + MCP C Dropcontact SAS | A LinkedIn URL is accepted as input, but the output is email, current job and company only, with no past roles, education or collection date. source |
| Hunter API + MCP C Hunter Web Services, Inc. | linkedin_handle is only a finder input; no endpoint returns roles or education for a LinkedIn URL. source |
| ZeroBounce B Hertza L.L.C. | No LinkedIn profile lookup. source |
What stops agents finishing
- live profile endpoints taking 30 to 100 seconds (enrich-layer)
- legal exposure after the Proxycurl shutdown and LinkedIn suits (acc-31 context)
- trial keys at 2 requests a minute until a top-up (enrich-layer)
Around it
Before: web-scrapers.platform-structured-data, lead-data.prospect-list-by-filter. After: lead-data.find-work-email, lead-data.enrich-known-contact.
Where this comes from
Weight 8 of 100 in Lead & company data: 5 of 39 accounts (acc-06, 10, 12, 14, 31)
The same as data: /api/v1/use-cases/lead-data.linkedin-profile-lookup.json, or the MCP tool get_use_case with id lead-data.linkedin-profile-lookup. Other jobs in this category: /api/v1/niches?category=lead-data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.