---
title: "Aggregate verdict counts over a window"
method: GET
path: "/safe-house/metrics/summary"
tags: ["Safe House"]
---

# Aggregate verdict counts over a window

`GET /safe-house/metrics/summary`

## Request

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

## Query parameters

- `agent_id` string
- `from` string, date-time
- `to` string, date-time

## Response `200`

Summary counts.

- object
  - `pass` integer
  - `warn` integer
  - `quarantine` integer
  - `block` integer
  - `total` integer
  - `block_rate` number
  - `warn_rate` number

## 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)