# Delx Commerce — Retry-Safe Classify

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

Classifies whether an HTTP request is safe to retry based on method, status code, mutation behavior, and idempotency key presence

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/retry-safe-classify?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-retry-safe-classify-895ff3be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VNcr3fA751YU6lwxmpIk7

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-commerce-retry-safe-classify-895ff3be -d '<json body>'
```

Example prompt: I just got a 503 from a POST call that mutates data and has an idempotency key — is it safe to retry, and what should I do next?

## When to prefer this

Choose this endpoint when an AI agent needs a principled, rule-based decision about HTTP retry safety at runtime — especially when dealing with potentially mutating requests, uncertain idempotency guarantees, or transient error codes. It is particularly useful in agentic workflows where unintended duplicate side effects (e.g. duplicate payments or writes) must be avoided. Prefer it over hardcoded retry logic when the HTTP method, status code, and idempotency posture vary dynamically across different API calls in the workflow.

## Known failure modes

- Missing required fields (method or status_code) may result in a 400 or malformed classification
- Invalid status_code values outside standard HTTP range may produce unexpected classifications
- Payment failure via x402 protocol results in 402 response before any classification occurs
- Network timeout on the Delx endpoint itself may require a retry of the classify call

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object with retry_safe (boolean), advice (e.g. 'retry_with_backoff'), reason (e.g. 'transient_status_with_idempotency_key'), the echoed method and status_code, and a schema identifier string for traceability.

## 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-commerce-retry-safe-classify-895ff3be/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)