When to use resolve vs enrich
resolve is cheaper than enrich per matched record. Both run the same matching logic — the difference is what comes back.
Parameters
list[dict]
required
Up to 500 per call. Each must have
record_id + at least one matching field
(LinkedIn URL, emails, name, etc.).str
default:"\"v2\""
API version.
list[str]
Quality gate. A record only counts as a match if the resolved person actually
has these fields. Up to 3.
bool
default:"False"
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.
match_score is an additive point total, not a 0-1 or 0-100 confidence — every
match scores at least 50 and strong ones routinely exceed 100, so don’t
threshold it as a percentage. It’s None when is_match is false. See
Interpreting match_score.
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