List Agent Runs — GET /api/v1/projects/{project_id}/agent-runs
List Agent Runs
Paged AgentRunEntry ledger, newest first (AI-3).
Endpoint: GET /api/v1/projects/{project_id}/agent-runs
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- You must be a member of the project. Admins always have access.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
project_id | path | yes | string (uuid) | ||
agent_id | query | no | string or null | ||
limit | query | no | integer | 50 | |
offset | query | no | integer | 0 | |
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | object (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Agent Investigations
- Operation ID:
list_agent_runs_api_v1_projects__project_id__agent_runs_get - Source code:
backend/app/routers/agent_investigations.py, line 357 - Specification: OpenAPI JSON