# Delx Timeout Budget

> Delx Timeout Budget is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-16).

Splits a total timeout budget into per-step millisecond allocations after reserving overhead, returning deterministic JSON slices for multi-step agent workflows

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/timeout-budget
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-timeout-budget-8ce313f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o0eF19uzYw2X2DI3ev8ra

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-timeout-budget-8ce313f9 -d '<json body>'
```

Example prompt: I have a 10000ms total timeout for my pipeline with 500ms reserved for overhead — split the remaining budget evenly across 4 sequential steps and tell me how many milliseconds each step gets.

## When to prefer this

Choose this endpoint when you need a deterministic, stateless, local computation to split a parent timeout into per-step slices in a multi-step agent or workflow pipeline — especially when composing sequential jobs where you want reproducible, machine-readable JSON output without any external dependencies or data retention.

## Known failure modes

- steps value of zero causes division-by-zero error
- reserved_ms exceeding total_ms results in negative remaining budget
- missing required fields (steps, total_ms, reserved_ms) returns validation error
- non-numeric inputs rejected with type error
- payment failure via x402 prevents execution

## How this service works

Split a total timeout into per-step budgets after reserved overhead — call when carving a parent timeout into per-step slices after overhead. Use before side effects when composing multi-step agent jobs—the same loyalty/workflow demand band agents already pay for on Bazaar, but fully local. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, and no claim of live…

## Output

Returns deterministic machine-readable JSON containing the per-step millisecond budget calculated as (total_ms minus reserved_ms) divided by steps, along with the remaining budget after overhead and individual step allocations.

## 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-timeout-budget-8ce313f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)