---
title: "Aggregate Safe House evaluation stats"
method: GET
path: "/safe-house/stats"
tags: ["Safe House"]
---

# Aggregate Safe House evaluation stats

`GET /safe-house/stats`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/safe-house/stats`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

## Query parameters

- `days` integer

## Response `200`

Per-tenant verdict counts + threat-type histogram over the window, scoped to the caller's org. Empty window returns zeroed counts (never 500).

- object
  - `verdicts` object: Count of evaluations by verdict (pass/warn/quarantine/block).
  - `threat_types` object[]: Top threat types by occurrence over the window.
    - `threat_type` string
    - `count` integer
  - `period_days` integer
  - `total_messages` integer: Total evaluations in the window.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `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)