confirm_upload

pro.aicut/aicut · Verify this server

Checks the file that was uploaded to an `upload_media` target and makes it usable. Returns the media `url` to pass to other tools, the file's size, its `kind` (`video` or `image`), its measured `width` and `height`, and - for a video only - its `duration_seconds`. WHEN: immediately after the bytes moved - either the curl command from `upload_media` printed a 2xx status, or the user says they finished on the `browser_upload_url` page. There is no other time to call it. WHAT IT CHECKS, and why a failure here is worth reading rather than retrying blindly: the file's actual CONTENTS must match the type that was declared, and the media must be MEASURABLE - aicut reads a clip's length and size from its container, and a picture's dimensions from its header, and that measurement is what every later transform is priced and charged from. A file that fails either check is rejected and deleted, and nothing has been charged at any point. Re-encoding to MP4 (a clip) or to PNG or JPEG (a picture) fixes the measurement case; uploading the file you meant to upload fixes the other. IF IT SAYS NOTHING HAS BEEN UPLOADED YET: the bytes did not land. On the curl route, read the body it printed - it carries S3's own reason (a size over the declared `bytes` comes back as `EntityTooLarge`), and a bare `000` with no body means your environment could not reach the storage host at all, so switch to `browser_upload_url` rather than retrying. On the browser route, the user has most likely not finished yet. DO NOT CALL `upload_media` AGAIN. The target from the first call is still live for its whole 15 minutes, a second call inside that window returns the same one anyway, and re-stating the link is what fills a conversation with base64. Say in one line that you are waiting, without the link, and call this again when they say they are done. If the upload really did report success, the CDN may still be serving a cached miss from a confirm you made too early; wait a few seconds and call this once more before concluding it failed. COSTS NO TOKENS. Safe to call again on the same id - it re-checks the same file and answers the same thing. AFTER THIS: the `url` behaves exactly like a url from one of the user's own generations, and ONE UPLOADED FILE WORKS EVERYWHERE ITS KIND IS TAKEN - there is no second upload for a second tool. A confirmed VIDEO goes in as `source_video` to `upscale_video` or `extend_video`, as `reference_video` to `motion_control`, or in `reference_videos` on `generate_video`. A confirmed IMAGE goes in as `source_image` to `upscale_image`, as `character_image` to `generate_lipsync` or `motion_control`, as a start or end frame or a reference image on `generate_video`, and as an input image on `generate_image`. No web app step, and no second copy - it is already on the account. OUTPUT: this returns JSON for you to read. When you report back to the user, give them the media URL plus a one-line summary. Do not paste the raw JSON, job ids, or internal field names into the conversation.