The Conversation API is the control-plane surface for chat history and agent execution state. It stores conversation data in Postgres, coordinates live agent output, and keeps a durable event log for replay and recovery.Documentation Index
Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Docs map
Concepts
| Page | Use it to understand |
|---|---|
| Architecture and flow | How a message moves through Studio, API, agents, streams, and durable state |
| Durable execution | How messages, agent runs, workflow runs, job runs, tasks, and cron jobs relate |
| Events and streaming | How SSE AG-UI transport maps to persisted run events and WebSocket notifications |
| Datastores and lineage | How Postgres, Redis, IDs, parent links, and cursors fit together |
Reference
| Page | Use it to find |
|---|---|
| Endpoints and validation | REST operations, SSE stream routes, WebSocket notification routes, AG-UI routes, durable run routes, control-plane routes, and schema contracts |
| Authorization | Bearer token, project access, conversation access, and JWS boundaries |
| Connect an agent | The runtime contract for developer-provided agents |
Key concepts
- Conversation: The durable thread that owns messages, participants, read state, and conversation-owned runs.
- Message: A user, assistant, or tool entry made from typed content parts.
- Run: A canonical durable execution record with a public run ID, kind, owner, status, parent run, and root run.
- Agent run: A conversation-owned run with
kind: "agent". It represents chat or project-agent execution attached to a conversation. - Workflow run: A project-owned run with
kind: "workflow". It represents a workflow target and its step graph. - Job run: A project-owned run with
kind: "job". It represents background execution of a target, including task targets. - Task: A developer-defined unit of background work. Jobs execute tasks when the job target points at a task.
- Cron job: A schedule definition. Each scheduled or manual trigger creates a job run.
- Run event: An ordered event attached to a run. Events power snapshots, replay, and public SSE streams.
- SSE stream: The response transport that updates Studio while a run is active.
- WebSocket notification: A lightweight event that tells Studio to invalidate and refetch state. It does not carry the token stream.