Get Agent Holdout
Changed onDid this agent do anything? Treated versus its own control arm.
Both arms are counted out of one table on one maturity clause, so they report the SAME outcome by construction rather than by convention. The workspace's organic return rate travels alongside under benchmark, explicitly not causal: it compares different people at different moments and an agent can beat it without having caused anything.
Expect not_yet for a while, and that is the question's property rather than a fault in the answer. The fleet view says how long.
Request
- Base URLhttps://api.minro.com (the document declares no server; this is the origin it was published from)
- URLhttps://api.minro.com/api/v1/agents/{agent_id}/holdout
- Authnone declared
Path parameters
Headers
Bearer <token>
Response
Successful Response
Changes
- info
added the optional property
/to the response with the status - info
added the optional property
/to the response with the status
- info
- info
the
response's property default value{"request_id":"","timestamp":"2026-09-16T23:27:36.856600"}was removed for the status - info
the
response's property default value2026-09-16T23:27:36.856600was removed for the status
- info