---
title: "Request insights for an eval run"
method: POST
path: "/projects/{projectId}/eval-runs/{runId}/insights"
tags: ["Evals"]
---

# Request insights for an eval run

`POST /projects/{projectId}/eval-runs/{runId}/insights`

**Spends.** Runs a model over the finished run and draws on the same shared `insightsPerDay` ledger as swarm and user-testing insights.

`202`: scheduled, not done. Poll the run detail's `insights` envelope rather than re-requesting — the envelope's `status` distinguishes `pending` from `not_requested`, which a second POST would not.

## Request body

- EvalRunInsightsRequest — Optional. A bodyless POST is the ordinary case.
  - `force` boolean — Regenerate even when insights already exist. SPENDS AGAIN. Must be a real boolean — `"false"` is rejected rather than read as consent.

## Response `202`

Scheduled.

- EvalRunInsightsRequested
  - `runId` string, required
  - `projectId` string, required
  - `status` 'pending', required

## Other responses

- `400` — Malformed body or parameters.
- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/f338eb09898f/schema)