Skip to main content
POST
Mid-run anchor check

Authorizations

Authorization
string
header
required

Your workspace API key, e.g. sk_sovereign_..., sent as Authorization: Bearer <key>.

Path Parameters

id
string
required

Body

application/json
step
string
required
Pattern: ^[A-Za-z0-9_.-]{1,40}$
items
object[]
required
Required array length: 1 - 64 elements

Response

The verdict for this check.

session_id
string
held
boolean
state
enum<string>

clear — no hold. grader_fooled — the gap (reward read − anchor read on the same outputs) widened beyond its paired noise since the first check while the anchor stayed within its own: the reward passes what the anchor fails, before true quality moves. gamed — the gap widened AND the anchor fell beyond its noise from its best. degrading — the anchor fell and the gap did not widen: both instruments see the fall. Every non-clear state holds.

Available options:
clear,
grader_fooled,
gamed,
degrading
reason
string | null
pinned_step
string | null
point
object
underpowered
string | null
history
object[]
items
object[]

Every item of this check with both verdicts and its kind — the seam list. Not stored server-side.

counts
object
spend_micros
string