The v2 API is in beta. Endpoints and response shapes may still change.
- Agent — a worker in your org. Create one and reuse it.
- Run — one brief and the work that follows. An agent does one run at a time.
- Table — what the agent builds. Read its rows with
GET /api/v2/tables/{tableId}/rows.
How runs work
Every run is asynchronous.POST /api/v2/agents and POST /api/v2/agents/{id}/runs
respond 202 Accepted with the run already running — the agent works in the background.
You poll GET /api/v2/agents/{id}/runs/{runId} until status
is no longer running, honoring the Retry-After header (15 seconds) while it runs. Runs
typically take 1–5 minutes. See the run object for the full response
shape.
Pick a model per run with the model field — origami-lite or origami-max. The default
is the highest model your plan unlocks (origami-lite on starter, origami-max on pro and
above).
Start here
Quickstart
Start an agent, follow up, poll, and fetch the data — end to end.
Create an agent
The first call, and every field it takes.
Run object
Status, actions, tables, and the optional stats and transcript.
Read rows back
Pull the rows the agent built, with typed cells, filters, and CSV.
GET /api/v2/tables/{tableId}/rows.