# CrustData People Search

> CrustData People Search is a paid API for AI agents from api.auor.io, paid per call via x402, $0.05/call, status healthy (last checked 2026-09-14, last successful call 2026-08-18).

Search for people using extensive filters via the CrustData API, returning matching professional profiles

## Facts

- Endpoint: POST https://api.auor.io/crustdata/v1/people/search
- Price: $0.05/call
- Payment: x402
- Status: healthy
- Last checked: 2026-09-14
- Last successful call: 2026-08-18
- Success rate: 50% of calls made through Zero
- Activations on Zero: 8
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-auor-io-53f1f5bd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qEZU4Urm3J5IUhFMWwHwq

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 api-auor-io-53f1f5bd -d '<json body>'
```

Example prompt: Search CrustData for people with the title 'VP of Engineering' who work at Series B SaaS companies in San Francisco — I need a list of leads to reach out to.

## When to prefer this

Use this endpoint when you need to search and discover people profiles using structured, multi-dimensional filters (title, company, location, industry, etc.) via the CrustData dataset. Prefer this over the person enrichment endpoint when you don't have a specific individual's identifier but instead want to find matching people from a set of criteria. It is distinct from place search and is purpose-built for professional contact and lead discovery.

## Known failure modes

- Invalid or missing required filter fields returns a 400 validation error
- Unsupported filter values or combinations return an error — use the filter values endpoint to get valid options
- Insufficient USDC balance or x402 payment failure returns a 402 Payment Required
- Overly broad filters may return too many results or trigger rate limiting
- Filters referencing unknown field names return schema validation errors

## How this service works

Search for people using the CrustData API with extensive filters.

## Output

A list of matching person profiles from CrustData, including professional details such as name, job title, company, location, and other available contact or professional attributes that match the submitted search filters.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "industry": {
   "type": "string"
  },
  "currentCompany": {
   "type": "string"
  },
  "seniorityLevel": {
   "type": "string"
  },
  "companyHeadquarters": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-auor-io-53f1f5bd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.auor.io](https://www.zero.xyz/host/api.auor.io/llms.txt)
