> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/agent-work/openapi.json](/docs/api/agent-work/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Agent work: Submit agent work answers

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Agent work](/docs/api/agent-work.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Submit agent work answers

`POST /v1/agent-work/claims/{claimId}/answers` - operationId `agent-work.submit-answers`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 300 requests a minute and 6,000 an hour per workspace |

Takes in up to 50 answers to the claim's items: `{ "agent": { "cli", "model" }, "answers": [ { "itemId",
"output" } ] }`. `output` is a JSON object for a `json` item and a string for a `text` item, at most
64 KB. Returns one result per answer, in the order sent: `accepted` (stored where Kenso's AI would have stored
it); `rejected` with a `reason` (`invalid_format`, `too_large`, `unknown_item` or a check
the answer failed; the item is closed and its work goes back to the queue); `expired` (the claim ran out or was
released, or the record no longer needs an answer); `duplicate` (the item already has an answer, or one is being
taken in). Each result also has `retryable`: true only when Kenso could not take the answer in and the item is
still held (`rejected` with `failed_checks`), so send that answer again; false for every other result.
Always `200` when the claim exists, whatever each answer's result. Answer items of a claim in as many calls as you like: the claim closes once
every item is answered. The agent's `cli` and `model` are saved on the claim. Send an
`Idempotency-Key` to retry safely: an answer stored once is never stored twice.

Errors:

- `400 validation_failed`: no answers, more than 50, an answer that is not an object, or an agent name over
100 characters.
- `403 forbidden`: you may not write the claim's kind.
- `404 not_found`: the workspace does not have the `agent_work` feature, or the claim is not the
workspace's.
- `429 rate_limited`: more than 300 submits a minute or 6,000 an hour for the workspace.

Open to any workspace member except a Client seat who may write the claim's kind.

Needs the `agent_work` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/agent-work/POST/v1/agent-work/claims/%7BclaimId%7D/answers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `claimId` | path | string | yes |  |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |
| `Idempotency-Key` | header | string | no | A unique value, such as a UUID, that makes a retry safe. Send the same key when you retry. For 24 hours, a repeat of the same request with the same key gets the first response again, with the `Idempotent-Replayed: true` header, and Kenso does not run the action twice. The same key with a different request answers `422 idempotency_key_reused`. Keys are per workspace and at most 200 characters long. A repeat sent while the first request is still running can get `503 service_unavailable` with `Retry-After`. Retry it with the same key. Kenso does not store a `5xx` response, so a retry after one runs the action again. It does not store a `408`, a `429` or another `4xx` that carries `Retry-After` either: retry with the same key after that time and Kenso runs the action again. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `agent` | AgentWorkAgentBody | no | The agent that wrote the answers, saved on the claim. Optional. |
| `answers` | array of AgentWorkAnswerBody | no | 1 to 50 answers, each to an item of this claim. |

### Response 200

`data` is a `AgentWorkSubmit`.

| Field | Type | Description |
| --- | --- | --- |
| `results` | array of AgentWorkAnswerResult | One result per answer, in the order sent. |
| `accepted` | integer (int32) | How many answers were accepted. |
| `rejected` | integer (int32) | How many answers were rejected. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/agent-work/claims/01JC8Z3K6Q2W4M7N9P5R1T3V5X/answers" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "agent": {
    "cli": "claude-code",
    "model": "string"
  },
  "answers": [
    {
      "itemId": "string",
      "output": null
    }
  ]
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "results": [
      {
        "itemId": "string",
        "status": "string",
        "reason": "invalid_format",
        "message": "string",
        "retryable": true
      }
    ],
    "accepted": 1,
    "rejected": 1
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### AgentWorkAgentBody

The agent that wrote the answers.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `cli` | string | no | The agent's CLI, such as `claude-code` or `codex`. At most 100 characters. |
| `model` | string | no | The model that wrote the answers. At most 100 characters. |

### AgentWorkAnswerBody

One answer.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `itemId` | string | no | The item's id from the claim. |
| `output` | object | no | The answer: a JSON object for a `json` item, a string for a `text` item. At most 64 KB. |

### AgentWorkAnswerResult

One answer's result.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `itemId` | string | no | The answer's `itemId`, as sent. |
| `status` | string | no | `accepted` (stored); `rejected` (see `reason`; the item is closed and its work goes back to the queue, unless `retryable` is true); `expired` (the claim ran out or was released, or the record no longer needs an answer); `duplicate` (the item already has an answer, or one is being taken in). |
| `reason` | string | no | Why a `rejected` answer was refused: `invalid_format`, `schema_mismatch`, `wrong_language`, `leaked_reasoning`, `failed_checks`, `human_written`, `unknown_item` or `too_large`. Null otherwise. |
| `message` | string | no | A sentence for a person, or null. |
| `retryable` | boolean | no | True only when the answer was not taken in and its item is still held, so send it again (a `rejected` result with `failed_checks`). False for every other result: do not send that answer again. |
