# Use the same memory from your product.

The canonical REST base is https://temri.ai/v1. Start with the generated operation contract.

## Authentication and workspace selection

The browser sends a current Clerk session bearer token. OAuth access tokens must match the exact configured REST resource audience, issuer, expiry and operation scopes. A product-installation credential is separately issued, narrowed and revocable.

For a human session, X-Temri-Workspace selects a canonical ws_ workspace ID and current membership is checked on every request. A service key is bound to its workspace; a selector cannot broaden it. Never send caller-created principal objects.

```http
GET /v1/workspaces
Authorization: Bearer <current-session-token>
```

## Namespace capabilities

Capabilities are read, observe, verify, correct, forget and admin. OAuth scopes use the temri: prefix, such as temri:read and temri:observe. Default scopes are read and observe. Namespace grants remain required even with an operation scope.

## Mutation retries

Every mutation requires an Idempotency-Key. Reuse it for an identical retry: the server replays its result. A changed payload under the same key returns 409. Read-only POST /v1/recall does not need a mutation key. Resolve uncertain writes by replay or readback rather than inventing a new key.

## Bounded recall and indexing

Recall accepts authorized namespace selectors, as_of, known_at and a context budget. Writes commit the ledger before asynchronous indexing and return a commit sequence. A min_sequence request can report pending indexing. Preserve partial and degraded status; exhausted refill budgets are not proof of absence.

> The first development deployment is configured for lexical retrieval with hybrid search disabled. Recall reports degraded coverage when the search provider is unavailable. Production hybrid search remains a release gate.

A min_sequence beyond the indexed sequence remains pending while indexing is disabled. Omit that field only when you deliberately accept retrieval without waiting for indexing. Direct memory reads remain available immediately after the ledger commit.

## Errors and privacy

Errors are structured JSON with stable codes and retryability. An unauthorized ID looks like an absent ID. Revoked or expired credentials require renewed authorization; do not fall back to stale private data. Private responses use private, no-store caching.

## Generated schema is authoritative

Read /openapi.json for exact inputs, outputs, scopes and bounds. It is generated by the shared catalog owner. Examples in this guide describe the connection contract; never put provider secrets into browser code.

## Continue reading

- [Temri · Memory with a sense of time](https://temri.ai/): Shared temporal memory for products and agents. Keep source-backed facts in protected namespaces and distinguish what applied then from what was known then.
- [How Temri works · From evidence to memory](https://temri.ai/how-it-works): Follow a memory from its source to a candidate, verification, historical retrieval, correction and deletion receipt.
- [Developer documentation · Temri](https://temri.ai/docs): Connect to Temri through REST and MCP. Learn workspace permissions, evidence, temporal queries and bounded retrieval.
- [Create your first memory · Temri quickstart](https://temri.ai/docs/quickstart): Use an enrolled Temri workspace to create a namespace, record evidence, save a candidate and recall it with explicit time controls.
- [The two clocks · Temri temporal semantics](https://temri.ai/docs/temporal): Understand as_of and known_at, half-open intervals, correction history, server-owned recorded time and deletion suppression.
- [Connect an agent · Temri MCP docs](https://temri.ai/docs/mcp): Connect to Temri’s authenticated MCP resource with narrowed scopes. Discover operations and verify your client before sharing memory.
- [Privacy, retention and deletion · Temri](https://temri.ai/privacy): What Temri stores, which services process it, how namespace access works and what a deletion receipt does and does not cover.
- [Pilot terms · Temri](https://temri.ai/terms): Terms for Temri’s admin-managed pilot, responsible use, source-backed claims, service limitations and account access.

[OpenAPI](https://temri.ai/openapi.json) · [Workspace](https://temri.ai/app)