--- title: "Names help too: How optional full name improves lookup requests – Invenitor" description: "How optional full name improves LinkedIn or GitHub URL lookup requests – better matching hints, still empty means not found, no invented contacts." url: https://invenitor.com/blog/names-help-too-how-optional-full-name-improves-lookup-requests agents: https://invenitor.com/llms.txt mcp: https://api.invenitor.com/mcp --- [Blog](https://invenitor.com/blog) Nov 3, 2026 · 9 min read · API # Names help too: How optional full name improves lookup requests Names help too: how optional full name improves lookup requests – URL remains primary; name is a soft hint; empties stay empty under coverage. On this page 1. [Request shape that stays honest](#request-shape-that-stays-honest) 2. [Why names help (without guaranteeing finds)](#why-names-help-without-guaranteeing-finds) 3. [UX: collect name without dark patterns](#ux-collect-name-without-dark-patterns) 4. [Agents and MCP](#agents-and-mcp) 5. [Credits unchanged](#credits-unchanged) 6. [What should you do next?](#what-should-you-do-next) 7. [Procurement one-liner](#procurement-one-liner) 8. [Request examples (conceptual)](#request-examples-conceptual) 9. [Sheet column tip](#sheet-column-tip) Profile URL is the primary key for honest contact lookup. Optional full name is a **hint**, not a license to invent. When desks send both LinkedIn URL and the person's name as written on the brief, coverage matching can improve – without changing empty-means-not-found. Invenitor is a people search and lookup API, not a sales cloud. Coverage varies; we do not publish hit-rate percentages. Hub: [LinkedIn or GitHub Profile URL → Contact Lookup API](https://invenitor.com/blog/linkedin-github-contact-lookup-api). Primer: [What Is a LinkedIn Profile URL Lookup?](https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup). GitHub: [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). Primary fields: One Primary Contact, Never Invented. ## Request shape that stays honest | Field | Required? | Role | | --------------- | ------------- | ------------------------------ | | Profile URL | Yes (primary) | Canonical find key | | Full name | Optional | Disambiguation hint | | Company / title | Optional | Context only – not invent fuel | | Source CRM id | Optional | Your correlation | Keys: [Rate Limits and Keys](https://invenitor.com/blog/rate-limits-and-keys-operating-a-contact-lookup-api-in). Errors: [Error Codes Buyers Should Expect](https://invenitor.com/blog/error-codes-buyers-should-expect-from-a-lookup-api). ## Why names help (without guaranteeing finds) Names reduce collisions when URLs are truncated, rewritten, or pasted from mobile. They do **not** authorize guessing `@company.com`. Honesty: Empty Means Not Found. Billing: Credits, Empty Results, and Timeouts. Marketing: [When We Have Them](https://invenitor.com/blog/when-we-have-them-writing-honest-marketing-for-contact-apis). ## UX: collect name without dark patterns In Add person, keep name for the person record anyway – then pass it optionally on enrich. ## Agents and MCP Agent tools should accept optional `full_name` beside `profile_url`. Prompt: if empty, do not invent. MCP: , [Agent-Readable Docs](https://invenitor.com/blog/agent-readable-docs-why-mcp-md-matters-for-contact-apis), [Claude / Cursor Agents](https://invenitor.com/blog/claude-cursor-agents-calling-a-contact-lookup-mcp-endpoint), ## Credits unchanged Optional name does not change found-only billing. 1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend. Primer: [What Are API Credits](https://invenitor.com/blog/what-are-api-credits-in-enrichment-products). Pay-per-lookup: [What Is Pay-Per-Lookup Pricing?](https://invenitor.com/blog/what-is-pay-per-lookup-pricing). Packs: , [25 to 1,000 Credits](https://invenitor.com/blog/25-to-1-000-credits-choosing-an-inr-pack-size). ## What should you do next? Add optional full name to your enrich payload. Keep empty UI honest. Verify against and . ## Procurement one-liner We send profile URL plus optional full name to a soft-mesh lookup – empties stay empty; credits remain found-only. ## Request examples (conceptual) URL only: coverage find. URL + full name: same found-only billing; better disambiguation when the URL is noisy. Name only: insufficient – do not invent. Honesty: Empty Means Not Found. Primary: One Primary Contact, Never Invented. Billing: Credits, Empty Results, and Timeouts. Primer: [What Are API Credits](https://invenitor.com/blog/what-are-api-credits-in-enrichment-products). Pay-per-lookup: [What Is Pay-Per-Lookup Pricing?](https://invenitor.com/blog/what-is-pay-per-lookup-pricing). Trust: [Trust Checklist](https://invenitor.com/blog/trust-checklist-before-you-buy-any-contact-api). Marketing: [When We Have Them](https://invenitor.com/blog/when-we-have-them-writing-honest-marketing-for-contact-apis). Hub: [LinkedIn or GitHub Profile URL → Contact Lookup API](https://invenitor.com/blog/linkedin-github-contact-lookup-api). LinkedIn: [What Is a LinkedIn Profile URL Lookup?](https://invenitor.com/blog/what-is-a-linkedin-profile-url-lookup). GitHub: [GitHub Profile URL Contact Lookup](https://invenitor.com/blog/github-profile-url-contact-lookup-when-developer-profiles-are-the). Keys: [Rate Limits and Keys](https://invenitor.com/blog/rate-limits-and-keys-operating-a-contact-lookup-api-in). Errors: [Error Codes Buyers Should Expect](https://invenitor.com/blog/error-codes-buyers-should-expect-from-a-lookup-api). Agents: , llms.txt for Contact APIs. Packs: [25 to 1,000 Credits](https://invenitor.com/blog/25-to-1-000-credits-choosing-an-inr-pack-size). · . ## Sheet column tip Keep `full_name` and `profile_url` separate; never overwrite empty phone with a guessed string from the name. ## Questions Is full name required for lookup?+ No. Profile URL is primary. Full name is an optional matching hint. Can name alone trigger inventing an email?+ Never. Empty means not found even when a name is present. Does sending a name spend an extra credit?+ No. Found-only billing is about found email/phone outcomes – not about optional hint fields. Where should CRM builders put the name field?+ On the person record and optionally in the enrich request beside the URL. How should agents treat optional name?+ Pass it when known; if lookup returns empty, stop – do not fabricate contacts. What docs cover request shape?+ /docs, OpenAPI hygiene, and LinkedIn/GitHub hub posts. How does Invenitor frame this?+ Reaching people; a lookup API that accepts honest hints without inventing fills. ## 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 - [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) - [Oct 12, 2026 · APIContact lookup API vs CRM vs sequencer: Pick the right layerContact lookup API vs CRM vs sequencer: pick the right layer – find contacts from profile URLs without buying a sales cloud or dialer stack.](https://invenitor.com/blog/contact-lookup-api-vs-crm-vs-sequencer-pick-the-right)