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
- 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.
- What is an AI video agent? One that talks, or one that makes
An AI video agent can mean a live on-camera persona like a Tavus PAL, or an agent that makes videos for you. Which one Sume is, and how to call it from code.
- Run the Sume video agent from your backend with Agent Completions
POST /v1/agent/completions runs the same agent as the Sume Agents chat, with tools and media generation, and returns an async run receipt you poll or webhook.
- Safe automation for AI agents that call paid APIs
Keep agents read-only by default, keep secrets out of logs, and on hosted MCP send an idempotency_key, preview with dry_run, and cap with max_spend_usd.
Written by Sume