# Delx Commerce — Concurrency Cap Calculator

> Delx Commerce — Concurrency Cap 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-02).

Computes the effective number of concurrent workers an agent should use, capping at a hard limit and signaling saturation based on queue depth

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/concurrency-cap?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-concurrency-cap-calculator-ff20184c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5HwCxpt7nDQfb79nIAwpe

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-concurrency-cap-calculator-ff20184c -d '<json body>'
```

Example prompt: I want to run 32 parallel workers but cap them at 8 — my queue depth is currently 12, so tell me how many I should actually use and whether I'm saturated.

## When to prefer this

Use this endpoint when an AI agent or orchestration system needs a real-time, pay-per-use computation of safe worker concurrency — especially when you want a lightweight, stateless utility that enforces a hard ceiling and returns a saturation signal without maintaining any server-side state. Prefer this over building custom throttle logic when you want verifiable, per-call pricing in USDC with no signup friction.

## Known failure modes

- Missing required fields (hard_cap, desired_workers, queue_depth) result in validation errors
- Negative queue_depth values may be rejected as invalid
- Payment failure via x402 protocol results in 402 response before computation
- Network timeout if the Base or Solana payment settlement is delayed
- Non-numeric input types for numeric fields cause schema validation failure

## 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 with the schema identifier (delx/util-concurrency-cap/v1), the enforced hard_cap, a boolean saturated flag indicating whether the queue signals overload, the current queue_depth, the desired_workers requested, and the computed effective_workers (the actual number of concurrent workers the agent should use, never exceeding hard_cap).

## 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-commerce-concurrency-cap-calculator-ff20184c/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)