# Delx Commerce — Backoff Schedule Generator

> Delx Commerce — Backoff Schedule Generator 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).

Computes an exponential-cap backoff schedule (delay list with jitter guidance) given base delay, cap, and attempt count

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/backoff-schedule?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-commerce-backoff-schedule-generator-8365ac0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NzvoSmjksMoQ2Nl4qbtl5

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-backoff-schedule-generator-8365ac0f -d '<json body>'
```

Example prompt: Generate a capped exponential backoff schedule for 4 retry attempts, starting at 250ms base delay and capping at 30 seconds, so I know how long to wait between each retry.

## When to prefer this

Choose this endpoint when you need a deterministic, server-computed exponential backoff schedule with a configurable cap and jitter guidance — especially in agent orchestration pipelines where consistent retry timing across distributed components matters. Prefer it over hand-coding retry math when you want a verified, reproducible delay sequence returned as structured data you can consume directly.

## Known failure modes

- Invalid parameter values outside allowed ranges (e.g. attempts > 20, cap_ms > 3600000) return a 4xx error
- base_ms exceeding cap_ms may produce a flat or degenerate schedule
- Missing required fields default to preset values (base 250ms, cap 30000ms, attempts 4)
- Payment failure via x402 prevents result delivery

## 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 containing the backoff strategy name (e.g. 'exponential_cap'), an ordered array of delay values in milliseconds, a jitter range recommendation for each delay slot (full jitter), and the total cumulative delay in milliseconds across all attempts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "cap_ms": {
   "type": "integer",
   "default": 30000,
   "maximum": 3600000,
   "minimum": 1
  },
  "base_ms": {
   "type": "integer",
   "default": 250,
   "maximum": 60000,
   "minimum": 1
  },
  "attempts": {
   "type": "integer",
   "default": 4,
   "maximum": 20,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/backoff-schedule/v1",
  "strategy": "exponential_cap",
  "delays_ms": [
   250,
   500,
   1000,
   2000
  ],
  "jitter_range": "0..delay_ms (full jitter recommended at execution time)",
  "total_delay_ms": 3750
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-backoff-schedule-generator-8365ac0f/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)