# Crustdata Person Contact Enrich

> Crustdata Person Contact Enrich is a paid API for AI agents from crustdata.withzero.xyz, paid per call via MPP, $0.1/call, status unknown (last checked 2026-09-15).

Enriches a person's contact records (business emails, personal emails, phone numbers) from a LinkedIn profile URL or business email via Crustdata.

## Facts

- Endpoint: POST https://crustdata.withzero.xyz/api/v1/person/contact/enrich
- Price: $0.1/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 3
- Provider: crustdata.withzero.xyz
- Website: https://crustdata.withzero.xyz
- Canonical page: https://www.zero.xyz/c/crustdata-withzero-xyz-crustdata-person-contact-enrich-c84909cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_evVXy1C3ql2V56OmN06L6

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 crustdata-withzero-xyz-crustdata-person-contact-enrich-c84909cc -d '<json body>'
```

Example prompt: Find the business email and phone number for the person at https://www.linkedin.com/in/johndoe — just pull the contact.business_emails and contact.phone_numbers fields to keep credits low.

## When to prefer this

Use this endpoint when you specifically need contact-level data (business email, personal email, or phone number) for a person already identified by LinkedIn URL or business email. Prefer this over the general person enrich endpoint when contact fields are the explicit goal. Use selective field requests (e.g. contact.business_emails only) to minimize credit consumption.

## Known failure modes

- Invalid or non-existent LinkedIn profile URL returns Crustdata error and settles $0
- Missing both professional_network_profile_urls and business_emails returns validation error
- Crustdata key lacks contact-enrich entitlement, resulting in authorization error
- More than 25 inputs in either array returns schema validation error
- No matching person found returns empty data with $0 settlement
- Invalid email format in business_emails array triggers input validation failure

## How this service works

Core workflow route: enrich one person's contact records by professional-network profile URL or business email. Use this when the workflow specifically needs business emails, personal emails, or phone numbers; request only the contact sub-fields needed to control credits. Default pricing is $0.10 per Crustdata credit with a $0.01 minimum successful-call settlement. Upstream Crustdata errors settle $0. Contact enrich is priced at one to five Crustdata credits per record and may require contact-enrich entitlement on the configured Crustdata key.

## Output

Returns Crustdata's raw JSON response containing the requested contact fields (business emails with status, personal emails with status, and/or phone numbers) for the specified person, plus billing metadata showing credits consumed, USDC settled, and pricing configuration.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "example": {
  "fields": [
   "contact.business_emails"
  ],
  "professional_network_profile_urls": [
   "https://www.linkedin.com/in/example"
  ]
 },
 "properties": {
  "fields": {
   "type": "array",
   "items": {
    "enum": [
     "contact",
     "contact.business_emails",
     "contact.business_emails.email",
     "contact.business_emails.status",
     "contact.personal_emails",
     "contact.personal_emails.email",
     "contact.personal_emails.status",
     "contact.phone_numbers",
     "crustdata_person_id"
    ],
    "type": "string"
   },
   "example": [
    "contact.business_emails"
   ],
   "description": "Contact data fields to request. Use contact for all contact records, or request specific contact tiers or sub-fields to control credits."
  },
  "business_emails": {
   "type": "array",
   "items": {
    "type": "string",
    "minLength": 1
   },
   "example": [
    "founder@example.com"
   ],
   "maxItems": 25,
   "minItems": 1,
   "description": "Business emails for reverse lookup. Max 25."
  },
  "professional_network_profile_urls": {
   "type": "array",
   "items": {
    "type": "string",
    "minLength": 1
   },
   "example": [
    "https://www.linkedin.com/in/example"
   ],
   "maxItems": 25,
   "minItems": 1,
   "description": "Person profile URLs to enrich for contact data. Max 25."
  }
 },
 "additionalProperties": false
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "data"
 ],
 "properties": {
  "data": {
   "description": "Raw JSON response returned by Crustdata."
  },
  "billing": {
   "type": "object",
   "required": [
    "apiCredits",
    "minimumCallUsdcMicro",
    "pricePerCreditUsdcMicro",
    "settledUsdcMicro"
   ],
   "properties": {
    "apiCredits": {
     "type": "number",
     "example": 0.06,
     "description": "Estimated Crustdata API credits charged for this request."
    },
    "settledUsdcMicro": {
     "type": "string",
     "example": "10000",
     "description": "USDC micro-units settled for this request."
    },
    "minimumCallUsdcMicro": {
     "type": "string",
     "example": "10000",
     "description": "Configured minimum successful-call settlement in USDC micro-units."
    },
    "pricePerCreditUsdcMicro": {
     "type": "string",
     "example": "100000",
     "description": "Configured USDC micro-units charged per Crustdata API credit."
    }
   },
   "additionalProperties": false
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/crustdata-withzero-xyz-crustdata-person-contact-enrich-c84909cc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from crustdata.withzero.xyz](https://www.zero.xyz/host/crustdata.withzero.xyz/llms.txt)