# Agent Incident Recovery Action Plan

> Agent Incident Recovery Action Plan is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Generates a structured, controller-readable recovery plan with stabilize, diagnose, recover, and prevent phases for agents that are looping, drifting, or failing.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/premium/recovery-action-plan
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-delx-ai-a4690bd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ijBNCTSMp0YRPx5_laJ9_

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 api-delx-ai-a4690bd7 -d '<json body>'
```

Example prompt: My agent named OrderFulfillmentBot has been looping on the payment validation step for the last 10 minutes — can you generate a full recovery action plan with stabilize, diagnose, recover, and prevent phases so I can get it back on track?

## When to prefer this

Use this endpoint when an AI agent is actively looping, drifting, or failing and you need a structured, phased recovery plan that a controller or orchestrator can act on immediately. Prefer this over generic RCA endpoints when you need forward-looking prevention steps alongside diagnosis, or when you need a plan formatted for machine-readable handoff to another controller.

## Known failure modes

- Insufficient incident context provided — plan may be generic rather than specific to the failure mode
- Agent state or error details missing — stabilize phase may lack targeted actions
- Ambiguous failure description — diagnosis phase may produce broad rather than targeted hypotheses
- Downstream timeout if agent context payload is too large
- $0.01 USDC payment not processed — x402 payment required error returned

## How this service works

Controller-readable incident recovery plan with stabilize, diagnose, recover, and prevent phases for looping, drifting, or failing agents.

## Output

A structured, controller-readable recovery action plan organized into four phases: stabilize (immediate actions to halt further damage), diagnose (root cause identification steps), recover (steps to restore normal operation), and prevent (measures to avoid recurrence). The plan is formatted for consumption by an orchestration controller or human operator managing the failed agent.

## Example request

```json
{
 "session_id": "123e4567-e89b-12d3-a456-426614174000",
 "incident_summary": "OrderFulfillmentBot has been looping on the payment validation step for 10 minutes, with 12 failed validation attempts and a payment validation timeout error on order ORD-2024-001."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-delx-ai-a4690bd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)