Assets start in your system
Ingest requests carry yourasset_id, so search results can join back to your database, CRM, support ticket, observability platform, or call log without ID translation.
Asset classes define search scope
asset_class is how you draw the boundary around what gets searched together. For most products, it maps to the entity your customers think in terms of:
- one end customer
- one workspace
- one project
- one support queue
Indexing surface types
types controls what gets indexed and searched.
| Type | Use when |
|---|---|
audio | Speaker identity, acoustic events, sound-level patterns. |
video | On-screen content, visual context, screen recordings. |
transcript | Spoken words, topic retrieval, semantic search over dialogue. |
Indexing is async
Ingest returns atask_id immediately. The actual indexing happens in the background. Poll until ready or failed.
pending → indexing → ready (or failed).
Search returns timestamped matches
Results includestart_ms and end_ms: millisecond offsets into the source recording.
threshold controls how strict the match has to be. Default is 0.5. Raise it to get fewer, higher-confidence results.
Your data stays yours
The API returns:asset_id, asset_class, types, scores, and timestamps. Provider IDs, index keys, and pipeline details stay behind the API.
TypeScript SDK
Inputs, outputs, and error types for the TypeScript client.

