# Happenstance Person Research

> Happenstance Person Research is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-09-14).

Starts an asynchronous person research request given identifying details like name, company, and role

## Facts

- Endpoint: POST https://x402.orthogonal.com/happenstance/v1/research
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/happenstance-person-research-e65d9c1b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__yPELrIUJl9yE4xar1fB1

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 happenstance-person-research-e65d9c1b -d '<json body>'
```

Example prompt: Can you research John Smith, who is the VP of Engineering at Acme Corp? I want to learn as much as possible about his background, experience, and role.

## When to prefer this

Choose this endpoint when you need to research a specific individual and have at least a name plus one additional identifier (company, role, location). It is well-suited for sales lead enrichment, pre-meeting research, candidate due diligence, or any workflow requiring deeper professional background on a named person. Prefer this over generic web search when structured person-profile output is needed rather than raw search results.

## Known failure modes

- Insufficient identifying information provided — too vague a description may return no results or low-confidence profile
- Person not found in available data sources — returns empty or partial results
- Ambiguous identity — multiple people match the description, leading to incorrect profile
- Service unavailable or timeout — research job fails to complete
- Payment failure — USDC transaction not processed, request rejected

## How this service works

Start a new person research request. Include as many details as possible about the person in the description field (name, company, role, etc.).

## Output

The agent receives a research request confirmation and, once processed, a detailed profile of the person including professional background, company affiliation, role details, and any other publicly available identifying information gathered about the individual.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "description": {
   "type": "string",
   "description": "Description of the person to research. Include name, company, role, or any identifying details."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/happenstance-person-research-e65d9c1b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)