Skip to main content
POST
Acknowledge A Prompt Review Finding
Changes state - verify before retry Accept or dismiss one agent prompt review finding. The decision applies to the agent across versions, sessions, and workspace teammates, so future reviews do not keep presenting a finding your team already evaluated.

When To Use A Prompt Review Acknowledgement

  • Use accepted when the finding is valid and the team has intentionally decided to live with it.
  • Use dismissed when the finding does not apply to this agent.
  • Do not acknowledge a finding merely to clear the review. Revise the draft when the warning reveals a real issue that should be fixed.

Before You Call It

Run Review An Agent Prompt and keep the finding’s fingerprint and kind. Send the agent ID that produced that review; it must be an agent in your workspace.

Side Effects And Retry Safety

This operation writes a shared acknowledgement for the agent. It does not edit the prompt, create a version, or publish the agent. The operation is idempotent for the same finding fingerprint. A first acknowledgement returns updated: false. Repeating it, or changing the decision for that fingerprint, updates the existing record and returns updated: true.

Verify The Result

Confirm the response contains the requested finding_fingerprint, kind, and status. The response also includes acked_at and, when available, acked_by. Run prompt review again and confirm the finding is marked acknowledged or no longer appears as a new warning.

Operation-Specific Errors

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

agentId
string
required

Signed agent ID of an agent in your workspace.

Body

application/json
finding_fingerprint
string
required

The finding's own fingerprint (sha1 hex), from the review response.

Pattern: ^[0-9a-f]{40}$
kind
string
required

The finding kind at ack time (contradiction, hallucination_risk, ...).

Maximum string length: 40
status
enum<string>
required
Available options:
accepted,
dismissed

Response

Finding acknowledgement stored.

success
enum<boolean>
required
Available options:
true
error
enum<boolean>
required
Available options:
false
statusCode
integer
required
Example:

201

message
string
required
Example:

"Success"

data
object
required
timestamp
string<date-time>
required