# ERC-8004 Identity Evidence Binding

> ERC-8004 Identity Evidence Binding is a paid API for AI agents from phion.systems, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-17).

Binds an ERC-8004 registry identity to independently marked evidence without asserting ownership claims

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/erc8004-identity-evidence?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/erc-8004-identity-evidence-binding-3e0ac097
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MJ8I70Yv8_U345U49ZiqF

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 erc-8004-identity-evidence-binding-3e0ac097 -d '<json body>'
```

Example prompt: Bind ERC-8004 registry identity 0xABCD1234 to our independently marked evidence bundle — don't assert ownership, just create the association record.

## When to prefer this

Use this endpoint when you need to formally associate an ERC-8004 registry identity with externally or independently marked evidence without making an ownership claim. It is distinct from identity ownership registration or verification — choose it when the goal is evidence linkage and attestation rather than identity claiming or resolution. Prefer it over generic blockchain attestation services when you specifically work within the ERC-8004 standard.

## Known failure modes

- Invalid or unresolvable ERC-8004 identity returns a resolution error
- Malformed or missing evidence markers cause a validation rejection
- Duplicate binding attempts for the same identity-evidence pair may return a conflict or idempotency error
- Insufficient evidence marking or independent attestation signals cause binding refusal
- Payment failure (x402 protocol) prevents endpoint invocation

## How this service works

Bind an ERC-8004 registry identity to supplied, independently marked evidence without claiming ownership

## Output

Returns a binding confirmation record associating the ERC-8004 registry identity with the supplied evidence, including attestation metadata, provenance markers, and the binding status — all without asserting ownership of the identity.

## 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/erc-8004-identity-evidence-binding-3e0ac097/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)