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.
Parameters
Up to 500 per call. Each must have
record_id + at least one matching field
(LinkedIn URL, emails, name, etc.).API version.
Quality gate (up to 3). A record only counts as a match if the resolved
person actually has these fields. Useful when you need contact info you can
act on (e.g. require a
phone). Omit to match on resolution alone.Narrow the response payload to just these fields. Reduces wire size; doesn’t
affect billing.
Validate input locally without sending. Returns the
EnrichRequest that
would be sent. See Validation.Response shape
Each result includes:| Field | What |
|---|---|
personal_information | full_name, gender, dob, age, … |
household_information | Household composition + income range |
financial_information | Estimated income, net worth, etc. |
social_media | Public profile URLs |
personal_emails, professional_emails | Ranked email arrays |
phones | Verified phone numbers |
address_history | Past + current addresses |
work_experience | Employment history |
education_experience | Schools + degrees |
relatives | Linked household members |
match_condition_fields is a quality gate — a record only counts as a
match if the resolved person actually has those fields (e.g. require a
phone you can dial). Omit it to match on resolution alone.Tabular output
personal_information.full_name) flatten into top-level
columns in the DataFrame. See Output formats.
Map onto your own schema
Project any result onto your pydantic model — missing fields becomeNone (with a one-time warning), so it never breaks:
Limits
- Records per call: 500
- Validation enforced locally before the call — over-limit records raise
MinervaValidationErrorwithout a round-trip - Billing: credits consumed per matched record — see your plan

