---
title: "Report a false-positive or false-negative against a protection recipe"
method: POST
path: "/recipes/{recipeId}/report"
tags: ["Recipes"]
---

# Report a false-positive or false-negative against a protection recipe

`POST /recipes/{recipeId}/report`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/recipes/{recipeId}/report`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Files a false-negative ('fn') or false-positive ('fp') report against an existing detection_recipes id. The customer is recorded as the 'created' identity on the recipe_review_actions chain; the candidate lands in `pending` state and awaits review. Requires customer-session auth (JWT cookie / bearer) OR an API key. **Idempotency-Key header is REQUIRED** — the body hash is folded into the reservation so a customer can re-submit with corrected details without 422'ing.

## Path parameters

- `recipeId` string, required

## Headers

- `Idempotency-Key` string, required

## Request body

- object
  - `type` 'fn' | 'fp', required: 'fn' (false negative — recipe should have fired) or 'fp' (false positive — recipe fired on legitimate behaviour).
  - `summary` string, required: Customer's description of what happened.
  - `evidence` string: Optional raw payload / log excerpt the admin reviewer can inspect.
  - `agent_id` string: Optional. Customer's agent id, when the report concerns a specific agent.
  - `checkpoint_id` string: Optional. Related integrity_checkpoints id (helps the reviewer correlate).

## Response `201`

Candidate created; awaiting review.

- object
  - `ok` true, required
  - `candidate_id` string, required
  - `type` 'fn' | 'fp', required
  - `related_recipe_id` string, required

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Cross-origin write refused (`cross_origin_rejected`). A state-changing request that carries the browser session cookie must come from a first-party origin (`Origin`, or failing that `Referer`) and must not send a form-style body (text/plain, urlencoded, multipart) the operation does not declare. Bearer and API-key callers are never subject to this check.
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `422`: Request was well-formed but semantically invalid (e.g., business-rule validation failure, malformed YAML inside a JSON payload).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)