Skip to content
1 minute readImprovedAgent-ready

Cost and margin inputs are checked, never dropped

Cost and margin inputs that cannot be read are refused by name, the explanation starts with the price you get, and a batch keeps pricing past an item that fails validation.

  • Nothing dropped quietly: a unit cost that is a string or negative, a margin outside 0 to under 100, or either one sent outside context.metadata is a 400 validation_failed naming the field.
  • The explanation leads with your price: when a limit moved the price, the first sentence gives the price returned and what moved it, for example "The price returned is 64.99 USD, raised from the function's 57.15 USD by the workspace minimum margin."
  • Batches keep going: in POST /api/compute/batch, an item that fails validation comes back as an error at its position, with its index and fields, and the other items are priced. It is not charged.