# Delx Commerce — Timeout Budget Calculator

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

Computes per-step timeout allocation by splitting a total timeout budget across sequential steps after reserving overhead milliseconds.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/timeout-budget?utm_source=zero.xyz
- Price: $0.003/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-timeout-budget-calculator-d51aaa82
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CMRRfZJurUTTiasETJ1Ob

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-timeout-budget-calculator-d51aaa82 -d '<json body>'
```

Example prompt: I have a total timeout budget of 5000ms, I want to reserve 500ms for overhead, and I need to split the remaining time across 3 sequential steps — how many milliseconds does each step get, and is it feasible?

## When to prefer this

Use this endpoint when an AI agent or orchestration system needs to programmatically compute fair per-step timeout allocations from a global deadline — especially when a fixed overhead must be reserved before distributing remaining time. Prefer it over manual arithmetic when building dynamic multi-step pipelines where step count or budget varies at runtime.

## Known failure modes

- Invalid or missing required fields (steps, total_ms, reserved_ms) may return a 400 error
- reserved_ms >= total_ms results in feasible:false with zero or negative available_ms
- Non-numeric inputs may cause validation errors
- steps value of 0 would cause a division-by-zero scenario

## 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 number of steps, total_ms, reserved_ms, available_ms (total minus reserved), per_step_ms (available divided by steps), a feasibility boolean, and the schema identifier 'delx/util-timeout-budget/v1'.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "steps": {
   "type": "number",
   "description": "Count of sequential steps that share the remaining timeout after reserved overhead."
  },
  "total_ms": {
   "type": "number",
   "description": "Total timeout budget in milliseconds."
  },
  "reserved_ms": {
   "type": "number",
   "description": "Milliseconds reserved for overhead before per-step split."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "steps": 3,
  "schema": "delx/util-timeout-budget/v1",
  "feasible": true,
  "total_ms": 5000,
  "per_step_ms": 1500,
  "reserved_ms": 500,
  "available_ms": 4500
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-timeout-budget-calculator-d51aaa82/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)