# Delx Commerce — Queue Wait Estimate

> Delx Commerce — Queue Wait Estimate 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-02).

Estimates the wait time for a job entering a queue given the number of workers, mean service time, and current queue depth.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/queue-wait-estimate?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-queue-wait-estimate-7a49ff7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hhywZSmSU1i5HQNevZpI5

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-queue-wait-estimate-7a49ff7c -d '<json body>'
```

Example prompt: I have a queue with 10 items ahead of my job, 2 parallel workers draining it, and each item takes about 200 ms to process — how long should I expect to wait before my job starts?

## When to prefer this

Use this endpoint when you need a fast, cheap, on-demand queuing theory calculation without standing up your own math library — particularly in agentic workflows where you want to decide whether to submit a job, scale workers, or alert on latency before committing resources. It's ideal when you already know your worker count, mean service time, and current queue depth and just need the expected wait in milliseconds.

## Known failure modes

- Missing required parameters (workers, service_ms, or queue_depth) result in a 4xx error
- Non-positive values for workers or service_ms may produce undefined or infinite estimates
- Payment failure via x402 protocol results in a 402 response before computation occurs
- Extremely large queue_depth or service_ms values may cause overflow or implausible estimates

## 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 following the 'delx/util-queue-wait-estimate/v1' schema, echoing back the input parameters (workers, service_ms, queue_depth) alongside a computed estimated_wait_ms value representing how long a newly enqueued item should expect to wait before processing begins.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "workers": {
   "type": "number",
   "description": "Number of parallel workers draining the queue."
  },
  "service_ms": {
   "type": "number",
   "description": "Mean service time per item in milliseconds."
  },
  "queue_depth": {
   "type": "number",
   "description": "Items waiting ahead of the new job."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-queue-wait-estimate/v1",
  "workers": 2,
  "service_ms": 200,
  "queue_depth": 10,
  "estimated_wait_ms": 1000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-queue-wait-estimate-7a49ff7c/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)