# Minerva Enrich - Person Record Enrichment

> Minerva Enrich - Person Record Enrichment is a paid API for AI agents from stableenrich.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15, last successful call 2026-07-17).

Enriches person records with demographics, work history, contact info, and wealth/income data using name, email, phone, or LinkedIn URL as input identifiers

## Facts

- Endpoint: POST https://stableenrich.dev/api/minerva/enrich
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Last successful call: 2026-07-17
- Success rate: 60% of calls made through Zero
- Rating: 3.0 / 5 from 2 reviews
- Activations on Zero: 5
- Tags: x402
- Canonical page: https://www.zero.xyz/c/minerva-enrich-person-record-enrichment-5b7e865f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MvIuI7pIJu6AaLtdS35bq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability minerva-enrich-person-record-enrichment-5b7e865f -d '<json body>'
```

Example prompt: Enrich this person record using Minerva — I have their name 'Jane Smith', email 'jane.smith@example.com', and LinkedIn 'https://linkedin.com/in/janesmith' — and return their phone numbers, estimated income range, work experience, and personal emails.

## When to prefer this

Use this endpoint when you need to append rich demographic, financial, and contact data to person records you already have partial identifiers for (name, email, phone, LinkedIn). Prefer it over a people search endpoint when you have existing records to match and enrich rather than needing to discover new prospects. Best for CRM enrichment, identity resolution, and building detailed person profiles at scale (up to 500 records per call).

## Known failure modes

- No match found: is_match returns false when the provided identifiers don't resolve to a known person
- Low match score: ambiguous inputs like a common name without email/phone may return low-confidence matches
- Validation error: records array is empty or exceeds 500 items
- Invalid match_condition_fields: using field names not in the allowed enum list causes a 400 error
- Rate or payment failure: insufficient USDC balance or x402 payment issue causes request rejection
- Partial enrichment: some requested return_fields may be null if data is unavailable for that person

## How this service works

Pay-per-request access to FullEnrich, CompanyEnrich, LeadMagic, Clado, Exa, Firecrawl, Google Maps, Serper, and Whitepages APIs. No auth, no subscriptions.

## Output

An array of matched person records, each containing a match score, Minerva person ID, full demographics (age, gender, DOB, marital status), contact info (phones ranked by type, personal and professional emails), work experience, LinkedIn/Twitter/Facebook URLs, estimated income and wealth ranges, home ownership status, retirement status, and relatives — alongside request metadata like api_request_id and completion timestamp.

## Example request

```json
{
 "records": [
  {
   "emails": [
    "john.smith@example.com"
   ],
   "full_name": "John Smith",
   "record_id": "test_001"
  }
 ],
 "return_fields": [
  "full_name",
  "personal_emails",
  "phones",
  "work_experience"
 ]
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "records": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "emails": {
      "type": "array",
      "items": {
       "type": "string"
      },
      "description": "Array of email addresses"
     },
     "phones": {
      "type": "array",
      "items": {
       "type": "string"
      },
      "description": "Array of phone numbers"
     },
     "full_name": {
      "type": "string",
      "description": "Person's full name"
     },
     "last_name": {
      "type": "string",
      "description": "Person's last name"
     },
     "record_id": {
      "type": "string",
      "description": "Your unique identifier for this record"
     },
     "first_name": {
      "type": "string",
      "description": "Person's first name"
     },
     "middle_name": {
      "type": "string",
      "description": "Person's middle name"
     },
     "minerva_pid": {
      "type": "string",
      "description": "Direct Minerva Person ID lookup for instant enrichment"
     },
     "name_suffix": {
      "type": "string",
      "description": "Name suffix (e.g., \"Jr.\", \"Sr.\", \"III\")"
     },
     "linkedin_url": {
      "type": "string",
      "description": "LinkedIn profile URL for direct enrichment"
     }
    },
    "additionalProperties": false
   },
   "minItems": 1,
   "description": "Array of person records to enrich. Maximum 500 per request."
  },
  "return_fields": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Fields to return beyond base fields. Alias: \"education\" → \"education_experience\". Omit to return all fields. Example: [\"full_name\", \"personal_emails\", \"phones\", \"work_experience\"]."
  },
  "match_condition_fields": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Fields that must be present for a match to be returned. Alias: \"email\" → \"emails\". Valid options include \"emails\", \"linkedin_url\", \"gender\", \"estimated_income_range\", \"estimated_wealth_range\", \"personal_email\", \"professional_email\", \"phone\", \"mobile_phone\", \"home_ownership_status\"."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/minerva-enrich-person-record-enrichment-5b7e865f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stableenrich.dev](https://www.zero.xyz/host/stableenrich.dev/llms.txt)