# The one path out of the inbox

`POST /api/v1/captures/{id}/triage`

MCP tool: `triage-capture`

Creates a task from a capture — the body is an `upsert-tasks` item without `dedupe_on` or `ref` — and marks the capture triaged; the capture itself never changes. The capture's references land on the task as `source` references. Any status is allowed, `discarded` and `reference` included. Triaging a capture twice answers with the task the first call made. Triage only on the person's word.

## Parameters

- `id` (path, required)

## Responses

- `200` — Already triaged — the task it already produced
- `201` — The capture was triaged into a new task
- `400` — The request does not match the operation's schema
- `404` — No such capture, or no such project