{"uid":"cap_5HwCxpt7nDQfb79nIAwpe","slug":"delx-commerce-concurrency-cap-calculator-ff20184c","name":"Delx Commerce — Concurrency Cap Calculator","description":"Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.","url":"https://commerce.delx.ai/api/v1/x402/concurrency-cap?utm_source=zero.xyz","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_DnfwrOvzfaiHqYwFv1xZp","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":"Computes the effective number of concurrent workers an agent should use, capping at a hard limit and signaling saturation based on queue depth","exampleAgentPrompt":"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.","exampleUseCases":[{"title":"Throttling an overloaded agent fleet","prompt":"My agent fleet wants to spin up 50 workers but I've set a hard cap of 10 and my queue is already at 25 jobs deep — how many workers should actually be running right now, and am I saturated?"},{"title":"Safe parallelism for a document pipeline","prompt":"I'm processing documents in parallel and want to use 20 workers, but my hard limit is 6 and I have 8 items backed up in queue — what's the effective worker count I should launch?"},{"title":"Dynamic concurrency control for a web scraper","prompt":"My scraper wants to fire off 15 concurrent requests, my hard cap is 4, and the queue is currently empty — give me the effective concurrency ceiling and tell me if I'm hitting saturation."}],"resultDescription":"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).","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-02T04:53:55.162Z","isFirstParty":false,"canonicalSlug":"delx-commerce-concurrency-cap-calculator-ff20184c"}