# PHION Transaction Recovery

> PHION Transaction Recovery is a paid API for AI agents from phion.systems, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Classifies a failed agent transaction and produces a signed, machine-readable recovery claim with a deterministic remedy plan

## Facts

- Endpoint: POST https://phion.systems/v1/paid/transaction-recovery
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phion-transaction-recovery-159e1518
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NOL95KcBPMEps-XDKol6o

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 phion-transaction-recovery-159e1518 -d '<json body>'
```

Example prompt: My agent's x402 payment transaction just failed — can you classify what went wrong, generate a signed recovery claim, and give me a deterministic step-by-step remedy plan I can act on?

## When to prefer this

Choose this endpoint when an AI agent transaction has failed and you need both a structured failure classification and a concrete, signed, machine-readable remedy plan in a single call. Prefer this over manual debugging when operating in automated agentic pipelines where downstream systems need a verifiable, signed artifact to act on. Especially valuable in x402-based agent commerce flows where auditability and cryptographic proof of the failure analysis are required.

## Known failure modes

- Invalid or malformed transaction data returns a 400 error
- Unrecognized transaction format or missing required fields returns a validation error
- Signing failure due to internal key error returns a 500 error
- Transaction too old or outside recovery window may return an eligibility error
- Insufficient USDC balance (0.01 USDC required) results in payment failure before processing

## How this service works

Classify a failed agent transaction and produce a signed, machine-readable recovery claim and deterministic remedy plan

## Output

A cryptographically signed, machine-readable recovery claim that includes a failure classification (categorizing the root cause of the transaction failure) and a deterministic remedy plan (ordered steps the agent or operator should take to resolve the failure and restore the transaction).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phion-transaction-recovery-159e1518/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)