Agents

Put Agent Operating Model

Replace the organisation's operating-model override. PUT SEMANTICS.

The whole document is replaced: a key absent from override is REMOVED, not left alone, and an empty object resets the org to graph8's defaults. That is the app's behaviour and this does not soften it - a partial-update spelling here would make the same body mean two different things on two surfaces.

This is a policy document, not a switch, which is why it is tiered write while /enabled is not: it describes the org, and an operator has to be turned on separately before anything reads it unattended.

put/agent/operators/operating-model

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/operators/operating-model
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

overrideobject required

The organisation's operating-model override, REPLACED WHOLE. This is a PUT: keys absent from the body are removed, not left alone. Read GET /agent/operators/operating-model first and send it back modified.

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.