--- title: "What is a LinkedIn profile URL lookup? definition for outreach – Invenitor" description: "LinkedIn profile URL lookup defined: paste a person URL, get email/phone when found. Coverage. REST + MCP. Not a sales cloud." url: https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup agents: https://invenitor.com/llms.txt mcp: https://api.invenitor.com/mcp --- [Blog](https://invenitor.com/blog) Oct 6, 2026 · 9 min read · API # What is a LinkedIn profile URL lookup? What is a LinkedIn profile URL lookup? A find call with a person profile URL that returns email/phone when available. On this page 1. [What goes in](#what-goes-in) 2. [What comes out](#what-comes-out) 3. [Coverage coverage (no public hit-rate %)](#coverage-coverage-no-public-hit-rate) 4. [How lookup differs from CRM and sequencers](#how-lookup-differs-from-crm-and-sequencers) 5. [Credits and billing for a lookup](#credits-and-billing-for-a-lookup) 6. [REST and MCP twins](#rest-and-mcp-twins) 7. [Desk usage in one sentence](#desk-usage-in-one-sentence) 8. [What should you do next?](#what-should-you-do-next) 9. [Common mistakes that look like “lookup failed”](#common-mistakes-that-look-like-lookup-failed) 10. [Teaching juniors the lookup sentence](#teaching-juniors-the-lookup-sentence) 11. [Lookup vs people-search theater](#lookup-vs-people-search-theater) A **LinkedIn profile URL lookup** is a find operation: you send a person profile URL (and optionally a name), and a contact lookup API returns email, phone, or links **when it has them**. Invenitor’s shape: A people search and lookup API, not a sales cloud. Category parent: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). Hub HowTo: [LinkedIn or GitHub Profile URL → Contact Lookup API](https://invenitor.com/blog/linkedin-github-contact-lookup-api). ## What goes in - A **person** LinkedIn profile URL (not a company page, not a search URL, not a post permalink). - Optional display name to help disambiguation. - Auth: Bearer API key (). Same family: GitHub person profile URLs – [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). ## What comes out When found: primary email and/or phone (and links when present). When failing: error/timeout – not a fictional contact. ## Coverage coverage (no public hit-rate %) Coverage varies by person and source. Honest language is intentional: we return contacts **when we have them**. We do not publish hit-rate percentages. Sample your own shortlist; do not buy a brochure %. ## How lookup differs from CRM and sequencers | Layer | Job | | ---------- | --------------------------- | | Lookup API | URL → fields when found | | CRM / CRM | Store people, stages, notes | | Sequencer | Outreach automation | Do not force a sales cloud to get a find. ## Credits and billing for a lookup 1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Live packs: . PAYG: [Pay-As-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). ## REST and MCP twins REST: `POST /api/v1/find` per . Agents: MCP per – [Claude / Cursor Agents: Calling a Contact Lookup MCP Endpoint](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint), ## Desk usage in one sentence ## What should you do next? Buy a pack on when ready. That is a LinkedIn profile URL lookup – not a cold-email cloud with a URL field. ## Common mistakes that look like “lookup failed” Free-plan traps: [The Hidden Cost of "Free Plan" Enrichment Tools](https://invenitor.com/blog/the-hidden-cost-of-free-plan-enrichment-tools-for-small). ## Teaching juniors the lookup sentence Paste person URL. Call find. If fields exist, save them. That sentence belongs in every SOP – Agents: , [Claude / Cursor Agents](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint). India commercial: [INR Credit Packs](https://invenitor.com/blog/inr-credit-packs-for-contact-lookup-how-razorpay-pricing-feels), Coverage: contacts when we have them – no brochure hit-rate %. ## Lookup vs people-search theater Category parent: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). Free-plan traps: [The Hidden Cost of "Free Plan" Enrichment Tools](https://invenitor.com/blog/the-hidden-cost-of-free-plan-enrichment-tools-for-small). PAYG: [Pay-As-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). Global INR rail: [US Price Arbitrage](https://invenitor.com/blog/us-price-arbitrage-why-some-teams-buy-inr-credit-apis). Live: · . ## Questions What is a LinkedIn profile URL lookup?+ A find call with a person LinkedIn profile URL that returns email/phone when available. Can I use a company page URL?+ No. Use person profile URLs. Company pages are the wrong input. When does a credit spend?+ 1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Is GitHub supported the same way?+ Yes – person GitHub profile URLs on the same find path. Where are REST and MCP docs?+ /docs for REST and /mcp.md for agents. How is this different from a CRM?+ Lookup resolves fields from a URL. A CRM stores workflow. Invenitor is not a sales cloud. ## Find the person you need Describe who you need in one sentence. Your first search is free, and you pay only for contacts we find [Find people free](https://invenitor.com/login?from=https%3A%2F%2Fpeople.invenitor.com%2Fsearch&x=w7&q=c5&z=g1)[See pricing](https://invenitor.com/pricing?x=w7&q=c5&z=g2) ## Keep reading - [Nov 3, 2026 · APINames help too: How optional full name improves lookup requestsNames help too: how optional full name improves lookup requests – URL remains primary; name is a soft hint; empties stay empty under coverage.](https://invenitor.com/blog/names-help-too-how-optional-full-name-improves-lookup-requests) - [Oct 27, 2026 · APIError codes buyers should expect from a lookup APIError codes buyers should expect from a lookup API – auth failures, rate limits, validation, and server faults – with honest empty vs error billing semantics.](https://invenitor.com/blog/error-codes-buyers-should-expect-from-a-lookup-api) - [Oct 19, 2026 · APIRate limits and keys: Operating a contact lookup API in productionRate limits and keys: operating a contact lookup API in production – key hygiene, 429 backoff, and found-only credits when enrichment is live.](https://invenitor.com/blog/rate-limits-and-keys-operating-a-contact-lookup-api-in)