---
title: "Tiering Decide"
method: POST
path: "/api/asclepius/verify/tiering/{user_id}/decide"
tags: ["asclepius-verify"]
---

# Tiering Decide

`POST /api/asclepius/verify/tiering/{user_id}/decide`

## Request

- Base URL: `https://app.archangelhealth.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://app.archangelhealth.ai/api/asclepius/verify/tiering/{user_id}/decide`
- Auth: none declared

Record an explicit tier decision as a training observation, without re-approving.

Separate from ``/approve`` on purpose. Approval is a lifecycle event that happens once;
a tier judgment is something an admin may make repeatedly and per-domain, and every one of
those is a label. Collapsing them would throw away most of the training signal — the
override IS the training signal (§5.3).

## Path parameters

- `user_id` string, required

## Headers

- `authorization` string, nullable

## Request body

- TierOverrideBody
  - `tier` string, required
  - `case_domain` string, nullable
  - `note` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform.md) - [All operations](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform/llms.txt) - [OpenAPI document](https://skmtc.dev/archangelhealth/apis/archangel-health-surgical-patient-platform/revisions/3514f4e119da?raw)