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

curl --request POST \ --url https://api.mnemom.ai/v1/recipes/{recipeId}/report \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: <idempotency-key>' \ --data ' { "summary": "<string>", "evidence": "<string>", "agent_id": "<string>", "checkpoint_id": "<string>" } '

Authorizations

Authorization

string

header

required

Supabase JWT token in Authorization: Bearer header

Headers

Idempotency-Key

string

required

Client-supplied UUID (or comparable) for de-duplication. Same key + same body within 24h replays the prior response; same key + different body returns 422.

Path Parameters

recipeId

string

required

Body

application/json

type

enum<string>

required

'fn' (false negative — recipe should have fired) or 'fp' (false positive — recipe fired on legitimate behaviour).

Available options:

fn,

fp

summary

string

required

Customer's description of what happened.

Minimum string length: 1

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

Candidate created; awaiting review.

enum<boolean>

required

Available options:

true

candidate_id

string

required

type

enum<string>

required

Available options:

fn,

fp