upload_asset

Upload a local file to Scenario and return an asset_id for use in run_model, analyze, display_asset, or other asset-backed tools. Two paths: (1) multipart presigned-URL upload (preferred), or (2) small inline base64 upload. IMPORTANT: Always prefer the multipart path when the host has shell access (e.g. Claude Desktop, Claude Code, Cursor). Passing base64 data in the tool call consumes context window and will fail or saturate the conversation for files above ~100KB. Only use inline base64 for very small files (<100KB) or when no shell is available. Args: - file_name, content_type, kind: required file metadata - file_size: required for multipart uploads — omit 'data' and pass file_size in bytes instead - data: base64 file contents — ONLY for tiny files (<100KB) when no shell is available - team_id, project_id: required for OAuth callers Returns: for multipart uploads, returns presigned upload URLs and upload_id — use curl to PUT each file part, then call complete_upload. For inline uploads, returns an immediate asset_id. If the host cannot execute shell commands to upload file parts, ask the user to upload at https://app.scenario.com and provide the asset_id. Examples: - "Upload this image" (with shell) -> get file_size with wc -c, omit data, pass file_size, then curl PUT each part, then complete_upload - "Upload a large video" -> same multipart flow: file_size, presigned URLs, curl, complete_upload - "Upload a tiny icon" (no shell, <100KB) -> pass data="<base64>" for single-step upload Don't use when: You already have a Scenario asset_id. Prefer reusing the existing asset_id in downstream tools instead.

Parameters