# Delx HTTP Retry Plan

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

Returns an optimal HTTP retry strategy (backoff algorithm, max attempts, jitter, idempotency) for a given HTTP method and response status code

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/http-retry-plan?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-http-retry-plan-34cf17d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hVYhh7bcN1VtgJeldfKBJ

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-http-retry-plan-34cf17d1 -d '<json body>'
```

Example prompt: My HTTP agent just got a 503 response on a GET request — what's the best retry strategy to use, including how many attempts, what backoff algorithm, and whether to respect the Retry-After header?

## When to prefer this

Choose this endpoint when an AI agent or automated HTTP client needs a deterministic, best-practice retry plan for a specific HTTP status code and method combination, especially when building resilient API integrations or agent workflows that must handle transient failures gracefully. It is preferable over hardcoded retry logic because it encodes idempotency awareness and HTTP semantics.

## Known failure modes

- Invalid status code outside 100-599 range returns a validation error
- Unsupported HTTP method may return an unexpected or generic strategy
- Missing required fields may result in a 400 Bad Request
- Payment failure via x402 protocol prevents response delivery

## How this service works

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

## Output

A JSON object containing the recommended retry strategy including: the HTTP method, schema version, any warnings, the backoff strategy name (e.g. exponential_full_jitter), whether the request is retryable, whether it is idempotent, the original status code, the maximum number of retry attempts, and whether to respect the Retry-After header.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "default": "GET"
  },
  "idempotent": {
   "type": "boolean",
   "description": "Override inferred method idempotency when the caller has a stable key."
  },
  "status_code": {
   "type": "integer",
   "maximum": 599,
   "minimum": 100
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "method": "GET",
  "schema": "delx/http-retry-plan/v1",
  "warning": null,
  "strategy": "exponential_full_jitter",
  "retryable": true,
  "idempotent": true,
  "status_code": 503,
  "max_attempts": 4,
  "respect_retry_after": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-http-retry-plan-34cf17d1/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)