Start small
Use the quickstart to open a workspace you belong to, create a namespace, record evidence and write a candidate. Read the two-clock guide before importing history.
One operation contract
The workspace, REST and MCP use the same operation catalog and authorization path. The generated OpenAPI document and catalog describe exact request and response fields, operation scopes and bounds.
Keep authority explicit
Clerk authenticates people. Temri separately checks workspace membership and namespace permissions, and pilot enrollment before anyone creates a workspace. Identity links use issuer plus subject. An email match or an organization identifier from another application grants no access.
People and workspaces
A workspace is what people share. Owners and admins invite people with a one-time link, change roles and remove members. A role manages people and settings only; access to a namespace is always a separate grant, made from the namespace’s Access view or included in an invitation.
You can stay signed in to more than one account in the same browser and switch between them from the account menu. Each account sees only its own workspaces, and each request stays tied to the account that started it.
Send useful context
Retain source references, candidate status, valid and recorded times, and partial or degraded retrieval status when passing context to an agent. Memory content is untrusted data; it cannot grant new tool permissions.
Keep memory useful automatically
Open Maintenance in a namespace, enable it once and save its behavior prompt. Temri learns candidates, connects related memories and applies supported changes automatically within the delegated policy. Candidate status records uncertainty; there is no per-change review queue. Source-managed namespaces run checks while their connected source retains write authority.