Finalize an uploaded context
Finalize an uploaded context (create_context): completes a multipart upload server-side (no ETag bookkeeping) and verifies the declared sha256 against the uploaded bytes. Small contexts answer {status: "ready", size_bytes} directly; a multi-GiB verify outlives your call - you get {status: "finalizing"} and the work continues server-side (your timeout never cancels it): poll get_context until status=ready. Re-calling while finalizing is safe (reports progress, never restarts). If the detached work fails, get_context reports {status: "failed", error} - re-calling finalize_context then starts a fresh attempt. A checksum mismatch is reported so you re-upload and resubmit. A no-op once ready. A finalized context feeds submit_job (context_id) and get_context (a download url to land it on a node), and stays reusable for ~30 days.
Request
- Base URL: https://autoresearch.sfcompute.com
- URL: https://autoresearch.sfcompute.com/preview/contexts/{id}/finalize
- Auth: HTTP bearer
Path parameters
Context id from create_context (e.g. "ctx-5rq8d").
Query parameters
Act in this workspace (its slug). Omitted: the token's bound workspace, then the organization's default. Never ambient - there is no switch-workspace mutation on this door.
Response
The capability's JSON result.
Changes
No recorded changes to this operation across all 1 revision of this API.