---
title: "Summarize the week's engagement with AI"
method: POST
path: "/digest/summary"
tags: ["dataroom"]
---

# Summarize the week's engagement with AI

`POST /digest/summary`

## Request

- Base URL: `https://localhost:4410/api/v1`
- URL: `https://localhost:4410/api/v1/digest/summary`
- Auth: HTTP bearer

A few sentences on the week's engagement table, written by the workspace's own language model from firms and metrics (never emails), citing rows as [R1]. Readers who declined detailed analytics are left out. A summary with a number the table doesn't hold, or that the guard reads as predicting investment or saying whom to pursue, is discarded and `summary` is null with the reason. Off unless an owner turned on summaries with AI; needs a decision model for the guard.

## Request body

- object
  - `days` integer

## Response `200`

The result.

- object
  - `summary` string, nullable, required
  - `model` string, nullable, required
  - `unavailable` string, nullable, required
  - `rows` integer[], required

## Other responses

- `default`: An RFC 9457 problem.

---

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