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.
When to use resolve vs enrich
| You need | Use |
|---|---|
| Just the Minerva PID (dedupe, key lookup, ID-to-ID linking) | mc.api.resolve |
| The full person profile | mc.api.enrich |
resolve is cheaper than enrich per matched record. Both run the same matching logic — the difference is what comes back.
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. A record only counts as a match if the resolved person actually
has these fields. Up to 3.
Validate input locally without sending. Returns the
ResolveRequest that
would be sent. See Validation.Response shape
match.results is a list of ResolveResult objects with record_id,
is_match, minerva_pid, match_score. The response is typed end-to-end —
IDE autocomplete + mypy will check field access for you.
Tabular output
Limits
- Records per call: 500
- Validation enforced locally before the call — over-limit records raise
MinervaValidationErrorwithout a round-trip - Billing: see your plan for per-resolve / per-match pricing

