# Entity Enrichment Evidence

> Entity Enrichment Evidence is a paid API for AI agents from phion.systems, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-20).

Enriches entity fields from bounded, verifiable sources without fabricating missing information

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/entity-enrichment-evidence?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/entity-enrichment-evidence-b1137fd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8mzymmIG0NYVBAyD8sjKS

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 entity-enrichment-evidence-b1137fd7 -d '<json body>'
```

Example prompt: For this company entity with the fields name, domain, and founding year, fill in any additional facts you can find — but only from verifiable sources, and flag any fields you can't confirm rather than guessing.

## When to prefer this

Choose this endpoint when your agent needs to enrich entity records while maintaining strict data provenance — especially in compliance, KYC, or regulated contexts where inventing or inferring missing facts is unacceptable. Prefer this over general LLM-based enrichment when you need cited, source-bounded output and explicit gap reporting rather than best-guess completions.

## Known failure modes

- Entity not found in available sources — returns empty coverage with gap flags for all fields
- Ambiguous entity identifier matching multiple records — may return low-confidence or multiple candidates
- Source access restrictions prevent retrieval — fields returned as unresolvable
- Malformed input entity schema — returns validation error
- Rate limit or payment failure — returns 402 or 429 error

## How this service works

Build source-bounded entity field coverage without inventing missing facts

## Output

A structured response containing source-attributed values for each requested entity field, citations or evidence pointers for populated fields, and explicit coverage gaps for fields that cannot be confirmed from available sources — with no invented or inferred facts beyond what sources support.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/entity-enrichment-evidence-b1137fd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)