> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Orientation: agents, configuration state, and a suggested next action

> The org's agents with their configuration state, the three top-level counts, and a suggested next action.

### Response

`object`

<ResponseField name="object" type="string" required />

<ResponseField name="agent_count" type="integer" required />

<ResponseField name="active_agent_count" type="integer" required>
  Agents with `activated: true`.
</ResponseField>

<ResponseField name="unverified_agent_count" type="integer" required>
  Agents with `eval_count: 0` — nothing checks they still behave after a change.
</ResponseField>

<ResponseField name="agents" type="object[]" required>
  Ordered by `updated_at` descending.

  <Expandable title="agents">
    <ResponseField name="id" type="string (uuid)" required />

    <ResponseField name="name" type="string,null" required />

    <ResponseField name="type" type="string,null" required />

    <ResponseField name="activated" type="boolean" required />

    <ResponseField name="has_instructions" type="boolean" required>
      Whether the agent has a non-empty `instructions` persona.
    </ResponseField>

    <ResponseField name="rule_count" type="integer" required>
      Best-effort: falls back to 0 if the count query fails.
    </ResponseField>

    <ResponseField name="function_count" type="integer" required>
      Best-effort: falls back to 0 if the count query fails.
    </ResponseField>

    <ResponseField name="eval_count" type="integer" required>
      Best-effort: falls back to 0 if the count query fails.
    </ResponseField>

    <ResponseField name="updated_at" type="string,null (date-time)" required />
  </Expandable>
</ResponseField>

<ResponseField name="next_action" type="string" required>
  A one-sentence suggestion, in order of priority: create an agent; give an agent instructions; add a rule; add evals; activate; or run evals / review analytics.
</ResponseField>

### Status codes

| Code  | Meaning                                                                                                   |
| ----- | --------------------------------------------------------------------------------------------------------- |
| `200` | The org's agents with their configuration state, the three top-level counts, and a suggested next action. |
| `401` | Missing, invalid, or expired API key.                                                                     |
| `403` | The key lacks a required scope.                                                                           |
| `429` | Rate limit exceeded.                                                                                      |

### Access

|                |                         |
| -------------- | ----------------------- |
| Required scope | `agents:read`           |
| Rate limit     | 120 requests per minute |

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://response.stateset.com/api/v1/workspace' \
    --header "Authorization: Bearer $RESPONSECX_API_KEY"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "object": "workspace",
    "agent_count": 1,
    "active_agent_count": 1,
    "unverified_agent_count": 1,
    "agents": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "name": "Two-Person Tent",
        "type": "standard",
        "activated": true,
        "has_instructions": true,
        "rule_count": 1,
        "function_count": 1,
        "eval_count": 1,
        "updated_at": "2026-08-31T14:22:05Z"
      }
    ],
    "next_action": "string"
  }
  ```
</ResponseExample>