## monitors/feedback

`GET /v1/monitors/feedback`

Records your verdict on findings and remembers it: what you mark known, resolved or irrelevant is not surfaced again by later runs (the same conversation, link, wording, topic or, for irrelevant, author), and what you mark useful is kept as a positive example for the relevance filter.

*Mark findings known, resolved, irrelevant or useful*

| Parameter | Required | Description |
| --- | --- | --- |
| `id` | yes | Monitor id — e.g. `mon_…` |
| `ids` | yes | Finding ids, comma-separated — e.g. `fnd_…,fnd_…` |
| `verdict` | yes | known, resolved, irrelevant or useful — e.g. `irrelevant` |
| `scope` | no | finding (default) or story: apply to the whole story the findings belong to — e.g. `story` |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. — e.g. `1` |

**Cost:** free — 0 credits.

```bash
curl "https://www.monocrawl.com/v1/monitors/feedback?id=mon_%E2%80%A6&ids=fnd_%E2%80%A6%2Cfnd_%E2%80%A6&verdict=irrelevant" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "monitor_id": null,
  "verdict": null,
  "marked": 0,
  "remembered": 0,
  "stories_muted": 0,
  "note": null
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/monitors/feedback#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/monitors/feedback.json)