Sign in
experiments

Get Agent Holdout

Did 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.

get/api/v1/agents/{agent_id}/holdout

Path parameters

agent_idstring uuid required

Headers

authorizationstring nullable

Bearer <token>

Bearer <token>

Response

Successful Response

dataobject required

Changes

Changed in 5 of the 6 revisions of this API.12

  • 5691a8e121582See the full diff
    • ○

      the response's property default value changed from {"request_id":"","timestamp":"2026-09-04T03:53:05.348646"} to {"request_id":"","timestamp":"2026-09-05T02:09:45.736252"} for the status

      response-property-default-value-changed

    • ○

      the response's property default value changed from 2026-09-04T03:53:05.348646 to 2026-09-05T02:09:45.736252 for the status

      response-property-default-value-changed

  • 6be81c2b52735See the full diff
    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      added the optional property / to the response with the status

      response-optional-property-added

    • ○

      the response's property default value changed from {"request_id":"","timestamp":"2026-09-03T19:42:04.697120"} to {"request_id":"","timestamp":"2026-09-04T03:53:05.348646"} for the status

      response-property-default-value-changed

    • ○

      the response's property default value changed from 2026-09-03T19:42:04.697120 to 2026-09-04T03:53:05.348646 for the status

      response-property-default-value-changed

  • dd130eae1c322See the full diff
    • ○

      the response's property default value changed from {"request_id":"","timestamp":"2026-09-03T04:12:49.531787"} to {"request_id":"","timestamp":"2026-09-03T19:42:04.697120"} for the status

      response-property-default-value-changed

    • ○

      the response's property default value changed from 2026-09-03T04:12:49.531787 to 2026-09-03T19:42:04.697120 for the status

      response-property-default-value-changed

  • 1ced22f7f72c2See the full diff
    • ○

      the response's property default value changed from {"request_id":"","timestamp":"2026-09-02T16:58:28.431377"} to {"request_id":"","timestamp":"2026-09-03T04:12:49.531787"} for the status

      response-property-default-value-changed

    • ○

      the response's property default value changed from 2026-09-02T16:58:28.431377 to 2026-09-03T04:12:49.531787 for the status

      response-property-default-value-changed

  • 6bd3ca9033ae1See the full diff
    • ○

      endpoint added

      endpoint-added