One active operation
The workspace shares admission across models, tools and compute. A running or unresolved operation can prevent another creation request and return 409. Additional keys in that workspace do not bypass this constraint. For batch processing, manage a bounded queue in your application. Start the next operation after the current operation’s terminal state is established. Do not hammer a conflicting endpoint with parallel retries.Spending caps are optional
A blank category cap means wallet-based admission. A supplied cap blocks new category work once reached. Neither the cap nor a local workflow budget is a guaranteed per-request maximum: a successful upstream result can settle above the remaining allowance. Compute has continuous runtime and termination behavior. Stop it explicitly, inspect the job until terminal, and do not equate disconnecting with termination.Pagination and dates
Tool cataloglimit accepts 1–100; compute history requires limit of 1–100.
Observability page numbers accept 1–9999. Trace dates are real YYYY-MM-DD UTC
dates with a range of at most 93 calendar days inclusive.
Use returned opaque cursors unchanged. The tool/model run listing APIs currently
return bounded recent lists; they do not expose the same cursor contract as
compute history. See API conventions.