---
title: "Run Workbench Ai"
method: POST
path: "/workbench/tables/{table_id}/ai/run-all"
tags: ["Workbench"]
---

# Run Workbench Ai

`POST /workbench/tables/{table_id}/ai/run-all`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/workbench/tables/{table_id}/ai/run-all`
- Auth: HTTP bearer

Run every configured AI pass over the table. SPENDS CREDITS.

OMITTING `row_ids` RUNS EVERY ROW, and the body is optional - so a bare
`POST` with no body at all is "enrich this entire table". On a 10,000-row
table with three configured columns that is 30,000 model calls.

Set `approved_max_credits`. The run refuses to exceed it, and a credit
preflight happens before any work starts, so an over-budget request costs
nothing rather than costing until the balance runs out.

Returns 202 and a handle: the work happens in the background. The group's
`skip_existing_values` and `skip_recently_enriched` settings still apply,
so re-running is usually far cheaper than the first pass.

## Path parameters

- `table_id` string, required: Workbench table id (UUID).

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- RunStagingAIRequest: Which rows a run covers, and the spend the caller approved. OMITTING `row_ids` RUNS EVERY ROW. `exclude_row_ids` narrows that back down.
  - `row_ids` integer[], nullable: Rows to run. OMIT to run EVERY row in the table.
  - `exclude_row_ids` integer[], nullable
  - `model` string, nullable: Override the configured model.
  - `prompt` string, nullable: Override the configured prompt.
  - `status_filter` string, nullable
  - `conditions` object[], nullable
  - `qualification_mode` boolean
  - `multi_row_output` boolean, nullable
  - `max_rows_per_source` integer, nullable
  - `approved_max_credits` integer, nullable: Ceiling the caller approves. The run refuses to exceed it.
  - `quote_expires_at` string, date-time, nullable
  - `quote_id` string, uuid, nullable

## Response `202`

Successful Response

- ApiResponseEnrichmentPayload
  - `data` EnrichmentPayload, required: One enrichment object, open-shaped. Open on purpose: a workbench column set is defined by the CUSTOMER at runtime, and the enrichment result shapes grow with every provider added. Pinning them would drop whatever a provider returned that this contract had not caught up on, which on an enrichment surface is the data the customer paid for.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)