Swarm insights

Request swarm run insights

Answers 202: generation is scheduled, not done. Poll the GET above rather than re-requesting.

No credits are consumed — the model cost is on MCPJam. It still draws on the insightsPerDay ledger, which counts REQUESTS and is SHARED with eval-run and user-testing insights, so a request here takes one from there too.

Three refusals, and they mean different things:

  • 429 with code: "RATE_LIMITED" and a short Retry-After — the per-minute burst brake. Wait seconds.
  • 429 naming insightsPerDay in details — the daily ledger. Retry-After counts to UTC midnight.
  • 403 — the feature is not available to your organization. Waiting will never help; collapsing this into the 429s would send someone who hit today's cap shopping for a plan they already have.
post/projects/{projectId}/swarm-runs/{swarmRunId}/insights

Request body

forceboolean

Regenerate over a swarm run that already has insights. OFF by default because it takes a SECOND slice of your organization's shared daily insight quota (no credits either way) — and the common cause of a repeated request is a caller that did not poll.

Response

Generation was scheduled.

swarmRunIdstring required
projectIdstring required
status'pending' required

Changes