- Databases — one row per finished call (web, inbound, outbound).
- Knowledge bases — files for mid-call RAG search.
feature_databases. Console: Monitor → Databases, or attach a database on the agent editor.
How a row is written
- Create a database with a name and columns (
fields). - Attach one or more agents.
- When a call hangs up, Kupe runs post-call extraction and inserts one row per session.
Schema you define, plus built-in analysis fields
summary (string) and success (boolean). Custom fields:
type is string | number | boolean | enum (enum needs enum_values). Unique on (database_id, session_id).
Create and attach
agent_ids on create to attach in the same request.
Routes
Patch
fields to replace the extraction schema for every attached agent.
Destinations
After a row is written you can fan it out. Patchdestinations:
Rows
Each row includesdirection (web | inbound | outbound), values (JSON of schema fields), status (pending | skipped | completed | failed), and sync_error. Search q matches caller, direction, and values text. The console sorts, filters empty columns, hides columns, and exports. Right-click a row to edit values, change a column type, or delete it.
Knowledge bases
Separate product for RAG files. Attach to an agent withconfig.knowledge_base_ids — do not dump FAQs into the system prompt.
Audio assets
Ambient beds for web calls:GET|POST /v1/orgs/{org_id}/projects/{project_id}/audio-assets, archive with POST /v1/audio-assets/{asset_id}/archive.
