Controls

Record enforcement outcome

Records what your code actually did with a verdict (honored / ignored / remediated) — the write side of the adherence loop. Auth: sk_live_ API key (Authorization: Bearer or X-API-Key). Requires the controls:report scope (controls:* and * also pass). Either honored or developer_response is required. Retries with the same decision_id are deduped and return recorded: false, deduped: true.

post/api/v1/controls/outcome

Request

  • Base URL: http://dobby-ai.com
  • URL: http://dobby-ai.com/api/v1/controls/outcome
  • Auth: HTTP bearer

Request body

decision_idstring nullable

The verdict's decision_id from /controls/check — enables retry dedup

honoredboolean

true = your code stopped the denied action; false = it proceeded anyway

developer_response'honored' | 'ignored' | 'remediated'

Explicit outcome (takes precedence over honored)

action_takenstring nullable
detailstring nullable
actionstring nullable

The tool/action the verdict was for (denormalized for rollups)

verdictstring nullable
actor_idstring nullable
workflow_idstring nullable
correlation_idstring nullable

Shared id linking this outcome to the LLM-call telemetry for the same action

Example request

{
  "action_taken": "stopped"
}

Response

Outcome recorded (recorded: false + deduped: true on a retried decision_id)

successboolean

Example response

{
  "success": true,
  "data": {
    "outcome_id": "peo_abc123def456",
    "recorded": true
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.