# Get a profile from a LinkedIn URL

> Get a profile from a LinkedIn URL: 1 companies fully do it, 13 with a limit, 40 carry the tag. Every listing in Lead & company data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/lead-data.linkedin-profile-lookup/
- Markdown: https://www.anchorterminal.com/niches/lead-data.linkedin-profile-lookup/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/lead-data.linkedin-profile-lookup/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/lead-data.linkedin-profile-lookup/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 13 | 40 | 8 | 5 |

## 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.

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

The docs show it meets the test above, and nothing we read says otherwise.

- **Crustdata API + MCP (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.

## Does the job, with a limit

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.

- **Apollo API + MCP (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.
- **Coresignal API + MCP (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.
- **Databar (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.
- **Enrich Layer API + MCP (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.
- **Explorium AgentSource (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.
- **FullContact (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.
- **FullEnrich API + MCP (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.
- **Fuse MCP (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.
- **LeadMagic API + MCP (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.
- **Lusha API + MCP (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.
- **People Data Labs (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.
- **Prospeo API + MCP (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.
- **RocketReach API (RocketReach, LLC)**: A LinkedIn URL is a lookup identifier and person_enrich returns profile metadata, but no collection timestamp was found.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Clay (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 (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 (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.

- not this job: Clearbit (HubSpot, Inc.): No public API takes a LinkedIn URL for a new customer; docs redirect to login.
- not this job: Dievio (Dievio): LinkedIn Lookup takes up to 100,000 URLs but returns emails and optional phones, not headline, roles or education, and no collection timestamp.
- not this job: Dropcontact API + MCP (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.
- not this job: Hunter API + MCP (Hunter Web Services, Inc.): linkedin_handle is only a finder input; no endpoint returns roles or education for a LinkedIn URL.
- not this job: ZeroBounce (Hertza L.L.C.): No LinkedIn profile lookup.

## 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)

As data: https://www.anchorterminal.com/api/v1/use-cases/lead-data.linkedin-profile-lookup.json, or the MCP tool get_use_case with id lead-data.linkedin-profile-lookup. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
