Select authorized storage
Bytes stores files in a platform-verified organization and workspace. Discover a granted workspace through CLI/MCP. Shared org and caller-private scopes stay within that workspace; the legacy all value supplies no cross-organization access.
Upload and verify bytes
Use an authenticated upload session for up to 100 MiB, or a configured R2 multipart session for large files. Session creation and part URL signing do not establish persisted bytes. Complete the upload and verify actual content and storage state.
Find and organize files
Listing can generate derived thumbnails and search can backfill semantic entries. Those GET actions require effect confirmation in CLI/MCP. Inspect pagination and filters; bulk operations report individual failures and provide no atomic undo.
Share and revoke access
Inspect view/download permissions, expiry and password protection before exposing a link. Sharing creation schedules notifications and usage integration; it is not proof of delivery. Rename and move handlers do not rewrite stored share paths.
Protect and export data
Workspace export contains file metadata and redacted share records, not the content needed to restore files. Erasure permanently removes files, vectors and shares in the verified workspace; empty-workspace archival is a separate platform operation.
Use the action reference
All 30 published Bytes actions have worked guides, success schemas, captured synthetic responses, exact refusals, verification and recovery. Native agent guidance remains separate from the readable body. Runtime deployment and provider proof remain environment-specific.
Action reference
Evidence
Actual exported Worker handlers with local Miniflare R2/KV. Auth, workspace grants, R2 multipart, notification, usage and semantic integrations are simulated at their configured test boundaries. Synthetic ids, timestamps and signed URLs confer no live access. No deployed provider outcome, external delivery or live grant is established. Upload-session credential values are explicitly redacted; binary responses use the tested SDK transport envelope.