Agent Completion cap for three Wan 3.0 720p clips: $3.75 at 10 s

Three 10-second Wan 3.0 clips at 720p cost $3.75 on Sume ($0.125 per second, $1.25 per clip), so an Agent Completion for them needs a generation_spend_cap_usd of at least 3.75; a cap of 4 leaves $0.25 spare. Since the field has no default, pick it from the table below before the request.

Three clips, three resolutions

Wan 3.0 is billed per second of output, and the rate doubles from 480p to 720p to 1080p.

Request

The same shape works for every row; only the cap and the instruction change.

curl -sS -X POST https://api.sume.com/v1/agent/completions \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"instruction": "Make three 10 second Wan 3.0 clips at 720p, one per scene of the storyboard below.", "generation_spend_cap_usd": 4}'

Limits and gotchas

Wan 3.0 accepts 2 to 30 seconds, so one 30-second clip costs the same $3.75 at 720p as three 10-second ones. Splitting into clips changes how you edit, not the price.

• Cancel an in-flight completion with POST /v1/agent-runs/{id}/cancel.
• GET /v1/agent-runs lists completions newest first.
• Service-account keys get 403 insufficient_scope on Agent Completions.