# Agent Retry Decision

> Agent Retry Decision is a paid API for AI agents from agent-product-normalizer.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-18).

Determines whether a failed API or tool call should be retried and recommends the next action to take

## Facts

- Endpoint: GET https://agent-product-normalizer.vercel.app/api/v1/retry-decision
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-retry-decision-c89a9921
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3U442mXcSB50wzu7iXnjh

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-retry-decision-c89a9921
```

Example prompt: I just got a 503 error on my GET request after 2 attempts — should I retry it or give up, and what should I do next?

## When to prefer this

Use this endpoint when your AI agent needs a lightweight, stateless decision about whether to retry a failed HTTP or tool call. Ideal for agent orchestration frameworks that need consistent retry logic without hardcoding rules. Prefer this over custom retry logic when you want a pre-built, paid-for-per-call decision service that accounts for error type, HTTP status, and attempt count together.

## Known failure modes

- Missing required 'status' query parameter returns an error
- Status code value exceeding maxLength of 4 characters rejected
- Attempt number exceeding maxLength of 3 characters rejected
- Invalid or unrecognized status codes may produce uncertain recommendations
- Network timeout reaching the decision endpoint itself

## How this service works

Decide whether an API/tool failure should be retried and suggest the next action

## Output

A structured decision indicating whether the failed request should be retried, along with a recommended next action (e.g. retry with backoff, abort, escalate to human) based on the HTTP status code, error message, and attempt number provided.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "status"
     ],
     "properties": {
      "error": {
       "type": "string",
       "maxLength": 4000
      },
      "status": {
       "type": "string",
       "maxLength": 4
      },
      "attempt": {
       "type": "string",
       "maxLength": 3
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-retry-decision-c89a9921/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-product-normalizer.vercel.app](https://www.zero.xyz/host/agent-product-normalizer.vercel.app/llms.txt)