Sume Action spend cap: 1 dollar default, per-run cap only lowers
A Sume Action carries a default spend cap of 1 dollar. A per-run cap can lower it but not raise it, so a heavy video job needs the cap changed on the Action.
The default spend cap on a Sume Action is 1 dollar. A per-run generation_spend_cap_usd can only go lower than the Action cap; it cannot raise it. If a scheduled run does video generation, a 1 dollar ceiling will stop it, so raise the cap on the Action itself in the dashboard, then use the per-run value to tighten it for cheap calls.
That is the opposite of a Format run, where the cap is yours to set per call up to 500.
Caps compared
| Surface | Default | Per-run override |
|---|---|---|
| Action | 1 dollar | Lower only |
| Format run | Format default, 400 dollars if never set | Up to 500, 0 rejected |
| Agent Completion | None; required in the request | Set per request |
Check before you schedule
Run the Action once through its API trigger if it has one, and read the usage record for that run before you turn the cron on.
Sources
Related posts
More in Agents
- Sume Scheduled has no MCP tool or CLI command: your options
Schedules are not exposed over Sume MCP or the CLI, and the API cannot create them. Author in the dashboard or ask the Agent in chat; run and monitor by API.
- Scheduled Sume runs: cron or API trigger is fixed at create
A Sume Action is either cron or api triggered, chosen at creation. How to author one, why you cannot create it over the public API, and how to run the api kind.
- VS Code Copilot automations on a schedule: Sume jobs and idempotency
VS Code automations can run agent tasks hourly, daily, weekly or on demand. Make each Sume create idempotent so a rerun resumes a job instead of paying twice.
- What can a $5 generation spend cap make? Clips, stills, captions
A $5 cap on an Agent Completion covers 16 five-second Wan 3.0 clips at 480p, or 50 nano-banana-2 stills, but not one Seedance 2.5 clip at 720p and 15 seconds.
Written by Sume