Run Task
Run the task once with the variables you supply, and wait for the result.
This executes for real: the tools call your endpoints with your secrets, the MCP servers spend your credits, and the model spends your tokens. A task that books a slot, charges a card or sends a message will do so.
vars must match what the task declares — an unknown name is refused rather
than dropped. The response is the whole run: the structured output, a
trace of every tool call, the steps used and what the tokens cost. On
failure error.type says whose problem it is. Secrets are redacted.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Values for the variables this task declares, by name. A required variable with no value and no default is refused before the run starts; a name the task does not declare is refused too, rather than silently dropped.
Response
Successful Response
running, completed, failed