# Delx Concurrency Cap

> Delx Concurrency Cap 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-15).

Clamps a desired worker concurrency value against a hard maximum limit and queue depth saturation signal, returning the safe allowed parallelism as deterministic JSON.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/concurrency-cap
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-concurrency-cap-27c9af12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m5EPL0hRDfSF7GsQn5EJV

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-concurrency-cap-27c9af12 -d '<json body>'
```

Example prompt: I want to spin up workers for a batch job — my hard cap is 20 workers, I currently have a queue depth of 45, and I'm requesting 30 concurrent workers. What's the safe concurrency I should actually use?

## When to prefer this

Use this endpoint when you need a lightweight, stateless, local computation to enforce a hard worker concurrency ceiling before executing side-effecting or resource-intensive steps in an agent pipeline. Prefer it over custom logic when you want deterministic, machine-readable output without any upstream API dependencies, state retention, or latency overhead. Ideal for multi-step agent workflows on Bazaar or similar orchestration systems where parallelism must be bounded cheaply.

## Known failure modes

- Missing required fields (hard_cap, desired_workers, or queue_depth) returns a 4xx validation error
- Negative queue_depth value may be rejected as invalid
- Non-numeric inputs cause schema validation failure
- Payment not included or insufficient USDC via x402 results in 402 Payment Required

## How this service works

Cap desired worker concurrency against a hard limit and queue depth signal — call when clamping desired parallelism against a hard worker limit. 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 li…

## Output

Returns deterministic machine-readable JSON containing the allowed (capped) concurrency value, reflecting the lesser of desired_workers and hard_cap adjusted for queue depth saturation. No state is stored and the result is computed locally and statelessly.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hard_cap": {
   "type": "number",
   "description": "Maximum allowed concurrent workers."
  },
  "queue_depth": {
   "type": "number",
   "description": "Current queue depth used as a saturation signal (non-negative)."
  },
  "desired_workers": {
   "type": "number",
   "description": "Requested concurrent workers."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-concurrency-cap/v1",
  "hard_cap": 8,
  "saturated": true,
  "queue_depth": 12,
  "desired_workers": 32,
  "effective_workers": 8
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-concurrency-cap-27c9af12/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)