Brand Alignment: answer outcome
POST /v1/brands/:brand_id/alignment/answers/:answer_id/outcome
Access is limited to the brands permitted by your credential. Requires write:alignment. Workspace API keys and signed-in MCP sessions are supported.
Writes require an active workspace entitlement and an Idempotency-Key header. Support memberships cannot write.
Sets your team’s own outcome for an answer when Asky’s assessment is wrong, per fact the answer was assessed against. The new outcome counts everywhere the answer does: outcome rates, facts, trends, sources and exports. Asky’s assessment and the answer’s statements are kept, and an outcome of null returns the verdict to Asky’s assessment. Choosing the outcome Asky already gave does the same.
Request body
Only the fields below are accepted. Brand and answer identifiers in the URL cannot be overridden in the body.
| Field | Required | Description |
|---|---|---|
outcome | Yes | aligned, contradicted, inconclusive, or identity (the engine did not recognize the brand; answers to scan questions only). null returns the verdict to Asky’s assessment. |
fact_id | No | The fact whose verdict to change. Required when the answer was assessed against several facts, unless all_facts is true. |
all_facts | No | true sets every fact the answer was assessed against to this outcome. |
scan_id | No | The scan the answer is in. Defaults to the latest finished scan. |
note | No | Why your team changed it, kept with the outcome (up to 500 characters). |
Response
The standard API envelope places the answer’s outcome, Asky’s own assessment and each fact’s verdict (outcome, automatic_outcome, overridden, note) in data, with request metadata in meta.
Answer identifiers come from the answers endpoint. An answer reused by several scans carries its outcome into each of them.