# Agent Approval Relay

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

Binds a time-limited human approval decision to a specific purpose and exact payload, creating a cryptographically anchored authorization record for agent actions

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/agent-approval-relay?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-approval-relay-494f5aa3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q8FGx1mCBc1Fi-nDpCi0b

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-approval-relay-494f5aa3 -d '<json body>'
```

Example prompt: Before executing this fund transfer, lock in my approval decision to this exact payment payload and purpose so the authorization can't be reused or redirected — give me a time-limited, purpose-bound approval receipt.

## When to prefer this

Choose this endpoint when an agent needs to demonstrate that a specific human approved a specific payload for a specific purpose within a bounded time window — not just that approval was granted generically. It is preferable over generic auth tokens or session-based approvals when auditability, payload-locking, and time-bounding are all required simultaneously, especially in high-stakes agentic workflows involving payments, irreversible actions, or regulated decisions.

## Known failure modes

- Approval window has expired — time-limited binding cannot be created after deadline
- Payload mismatch — submitted payload does not match the content originally presented for approval
- Purpose mismatch — stated purpose conflicts with the bound authorization context
- Invalid or missing approval decision — relay cannot proceed without a valid human decision signal
- Replay attack detected — approval receipt already consumed or reused
- Malformed input schema — required fields absent or incorrectly typed

## How this service works

Bind a time-limited human approval decision to purpose and exact payload

## Output

A signed, time-limited receipt that cryptographically binds a human approval decision to a specific purpose and exact payload hash, preventing reuse, repurposing, or forgery of the authorization across different agent actions or time windows.

## 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-approval-relay-494f5aa3/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)