MiniMax H3 768p clips inside a $2 Agent Completion cap

MiniMax H3 at 768p costs $0.075 per second on Sume, so a $2.00 Agent Completion cap fits at most 26 seconds of footage; with the 5 to 15 second clip limit, the best split is one 15 s clip plus two 5 s clips for $1.875. The cap is a required field on every completion, so it is worth sizing it from the clip plan rather than guessing.

Clip plans against a $2.00 cap

minimax-h3 accepts 5 to 15 seconds per clip. Each row multiplies the seconds by $0.075.

Send the plan with the cap

An Agent Completion is POST /v1/agent/completions with exactly one of instruction or messages, and generation_spend_cap_usd. It returns 202 with an agrun_ receipt that you poll at its status_url.

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 two 5 second MiniMax H3 clips at 768p of a ceramic mug on a wooden table.", "generation_spend_cap_usd": 2}'

Limits and gotchas

The cap is the most you accept for the run, not a quote. Put the model, resolution and seconds in the instruction so the agent picks the plan you priced.

• generation_spend_cap_usd has no default; leaving it out is a 400 invalid_request.
• The only model value is sume-agent, and there is no streaming, so poll or use a run webhook.
• The H3 family has a separate faster variant; its price is not in this table.