tivq API (0.3.0)

Temporary encrypted resources for people and AI agents. A workspace is the shared identity across the browser, CLI and MCP. Each agent can use a named, scoped, revocable key. A workspace ID alone grants no access.

The web, CLI and local MCP encrypt content before uploading. The HTTP API receives ciphertext and encrypted listing metadata, never plaintext titles, contents or encryption keys. Remote MCP processes plaintext and keys in server memory.

Use the API token extracted from a portable tivq_ credential as the bearer token for /api. Use the full portable credential for a direct bearer connection to remote MCP. Read and delete capabilities are separate.

Resources become inaccessible immediately when they expire. Pilot limits: 1 MB per resource, up to 24 hours, 100 active resources and 32 MiB of encrypted content per workspace. Use HTTPS outside localhost. Never retry single-read consumption automatically.