Omni Developers

Files & Vault

Upload encrypted files, wait for Vault readiness, and ground stateful tasks in your knowledge.

Files stores encrypted bytes. Vault processes completed files into knowledge Omni can recall. They are connected, but their states are deliberately distinct.

  1. Local fileYour source bytes
  2. Encryptomni-file-v1
  3. UploadReturned PUT capability
  4. CompleteCiphertext stored
  5. READYVault processing finished
  6. AskAttach file_id
  7. [V1]Validated citation

COMPLETE is not READY

Completing an upload confirms the encrypted object was stored. Wait until the workspace Vault record reports ready before attaching the file to a task.

Public file lifecycle

  1. Reserve an encrypted upload with POST /v1/files/uploads.
  2. PUT ciphertext to the returned capability URL using its returned headers.
  3. Confirm storage with POST /v1/files/{file_id}/complete.
  4. Poll GET /v1/workspaces/{workspace_id}/vault/files/{file_id}.
  5. Use the ready file_id in attachments.

Clients never send a project ID, bucket, provider, object path, storage target, placement, owner, or tenant ID. Upload capability URLs are temporary and should not be logged.

Start with Upload knowledge, then Ask with a file.

Workspaces

Discover the persistent Omni workspaces available to the authenticated user.

Conversation History

Read durable workspace messages and citations through a stable public abstraction.

On this page

Public file lifecycle