# Delx Retry Safe Classify

> Delx Retry Safe Classify is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Classifies whether a failed HTTP-style call is safe to automatically retry, returning a deterministic machine-readable JSON verdict.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/retry-safe-classify
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-retry-safe-classify-2be5ba59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6go6Z1AqTfpe4TFbooqkc

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 delx-retry-safe-classify-2be5ba59 -d '<json body>'
```

Example prompt: Can you check if it's safe to auto-retry that failed POST request — it came back with a 503 status, the body does mutate state, and there's no idempotency key attached?

## When to prefer this

Use this endpoint when an AI agent or orchestration layer needs a deterministic, rule-based advisory on retry safety before re-issuing a failed HTTP call — especially in automated pipelines where incorrect retries could cause duplicate mutations, financial side effects, or data corruption. Prefer this over hand-coded retry logic when you want a consistent, auditable classification step at near-zero cost ($0.001 USDC) that is stateless and has no upstream dependencies.

## Known failure modes

- Missing required fields (method or status_code) may return a validation error
- Invalid method string or non-integer status code causes malformed input rejection
- Ambiguous combinations (e.g. POST with no body_mutates flag) may return conservative non-retry verdict
- Payment failure over x402 results in 402 response before classification occurs

## How this service works

Classify whether a failed HTTP-style call is safe to auto-retry — first-party local utility for agent preflight and proven micro-utils expansion. Returns deterministic machine-readable JSON for $0.001 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, no web search, no live RPC, and no mediagen. Results are advisory; the caller owns authorization, budgets, and production controls. Sibling of Delx routes that already…

## Output

A deterministic JSON object indicating whether the given HTTP call is safe to auto-retry, based on the method, status code, body mutation behavior, and idempotency key presence. No state is stored; results are advisory and stateless.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "description": "Input field: method."
  },
  "status_code": {
   "type": "integer",
   "description": "Input field: status code."
  },
  "body_mutates": {
   "type": "boolean",
   "description": "Input field: body mutates."
  },
  "idempotency_key_present": {
   "type": "boolean",
   "description": "Input field: idempotency key present."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "advice": "retry_with_backoff",
  "method": "POST",
  "reason": "transient_status_with_idempotency_key",
  "schema": "delx/util-retry-safe-classify/v1",
  "retry_safe": true,
  "status_code": 503
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-retry-safe-classify-2be5ba59/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)