# Agent Post-Settlement Failure Recovery Decision Procedure

> Agent Post-Settlement Failure Recovery Decision Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Classifies paid x402/MPP call failures after settlement and returns a structured decision on whether to retry, request a refund, or switch providers, along with retry budget, backoff settings, and dispute evidence preservation guidance.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/agent-post-settlement-failure-recovery-decision
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-post-settlement-failure-recovery-decision-procedure-cc3dd1fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-4vL53E-ABlTKrfRPKaqs

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-post-settlement-failure-recovery-decision-procedure-cc3dd1fd
```

Example prompt: I just made a paid x402 API call that settled successfully but the provider returned malformed data — can you classify this failure and tell me whether I should retry, request a refund, or switch providers, and what retry budget and backoff to use?

## When to prefer this

Use this endpoint when an AI agent has already settled payment for an x402 or MPP call and received a failure response, and needs a structured, actionable recovery decision rather than manual triage. Prefer this over generic retry logic when you need failure classification, backoff guidance, merchant reputation feedback, and dispute evidence handling in a single procedural call.

## Known failure modes

- No payment sent or payment rejected — returns unpaid/402 response rather than decision content
- Invalid or missing topic parameter may result in a generic procedure rather than a tailored one
- LLM generation failure may return ok:false with empty brief
- Rate limiting or service unavailability on the provider side returns an error response
- Malformed query parameters cause schema validation failure

## How this service works

Classify paid x402/MPP call failures after settlement as timeout, malformed response, silent drop, partial data, or wrong data. Decide between retry, refund request, or provider switch. Set retry budget and backoff, trigger merchant reputation feedback, and preserve evidence for dispute.

## Output

A prose decision brief classifying the post-settlement failure type (timeout, malformed response, silent drop, partial data, or wrong data), a recommended recovery action (retry, refund request, or provider switch), retry budget and backoff parameters, a merchant reputation feedback trigger recommendation, and guidance on preserving dispute evidence. Includes metadata such as generation source (llm, reasoning, or deterministic) and ISO-8601 timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "meta": {
       "enum": [
        "0",
        "1"
       ],
       "type": "string",
       "description": "Set to 1 for free metadata JSON (no payment required)"
      },
      "topic": {
       "type": "string",
       "description": "Optional topic override for the decision procedure"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "Agent post-settlement failure recovery procedure paid response",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "ok",
      "paid",
      "service",
      "provider",
      "result"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "paid": {
       "type": "boolean"
      },
      "result": {
       "type": "object",
       "required": [
        "ok",
        "service"
       ],
       "properties": {
        "ok": {
         "type": "boolean",
         "description": "Handler success"
        },
        "brief": {
         "type": "string",
         "description": "Decision procedure prose for agents"
        },
        "model": {
         "type": "string"
        },
        "topic": {
         "type": "string"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "procedure": {
         "type": "string"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        },
        "generationSource": {
         "enum": [
          "llm",
          "reasoning",
          "deterministic"
         ],
         "type": "string"
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         "type": "string"
     
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-post-settlement-failure-recovery-decision-procedure-cc3dd1fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)