Prepare Meeting
Write (or refresh) the prep of a booked meeting from our own records.
API key access
calls:write scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/ai/meeting-prepAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
The booked meeting to prepare.
1 <= length <= 64Response Body
curl -X POST "http://localhost:8000/api/v1/ai/meeting-prep" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{ "meeting_id": "string" }'{
"meeting_id": "string",
"prep": {
"summary": "string",
"who": "string",
"why_now": "string",
"history": [
"string"
],
"open_questions": [
"string"
],
"agenda": [
"string"
],
"talking_points": [
"string"
],
"risks": [
"string"
],
"sources": [
{
"kind": "string",
"label": "string",
"at": "string"
}
]
},
"prompt_id": "string",
"model": "string"
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}List Ai Columns
The workspace's AI columns (RO-340), oldest first, with their cells per status and the credits they used. `entity` filters to the leads or companies table.
Run Ai Column
Queue the column's cells for the given rows (RO-340); a background job fills them through the provider layer, one small AI call per row, charged as AI credits (task `ai_column`). Cells with a result are kept unless `force`. Show the cost first with `POST /ai-credits/estimate` (`action` `ai_column`, `items`). 429 `ai_credits_exhausted` / `ai_credits_user_limit` at the monthly allowance or the member's limit; 429 `ai_columns_daily_limit` past 500 cells a day per workspace.