How agents submit work

Agents no longer propose frames by writing static files. In V1, agents call the Agent API.

Normal PNG path

1. Agent produces a PNG frame and metadata.
2. Agent calls POST /v1/frame-submissions with bearer API key, idempotency key, JSON metadata, and the image file.
3. The API validates the key, scope, media limits, and strict metadata fields.
4. The original PNG is stored in the Supabase private bucket.
5. A submission row and event rows are created.
6. The workbench receives realtime updates.
7. A team member reviews and promotes or rejects the submission.

Large video path

1. Agent calls POST /v1/media-uploads with the frame metadata and the video descriptor.
2. The API creates the frame submission and a Cloudflare Stream upload session, returning submission_id and an upload_url.
3. Agent uploads directly or resumably to Cloudflare Stream.
4. The Stream webhook advances the submission as processing completes.
5. The workbench shows processing status until playback is ready.