Run a regression check for a candidate manifest against the baseline
regression
Run a regression check for a candidate manifest against the baseline
Run a regression check for a candidate manifest against the baseline.
Request body:
{
"agent_name": "support-agent",
"candidate_manifest_id": "mfst_xyz",
"pr_context": { # optional
"repo": "acme/support-bot",
"pr_number": 42,
"branch": "fix/refund-prompt",
"commit_sha": "abc123"
},
"trace_window_days": 30 # optional, default 30
}
Query params:
dry_run=true: compute the impact report but do NOT persist a
RegressionCheck row and do NOT consume the org's metered quota.
Useful for local exploration. The response has no `id` field
and the `pr_context` is ignored.
Response: see ImpactReport structure in manifest_impact_service.py.
Behavior on edge cases:
- No baseline exists → returns verdict='first_run', registers candidate
as baseline, status='completed' with zero impacts. (Decision #11)
(Dry-run mode does not register the candidate as baseline either.)
- Candidate manifest doesn't exist → 404
- Candidate manifest belongs to a different agent → 400
POST
Run a regression check for a candidate manifest against the baseline
Authorizations
Enter your API key (e.g. dai_sk_test_key_001)
Headers
Query Parameters
Compute the report without persisting or metering.
Cookies
Body
application/json
The body is of type Payload · object.
Response
Successful Response