---
ref: tool:lusha/enrich-person
name: Enrich a person
company: company:lusha
workflows: []
access: [mcp, api]
tags: [capability:enrich-contacts, category:data-provider, has:api, has:mcp]
docs: https://docs.lusha.com/mcp-docs
updated: 2026-09-27
---

# Enrich a person

Returns a person's verified email and direct and mobile phone numbers, with their title and company, found by email, LinkedIn URL, or first name, last name and company.

Pass one lookup path: an email, a LinkedIn URL, or first name, last name and
company name together. `enrich` defaults to true and reveals phones and email
in the same call. When the match may be ambiguous, call it with
`enrich: false` for a preview that spends no reveal credits, then reveal the
chosen person with `prospecting_contact_enrich`; never do both for the same
person, which charges twice.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "lusha": { "url": "https://mcp.lusha.com" } } }
```

Call the MCP tool `contacts_search`.

Server URL: https://mcp.lusha.com

### API (official)

- Base URL: https://api.lusha.com
- Endpoint: `POST /v3/contacts/search-and-enrich`
- Auth: send the header `api_key: $LUSHA_API_KEY`
- Get a key: https://dashboard.lusha.com/enrich/api
- Docs: https://docs.lusha.com/apis/openapi

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.