# 3D Reconstruction End-to-End Flow

Follow a batch of 2:1 panoramas or 1:1 pinhole images through Argus reconstruction and output retrieval.

Canonical: https://developer.realsee.ai/docs/argus/process
Source: https://developer.realsee.ai/docs/argus/process.md
Language: en

Choose one input type for each reconstruction batch:

- Multiple 2:1 equirectangular panoramas.
- Multiple 1:1 pinhole images.

Keep that type for the whole batch.

The reconstruction workflow has three stages:

1. **File token and ZIP upload** — call `GET /open/v1/argus/file/token`, then upload one ZIP containing the selected images. Keep gateway tokens and upload-session creation on your backend.
2. **Task submit** — call `POST /open/v1/argus/task/submit` with the uploaded ZIP's full object path in `private_cos_keys` and a nonempty `title`. Keep the returned `task_code`. Submission is not idempotent; confirm an uncertain outcome before submitting again.
3. **Task info and output** — query `GET /open/v1/argus/task/info?task_code=...`. When `data.status` is `2`, download the temporary `output_url` before `expiration_timestamp`, then validate `output.json` and the referenced files.

The gateway task status and the algorithm's output-manifest status are separate. [Outputs and Result Handling](https://developer.realsee.ai/docs/argus/outputs) explains `success`, `partial`, and `error` inside the downloaded result.

Use the current [Quickstart](https://developer.realsee.ai/docs/argus/quickstart) and [API Reference](https://developer.realsee.ai/docs/argus/reference) for batch upload details and request fields.