> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minerva.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Enrich Input Rules

> Valid identifiers and record shapes for Enrich v2

These rules define valid lookup shapes for [Enrich
v2](/api-reference/enrich-v2). Each record must describe one specific person.
Never combine identifiers from different people or invent missing values.

## Client support

| Client                           | Supported inputs                                       | `record_id`                                                |
| -------------------------------- | ------------------------------------------------------ | ---------------------------------------------------------- |
| REST API                         | All lookup shapes on this page                         | Required                                                   |
| MCP `enrich_people` tool         | All lookup shapes on this page                         | Optional; echoed in the corresponding result when provided |
| [Python SDK](/sdk/guides/enrich) | Minerva PID, LinkedIn URL, or name with email or phone | Required                                                   |

Postal-address inputs are not yet accepted by the Python SDK. Use the REST API
or MCP tool for address matching.

## Choose a lookup shape

Each record must satisfy one of these lookup shapes:

| Lookup                 | Information required                                                    |
| ---------------------- | ----------------------------------------------------------------------- |
| Direct Minerva lookup  | A valid `minerva_pid`                                                   |
| Direct LinkedIn lookup | A valid LinkedIn profile URL or username in `linkedin_url`              |
| Person matching        | A valid name plus at least one valid email, US phone, or postal address |

If a record contains a `minerva_pid`, it takes precedence over all other lookup
fields. A `linkedin_url` is used as the direct identifier only when no
`minerva_pid` is present. Any additional fields are still validated and must
belong to the same person.

## Person matching

Provide either a `full_name` containing a first and last name, or both
`first_name` and `last_name`. Include every accurate email, phone, and address
available; more evidence can improve match confidence.

### Addresses and phones

An address can be supplied as `full_address`, or as parsed fields. Parsed
addresses require `address_line_1` plus either `zipcode` or both `city` and
`state`. Do not mix `full_address` with parsed address fields. Phones must be
10-digit US numbers, optionally formatted with the `+1` country code.

## Matching and returned fields

`match_condition_fields` is a quality gate: it filters a resolved match based
on fields present in the resulting profile. It does not replace the identifying
information above.

`return_fields` only controls which enrichment fields are returned. It does not
affect how a person is identified.