Skip to main content
A run starts when you post a message. It ends closed or failed. In between it may pause for a question (awaiting_input) or a side-effect confirmation (awaiting_outcome).

Attributes

uuid
required
Unique identifier for the run.
uuid
Thread this turn belongs to.
enum
required
running, awaiting_input, awaiting_outcome, closed, or failed.
boolean
true when the run will not change again (closed or failed).
number
Credits charged for this run.
object
Host used for customer tools, when one was resolved.
object
Latest assistant message, when the run has one.

Trace

GET /v1/loom/runs/:id/trace returns the same run plus the ordered turns. This is what “every run on a trace” means.
timestamp
When the run started.
timestamp
When the run reached a terminal state.
array
Model turns in order.
array
Data-plane HTTP calls attributed to this run (identify, and so on), newest first.
integer
Total attributed requests, which may exceed the array length.

Outcomes

When state is awaiting_outcome, post { tool_call_id, state } where state is occurred or failed. Optional detail is stored on the outcome. A retry against an already-resolved tool call is a no-op.

Endpoints