VEverdun
settings

Update Deepalert Default Threshold

The DeepAlert fleet default confidence floor: OWNER-ONLY, the sole writer. One transaction writes the value, the revision and the durable deepalert_threshold_changes row; a stale expected_revision is a 409 carrying the current value and revision. This is an ACTIVATION capability: shipping it authorizes nothing, and it is used only per the recorded flip procedure. The audit-log line below is best-effort and written after the commit; the change table is the record.

put/settings/deepalert-default-confidence-threshold

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/settings/deepalert-default-confidence-threshold
  • Auth
    HTTP bearer

Request body

expected_revisioninteger required

The fleet revision the caller last read. A different current revision answers 409 with the current value and revision, even when the requested value equals the current one.

reasonstring nullable

Free text recorded with the change; optional.

Example request

{
  "reason": "Per the recorded flip procedure"
}

Response

Successful Response

valuenumber required

The fleet default DeepAlert confidence floor now in force.

revisioninteger required

The fleet revision now in force. Moves by exactly one per change; an equal-value PUT at the current revision is a no-op and returns the existing one.

changed_atstring date-time nullable

When the CURRENT revision was recorded (the DB clock inside the change's transaction). Descriptive only: rows and events are assigned to an epoch by revision, never by this time. Null only if no change row exists for the revision.

Example response

{
  "value": 25,
  "revision": 1
}

Changes

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