# Witbitz > Witbitz (https://witbitz.chat) is a **trusted runtime** for building collaborative applications where humans, > applications, and autonomous AI agents work together safely, under explicit permissions. You build your app as a > **static website with a verifiable privacy policy**, and Witbitz provides the runtime underneath — identity, > permissions, agents, storage, payments, and secure execution. It is built on the open Kibitz engine and inherits > its account-free, link-based room model. Witbitz is **three layers**: (1) **interaction** — how humans and AI meet, today live calls and async Spaces; (2) **the platform** — a general-purpose app backend that carries the whole app flow and the AI that runs *inside* the app; (3) **the app** — an extreme **backendless** static page that connects only to Witbitz, which is exactly what makes its privacy *verifiable*. Everything happens in a **Space**: a self-authenticated room whose identity, members, and keys live in the link, not a central account server. The platform is **content-blind** — a Space's data is sealed ciphertext at rest, so as long as the compute runs the declared program, neither the operator **nor the app's own owner** can read the users' content (the "double blind"). Agents never own authority; they receive delegated, revocable authority, and a human keeps the final say (propose → approve → execute). The first app is **Spaces**, a multiplayer ChatGPT. This file is a map for language models. Each page below links to its clean Markdown (`.md`). The full text of every doc inlined into one file is at https://docs.witbitz.chat/llms-full.txt. ## Start here - [What Witbitz is (portal home)](https://docs.witbitz.chat/): the trusted-runtime idea, the three layers, the double blind, the featured Spaces app, and what you can build (the app topologies). Read this first. ## Docs (deep dives, code-synced) - [What Witbitz is — the platform](https://docs.witbitz.chat/docs/platform.md): the read-first overview — the idea, the runtime services, the three layers (interaction / platform / app), the two guarantees (double blind + human authority), exactly what's reused from Kibitz vs witbitz's own, the first app, and the app topologies. - [The Space link is the auth](https://docs.witbitz.chat/docs/room-link-auth.md): who is in a room and who said what, with a content-blind platform and no stored ACL — membership by key possession (`mkCommit`), the k-of-n key model, the E2EE ledger + decrypt-once render (the double blind), per-member entry signatures fully compatible with the Kibitz room link (invite-token grants → per-entry signatures → verified author), admission via the inherited Kibitz join gate, and blind-safe short links. - [Async Spaces](https://docs.witbitz.chat/docs/async-spaces.md): the agent as a function, not a server — the sealed ledger, the decrypt-once render, content-blind poll (etag over ciphertext), the ops, idle ~ $0. Live in prod. - [The double blind](https://docs.witbitz.chat/docs/the-double-blind.md): verifiable privacy — ciphertext at rest (platform blind) + a backendless static app (owner blind) + the certify-the-footprint north-star; shipped vs designed. - [Delegated authority](https://docs.witbitz.chat/docs/delegated-authority.md): humans keep the final say — propose, approve, execute + a sealed append-only audit; the invariant that no action runs without an approval. - [Platform API — the /v1 surface](https://docs.witbitz.chat/docs/api-reference.md): tenant-keyed JSON API — auth (secret/publishable keys + capability tokens), the envelope, idempotency, and the surface (agents, collections, items, artifacts, sessions, credits, tenants). The OpenAPI is canonical. - [The Bridge](https://docs.witbitz.chat/docs/the-bridge.md): governed collaboration between sovereign Spaces (the cross-org frontier) — the three-space model, the five invariants, key epochs, the live ops, native-or-external parties. Early protocol preview. ## API - [Platform API — OpenAPI (production)](https://api.witbitz.chat/v1/openapi.json) · [full design spec](https://api.witbitz.chat/v1/openapi.full.json) · [discovery](https://api.witbitz.chat/v1/): tenant-keyed, JSON over HTTPS. Agents, collections, sessions, wallets, ratings; a keyless render page for published content. Invite-only during private beta. - [The Bridge protocol — OpenAPI](https://docs.witbitz.chat/bridge.openapi.yaml) · [normative spec](https://docs.witbitz.chat/bridge-protocol.md): governed collaboration between sovereign Spaces (the forward-looking, cross-org frontier) — a shared Space N parties join, party-signed + content-blind, verified against per-party keys. Early protocol preview. ## Try it - [The Spaces app (demo)](https://witbitz-spaces.pages.dev): a multiplayer ChatGPT — a shared room where people and an AI collaborate, with tools that render as live widgets and a room that persists. No install, no account. ## The engine (Kibitz) Witbitz runs on the open Kibitz engine. The **live call IS Kibitz** — that path uses the deep-dives below by *running the engine*. The **async Space** is witbitz's own (turn-based, content-blind HTTP); it ports only the Kibitz **signed-invite** identity format (see the link-auth doc above), NOT the OIDC/cert-binding path. These Kibitz docs are canonical for the engine — witbitz does not duplicate them: - [Kibitz map for LLMs](https://kibitz.chat/llms.txt) · [everything in one fetch](https://kibitz.chat/llms-full.txt) - [Architecture](https://kibitz.chat/docs/architecture) — the room model, the transport planes, the composable engine. - [Threat model](https://kibitz.chat/docs/threat-model) — who can see what; the agent surface. - [Verification](https://kibitz.chat/docs/verification) — "the link is the verifier": the join-gate methods (the source we ported for async). - [Cert-binding](https://kibitz.chat/docs/cert-binding) — how an OIDC token is bound to the DTLS cert (the LIVE-only mechanism async does not use). - [Agent protocol](https://kibitz.chat/docs/agent-protocol) · [Agent platform](https://kibitz.chat/docs/agent-platform) — how an AI agent perceives + acts in a call, and the capability/consent model. - [Offline mode](https://kibitz.chat/docs/offline-mode) — same-Wi-Fi rooms via a LAN hub. ## Contact - hello@witbitz.chat — API access (private beta), general, and security.