# PHION Enrich Basic

> PHION Enrich Basic is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-22).

Provider-backed basic entity enrichment with explicit match confidence, limitations, and a signed receipt, paid per-call via x402.

## Facts

- Endpoint: POST https://phion.systems/v1/paid/commercial/enrich-basic?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phion-enrich-basic-5591d5f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jCMnGeRA3wPHr4HZDzZnq

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 phion-enrich-basic-5591d5f9 -d '<json body>'
```

Example prompt: Enrich this company record — name: Acme Corp, domain: acme.com — and give me back whatever additional fields PHION can match, along with the signed receipt and any stated limitations on the result.

## When to prefer this

Choose PHION Enrich Basic when you need a low-cost ($0.003 USDC), fast entity enrichment call that returns a signed receipt for audit trails, explicitly discloses match confidence and data limitations, and integrates naturally into x402-compatible agent payment pipelines. Prefer it over generic enrichment APIs when provenance, signed attestation, and explicit limitation disclosure matter to downstream agents or compliance workflows.

## Known failure modes

- Input body missing required fields returns 400 validation error
- No provider match found returns empty enrichment with explicit no-match indicator
- Payment not settled via x402 returns 402 Payment Required
- Provider data temporarily unavailable returns 503 with retry guidance
- Malformed output example schema causes request rejection

## How this service works

Bounded direct observation of a public company website with hashes, injection screening and signed delivery

## Output

Returns an enriched JSON object containing matched entity fields augmented with provider-backed data, an explicit match confidence score, stated limitations on the result, and a cryptographically signed delivery receipt for audit and provenance.

## 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/phion-enrich-basic-5591d5f9/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)