# Delx Commerce — Retry-After Header Parser

> Delx Commerce — Retry-After Header Parser 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).

Parses an HTTP Retry-After header value and computes the delay in seconds and the absolute retry timestamp epoch.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/retry-after-parse?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-after-header-parser-43105975
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Olz-7YQ7SokPilvNGbV_L

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-after-header-parser-43105975 -d '<json body>'
```

Example prompt: I just got a 429 response with the Retry-After header set to '120'. Given that the current epoch time is 1720000000, how many seconds do I need to wait and at what epoch can I retry?

## When to prefer this

Choose this endpoint when your agent needs to deterministically parse HTTP Retry-After headers — whether numeric seconds or HTTP date strings — into a concrete wait duration and retry epoch, especially when auditability (input hash, no retention guarantee) and micro-cost pay-per-call pricing matter. Prefer this over hand-rolling parsing logic when you need verifiable, consistent output for retry scheduling in agentic workflows.

## Known failure modes

- Malformed or unparseable Retry-After value returns an error status
- Missing required 'value' field causes a validation error
- now_epoch not provided may cause incorrect absolute timestamp calculation
- Value exceeding 8192 characters is rejected
- Invalid date string format in Retry-After header may cause parse failure

## 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: delay_seconds (how long to wait in seconds), retry_at_epoch (absolute Unix epoch when to retry), status ('pass' or failure), operation label, and an evidence block confirming no data retention, number of external calls made, and a SHA-256 hash of the input for auditability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "string",
   "maxLength": 8192,
   "description": "Value supplied to Retry After Parse; used only for this bounded calculation and processed in memory without retention."
  },
  "now_epoch": {
   "type": "integer",
   "description": "Now Epoch supplied to Retry After Parse; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "delay_seconds": 120,
   "retry_at_epoch": 1720000120
  },
  "schema": "delx/util-retry-after-parse/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "d9694253aa50ca3a4c76da4bbf323706780e4a4cfeb723b7ee5a097e2965b646",
   "external_calls": 0
  },
  "operation": "web_reliability:retry_after_parse"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-retry-after-header-parser-43105975/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)