# Agent Memory Provenance

> Agent Memory Provenance is a paid API for AI agents from phion.systems, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-20).

Binds a memory record to its source identity, observation timestamp, and content hash to establish verifiable provenance

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/agent-memory-provenance?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-memory-provenance-21989a0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cwrpOFW00BLejTfWZBlwx

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 agent-memory-provenance-21989a0f -d '<json body>'
```

Example prompt: Bind this memory record to my agent's source identity, lock in the observation time as right now, and generate a content hash so I can prove its provenance later — the content is 'user confirmed billing address on 2024-06-10'.

## When to prefer this

Choose this endpoint when an AI agent needs to establish verifiable, tamper-evident provenance for a stored memory — particularly in multi-agent environments where memories are shared and their origin or integrity may be disputed. It is preferred over generic logging when cryptographic content hashing and signed source-identity binding are required for auditing or compliance.

## Known failure modes

- Missing or malformed source identity causes binding failure
- Invalid or unparseable observation timestamp returns a validation error
- Content hash mismatch if pre-computed hash conflicts with server-side computation
- Insufficient payment or expired x402 payment token results in 402 rejection
- Empty or null memory content body yields schema validation error

## How this service works

Bind a memory record to source identity, observation time and content hash

## Output

Returns a signed provenance record that links the memory content to its source identity, observation timestamp, and a cryptographic content hash — enabling downstream agents or auditors to verify the memory's origin and integrity.

## 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/agent-memory-provenance-21989a0f/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)