# Multi-Agent Escrow Recommendation

> Multi-Agent Escrow Recommendation is a paid API for AI agents from phion.systems, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-21).

Recommends evidence-bound hold or release states for escrow scenarios without taking custody of or moving funds

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/multi-agent-escrow?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/multi-agent-escrow-recommendation-e0d109ee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kFhuMRMWSHrvSyWwfel_C

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 multi-agent-escrow-recommendation-e0d109ee -d '<json body>'
```

Example prompt: Based on the evidence I have for task completion in this agent-to-agent transaction, can you recommend whether the escrow should stay on hold or be released — without actually moving any funds?

## When to prefer this

Choose this endpoint when an AI agent needs an impartial, evidence-bound recommendation on whether escrow funds should be held or released, but where the agent itself must not have custody over funds or execute any payment movement. Ideal for multi-agent workflows where a neutral third-party recommendation is needed to satisfy trust requirements between agents, especially in x402-based payment flows where escrow state changes are gated on external validation.

## Known failure modes

- Insufficient evidence provided to make a recommendation
- Malformed or missing escrow context in input payload
- Conflicting evidence that prevents a clear hold/release determination
- Input schema validation failure due to incomplete JSON payload
- Service timeout if evidence retrieval or evaluation takes too long
- Ambiguous release conditions that cannot be deterministically resolved

## How this service works

Recommend evidence-bound hold or release states without custody or fund movement

## Output

A recommendation object indicating whether the escrow should be in a hold or release state, bound to the specific evidence provided, without any custody of or movement of funds. Typically includes the recommended state, evidence references, and a signed or attestable receipt of the recommendation.

## 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/multi-agent-escrow-recommendation-e0d109ee/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)