Agents

Set Agent Operator Trust Dial

Set how far ONE skill may go on its own. THIS GOVERNS UNATTENDED ACTION.

The trust dial is the control that decides whether a finding stays a finding, becomes an approval a person decides, or is simply DONE. Raising it is the single most consequential write on this surface, which is why it takes the run grant rather than plain write.

THE DIAL IS A CEILING REQUEST, NOT A SETTING. The effective autonomy is the minimum of this value, the skill's graph8-managed risk cap and the platform ceiling, so a skill capped at PROPOSE stays at PROPOSE no matter what is sent. Read the response rather than assuming the write took literally.

Read GET /agent/operators/{operator}/scorecard first. A dial raised on a skill that has been wrong is how unattended work becomes unattended damage.

put/agent/operators/{operator}/skills/{skill_key}

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/operators/{operator}/skills/{skill_key}
  • Auth: HTTP bearer

Path parameters

operatorstring required
skill_keystring required

Skill key from GET /agent/operators/{operator}/skills.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

autonomy'OFF' | 'DETECT' | 'PROPOSE' | 'AUTO' required

How far this skill may go on its own. OFF - do not run it. DETECT - look, and record what it finds. PROPOSE - look, and raise an approval task a person decides. AUTO - act and log, with no human in the loop. THIS IS A REQUEST, NOT A GUARANTEE: the effective level is the MINIMUM of this dial, the skill's own graph8-managed risk cap and the platform ceiling, so a skill capped at PROPOSE stays at PROPOSE however this is set. Read the response, and GET /agent/operators/{operator}/skills, for what the dial actually resolved to.

Response

Successful Response

dataOperatorPayload required

An open envelope for one operator answer.

Open because an operator's health snapshot, scorecard and catalog are per-operator documents whose shape follows what that operator monitors - the revenue operator reports different checks from the deliverability one, and both grow. On an OVERSIGHT surface a dropped field reads as "nothing to worry about" rather than "we did not tell you", which is the failure mode worth designing against.

Changes

No recorded changes to this operation across all 2 revisions of this API.