Private intelligence,
specified.

Umbra is a private AI workspace for asking questions, making images and video, writing code, and connecting your own tools. It is not a model, an account system, or a server-side archive of your conversations.

In browser chat, Smart Privacy detects recognizable details before the request leaves your device. A provider receives the redacted text; the browser keeps the reversible mapping and restores your context when the response returns.

Smart Privacy is the default. Full adds lower-confidence contextual categories, while Off leaves the prompt unchanged. The detector set covers names, email addresses, phone numbers, locations, URLs, IP addresses, EVM addresses and transaction hashes, secrets, financial identifiers, organizations, money, dates of birth, and health terms.

Avery Chen → [PERSON_1]
avery@example.com → [EMAIL_1]
0x1234…7890 → [WALLET_1]
Lisbon → [LOCATION_1]

Each replacement is recorded in a local receipt. When the response arrives, the browser restores placeholders such as [PERSON_1] and [EMAIL_1] from the conversation vault. The Leak check surface lets you inspect a prompt without sending it anywhere.

UmbraChat can use the configured model catalog directly or choose with umbra-auto. The router considers the prompt and available model capabilities; a selected model is shown with the response.

The Tune panel exposes temperature, reasoning effort where a model supports it, and optional web search. Search results include URL citations beneath the answer. UmbraCouncil sends one browser-redacted brief to up to three seats in parallel; council runs remain in memory and are not saved as conversations.

The model catalog lists the configured models, context windows, pricing, and declared capabilities. The usage dashboard stores only provider-reported accounting by day and model.

Conversations, manually written memory entries, settings, usage records, connector registrations, and API key records use IndexedDB in this browser. Memory is optional manual context, not automatic learning or a profile inferred from your conversations. Umbra can suggest memories from your own wording, entirely in this browser.

The credits vault is encrypted with Web Crypto and can be exported as an encrypted recovery file. A wipe-data control clears local application state. There is no sync service: switching browsers or devices does not bring these records with you unless you explicitly export and import the relevant recovery data.

Text files (.txt, .md, .csv, and .json), PDFs, and images can be attached in Chat. Text and PDF content is extracted in the browser; image data is passed only to models that declare vision support.

Extracted text uses the same privacy boundary as the prompt. The combined extracted text sent for a turn is capped at 120,000 characters, and the chat surface marks truncated attachments. Umbra does not provide server-side file storage.

The Connectors surface stores endpoint registrations in this browser and uses the /api/mcp proxy for cross-origin requests. The proxy accepts HTTPS URLs and supports initialize, tools/list, and tools/call operations.

Discover tools and run them manually from the connector surface. Optional agentic tool use can ask the model to choose from discovered tools, with a maximum of three tool rounds in a turn. Arguments are restored before a connector call and results are redacted before returning to the model.

UmbraCode turns a product idea into project files through the configured coding model. Its preview renders those files in an isolated sandboxed iframe rather than mixing generated markup into the workspace page.

The surface is designed for iterative prompts, file inspection, and a live preview. It does not promise a production deployment or replace a project's own security review.

The API is available at /api/agent/v1 relative to your Umbra host. Create persistent keys from Developers; keys can be revoked there or through the revoke endpoint. The full key is returned once and stored only in the browser that created it.

There are no accounts, so possession of a key is the authorization to revoke it. API requests are not browser chat: client applications must redact their own prompts before sending them.

A signed holder proof can attach a verified $UMBRA tier to a new key. Each key then has an enforced daily quota: 200 for Base, 1,000 for Holder, 5,000 for Circle, and 20,000 for Council.

curl https://{your-domain}/api/agent/v1/chat/completions \
  -H "Authorization: Bearer $UMBRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"umbra-auto","stream":false,"messages":[{"role":"user","content":"Hello"}]}'

const response = await fetch("https://{your-domain}/api/agent/v1/chat/completions", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.UMBRA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: "umbra-auto",
    stream: false,
    messages: [{ role: "user", content: "Hello" }],
  }),
});
const completion = await response.json();
console.log(completion.choices[0].message.content);

Self-hosters can still sign tokens directly with UMBRA_API_SECRET. The API server does not store prompt or response text.

Credits are held in an encrypted, browser-only vault. The Credits surface reads wallet balances on Ethereum and, when a treasury is configured, sends USDG to that treasury. After confirmation, the browser verifies the receipt through the public RPC and grants matching local credits once per transaction hash.

Wallet connections support multiple browser extensions through EIP-6963, plus WalletConnect QR sessions when configured.

Sending USDG transfers real funds. It does not create an account or imply refunds. The treasury address is public build configuration from NEXT_PUBLIC_UMBRA_TREASURY; when it is absent, the top-up form remains unavailable.

Clearing local data or losing the recovery file loses the displayed local balance. Umbra does not hold an account balance on your behalf.

Provider availability, model capabilities, browser storage, detector coverage, and local credentials can all affect a result. This specification describes the shipped boundary, not a guarantee that every provider or browser behaves the same way.