---
title: "List the actions the AI Assistant can take"
method: GET
path: "/assistant/verbs/"
tags: ["workspace-actions"]
---

# List the actions the AI Assistant can take

`GET /assistant/verbs/`

## Request

- Base URL: `https://api.getoneprofile.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.getoneprofile.ai/assistant/verbs/`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

The eight verbs, with their labels and the one static rule: whether the verb always asks first.

## Response `200`

Successful Response

- VerbListResponseSchema: The eight verbs, in display order.
  - `total_count` integer, required
  - `verbs` VerbReadSchema[], required
    - `always_proposes` boolean, required: Whether the verb always waits for a person, whatever was granted.
    - `key` 'create_table_from_search' | 'add_column' | 'run_column' | 'enrich_rows' | 'add_contacts_to_sequence' | 'push_to_destination' | 'call_endpoint' | 'start_search', required: The eight things an AI may do to a workspace. Exactly eight, not sixty: today's cell-level actions all run against one cell, and building a table, adding contacts to a sequence and starting a search had no home at all. Anything new here is a product decision about what an assistant may touch, not a convenience for a planner.
    - `label` string, required

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `422`: Invalid request made to the API.
- `500`: Internal server error.
- `502`: Bad gateway error.
- `503`: Service unavailable.

---

[API](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile.md) · [All operations](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/llms.txt) · [OpenAPI document](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/revisions/4a6bd71e3f02?raw)