Security.RunDevelopers
v1 PreviewOpenAPI ↗
API & MCP reference/Upload files for a run
HOW-TO GUIDES

Upload files for a run

Turn local files into artifact IDs, then choose their paths inside the tool.

1. Upload and seal a file

Save the example as upload_file.py, place sample.bin next to it, and run it with your API URL and token set. It calculates the size and SHA-256, declares the upload, sends the bytes, and seals the artifact. Save the printed artifact ID.

2. Choose a name for the tool

Put the returned ID in invocation.files, for example {"path":"samples/input.bin","artifact_id":"artifact_..."}. The tool sees that file under /tmp/work/samples/input.bin. Use samples/input.bin in its arguments.

3. Add the other inputs

Repeat for each rule, source file or configuration file. You can upload once and reuse a sealed artifact in multiple runs. A directory is represented by named files such as src/app.py and src/helpers.py; uploading a ZIP does not automatically extract it.

Empty files and executable scripts

Use empty_files for empty inputs and directories for empty directories. Set executable: true on a staged script if the tool needs to execute it.

If an upload fails

A checksum mismatch usually means the declared hash or size came from different bytes. Recalculate both and create a new upload. Sealing must succeed before an artifact can be submitted to a run.

Inputs are limited to 8 MiB per artifact and 32 MiB total per run, including stdin. See Limits and environments for the complete limits.

Search documentation, capabilities and native tools.

Copy this page

Your browser couldn’t copy automatically. Copy the selected Markdown below.