Skip to main content
A handful of concepts recur across the entire API. Understanding them once makes every endpoint predictable. They fit together in a line: your data lives in a tenant, organized into datasets that sources feed. You query a dataset through the search model, then page or export the results with handles, save them as views, and trace any result back through provenance.

Tenancy & isolation

Every request acts within one tenant, and data never crosses tenant boundaries.

Datasets & schema

Datasets hold your records and expose a queryable schema and readiness state.

Sources & images

Add JSONL, CSV, or images to a source — records and the images they reference become one searchable thing.

Search model

One envelope spanning text, SQL, and semantic search.

Handles & cursors

Page, export, and re-run queries from a handle instead of copying results.

Views

Save a query or freeze a result set for repeatable analysis.

Provenance

Trace every result back to the source object and line it came from.

​
Roles at a glance

Access within a tenant is role-based. The same tenant header selects the workspace; the token’s role within that workspace decides what it can do. Read endpoints are open to any member; operations that mutate or delete require an admin role. See Roles & permissions for the full breakdown and Plans & RBAC for how enforcement is enabled.