{"uid":"cap_m5EPL0hRDfSF7GsQn5EJV","slug":"delx-concurrency-cap-27c9af12","name":"Delx Concurrency Cap","description":"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…","url":"https://api.delx.ai/api/v1/x402/concurrency-cap","method":"POST","headers":{},"bodySchema":{"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."}}},"responseSchema":{"type":"json","example":{"schema":"delx/util-concurrency-cap/v1","hard_cap":8,"saturated":true,"queue_depth":12,"desired_workers":32,"effective_workers":8}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.003","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.003/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm__KPxvr62M1ZekIUnmeT0I","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.003","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Clamps a desired worker concurrency value against a hard maximum limit and queue depth saturation signal, returning the safe allowed parallelism as deterministic JSON.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Throttle agent job before side effects","prompt":"Before I fan out my order-processing pipeline, clamp my desired 50 concurrent workers against a hard cap of 30 and a current queue depth of 120 — what's the safe parallelism to use?"},{"title":"Preventing crawler over-provisioning","prompt":"I'm about to launch a web scraping job. I want 25 workers but my system hard limit is 15 and the queue depth is 80 — tell me the concurrency I should actually run at."},{"title":"Dynamic scaling check in orchestration loop","prompt":"My orchestrator loop wants to scale up to 10 workers, the hard cap is 8, and queue depth is 3 right now — run a concurrency cap check so I know how many to actually start."}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T07:14:46.672Z","isFirstParty":false}