CLI
The CLI is installed with the Python SDK. See Authentication for environment configuration. Every API command uses the configured deployment’s/v1 routes. After logging
in, use sutro quotas to verify that the deployment can reach Batch.
Resumable S3 batches
Configure deployment credentials withsutro login or environment variables,
and configure local AWS credentials. On macOS or Linux, run:
results.parquet.sutro.json and partial-download files. The
receipt preserves the submission key and job ID; the output path also locates
that receipt. To change destination or recover on another machine, use:
jobs resume needs deployment credentials but no source AWS credentials.
Ctrl-C and timeout stop local watching without cancelling remote work.
Failed or partial jobs stop without replacement submissions or partial output.
AWS credentials stay local; the CLI pins the object’s version, ETag and size
before signing its GET URL. Unversioned objects must remain unchanged until
ingestion finishes. JSONL uses one UTF-8 object per nonblank line, no duplicate
keys and at most 4 MiB per line. Directories, globs and compressed CSV/JSONL are
unsupported. The command requires macOS or Linux.
Receipts bind the deployment and authenticated owner; same-owner key rotation
can resume. An older receipt with no owner ID and no visible reservation stops
without posting. Keep the original owner’s key or use a known job ID.
Output uses SDK result conventions: representable JSON objects expand into
columns, nested values remain nested, and IDs/confidence are preserved.
Otherwise output remains
inference_result. Use --no-unpack-json for field
collisions. For Python, use the existing
batch_run_function()
and job methods.
Result options
--save-format accepts parquet or csv and defaults to parquet. Without
--save, results print to the terminal.
sutro set-base-url remains as a hidden deprecated alias for
sutro set-api-url.