Skip to main content
POST
Admit a headless Computer operation

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

checkfu-version
enum<string>
required
Available options:
2026-08-31
idempotency-key
string
Maximum string length: 255
x-checkfu-computer-ingress-token
string
Pattern: ^[0-9a-f]{64}$

Path Parameters

id
string
required
Pattern: ^comp_[0-9a-f]{32}$

Body

application/json

Caller-selected headless operation ingress: the exact Computer attachment, its Session, the mutation-epoch fence, a short deadline, the operation itself, and whether authority is proven by the owning Run (whose id the ingress carries) or a terminal ingress grant (whose token rides the request headers). The server derives identity, generation, clocks, and provenance.

attachment_id
string
required
Pattern: ^catt_[0-9a-f]{32}$
session_id
string
required
Pattern: ^sess_[0-9a-f]{32}$
expected_mutation_epoch
integer
required
Required range: x >= 0
deadline
string
required

A canonical UTC ISO-8601 timestamp with millisecond precision.

Maximum string length: 24
Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$
operation
object
required

One mutating headless Computer operation: a filesystem write or remove with its content-addressed digest, or a process start, inspect, or signal. Paths stay inside the attached workspace's mutable tree and every bound is enforced at admission.

ingress
object
required

The provenance one headless operation ingress carries: either the Session Run whose live attempt-and-lease authority is revalidated by the owning Session, or a terminal Computer ingress grant whose token rides the request headers.

Response

Admission receipt for one headless Computer operation: the server-derived operation identity, whether the Computer's serialized mutation slot dispatched or queued it, and whether the request replayed an existing admission.

Admission receipt for one headless Computer operation: the server-derived operation identity, whether the Computer's serialized mutation slot dispatched or queued it, and whether the request replayed an existing admission.

operation_id
string
required
Pattern: ^cop_[0-9a-f]{32}$
disposition
enum<string>
required
Available options:
dispatched,
queued,
settled
replayed
boolean
required