Mirage Tesseract needs local files; Sume needs public HTTPS URLs

Mirage Tesseract works on local files, while Sume avatar inputs have to be public HTTPS URLs, so moving footage between them takes one hosting step. The Mirage announcement says the engine needs an agent environment that can access local files and run local tools. Sume's media input rules reject localhost, private-network, signed or private URLs and mismatched content types before a job is submitted.

Direction one: local to Sume

If Tesseract produced a product image or a clip you want Sume to use, it must be reachable at a public HTTPS address with a correct content type. A file path on your disk will not work, and neither will a time-limited signed URL.

Check the content type matches the file. A .png served as text/html is rejected.

Direction two: Sume to local

Sume outputs are mirrored to media.sume.com URLs. Download the result file to the folder your local engine reads, then continue editing there. Fetch the URL from the job result at /v1/jobs/:id/result.

A simple loop

Keep the script in text, render the presenter in Sume, download the MP4, then do compositing locally. Re-render only the avatar clip when the words change, and leave the local project untouched.

If your agent lives somewhere with no disk, skip the local step and use the hosted result URL directly.