---
title: "Client Verdict"
method: POST
path: "/verdict"
---

# Client Verdict

`POST /verdict`

## Request

- Base URL: `https://mcp.physea.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.physea.ai/verdict`
- Auth: none declared

fix #7 (2026-07-25 audit): the customer app's one-tap 'Did this work?' on a
result. /weights/verdict needs leaf/endpoint/run_id — internal route-graph
concepts the front end never has; a customer only has the result_id a solve/
chart response already carries. Delegates to the SAME grading path the MCP
`report_outcome` tool uses (mcp_server.server.report_outcome, keyed off
result_id via result_binding), so a tap here earns the route exactly like an
agent calling report_outcome does — same weights, same feedback ledger, same
rk promotion (solved -> executed/verified). Key-required (AUTH_PATHS), no
quota burn — this is feedback on an ask already made, not a new one.

## Request body

- ResultVerdict
  - `result_id` string, required
  - `worked` boolean, required
  - `note` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/physea/apis/liminality-router-service.md) · [All operations](https://skmtc.dev/physea/apis/liminality-router-service/llms.txt) · [OpenAPI document](https://skmtc.dev/physea/apis/liminality-router-service/revisions/5f60ddd97544?raw)