# Automated Dispute Bundle

> Automated Dispute Bundle is a paid API for AI agents from phion.systems, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Assembles verified failure evidence and recommends dispute review for a transaction or agent interaction without executing any refund or financial action

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/automated-dispute-bundle?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/automated-dispute-bundle-4976c8d5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Aph7HDQpXmVqydqDc5YlN

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 automated-dispute-bundle-4976c8d5 -d '<json body>'
```

Example prompt: Can you build me a verified dispute bundle for transaction TXN-8821 — it failed during the agent commerce journey and I need assembled evidence with a review recommendation, but don't actually execute any refund yet?

## When to prefer this

Choose this endpoint when you need to prepare a formal, verifiable dispute package for a failed agent transaction or commerce journey but must not trigger any financial action automatically. It is ideal when human review is required before any refund or chargeback, when auditability and signed evidence are mandatory, or when operating under agent policy constraints that prohibit autonomous financial remediation. Prefer it over manual evidence collection when you need tamper-evident, signed documentation ready for escalation.

## Known failure modes

- Missing or unresolvable transaction/journey identifier returns an error with no bundle produced
- Insufficient evidence data prevents bundle assembly, returning a partial or null result
- Evidence verification fails if upstream signed receipts are unavailable or tampered
- Service timeout if evidence collection from multiple sources exceeds processing window

## How this service works

Assemble verified failure evidence and recommend review without executing refunds

## Output

A structured dispute bundle containing verified, signed evidence of the failure event, a provenance-linked record of the relevant commerce journey, and a human-readable recommendation for dispute review — without executing any refund, chargeback, or financial action.

## 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/automated-dispute-bundle-4976c8d5/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)