A 20,000-character narration fits a $1.00 scheduled cap at $0.95
Sume TTS at $0.0475 per 1,000 characters prices 20,000 characters at $0.95, 5 cents under the $1.00 default cap of a schedule. What 21,000 does.

A 20,000-character narration costs $0.95 on Sume ($0.0475 per 1,000 characters), which fits under the $1.00 default cap of a scheduled run with $0.05 to spare. A 21,000-character script costs $0.9975, and 22,000 characters would reach $1.045, over the cap.
Script length against the default cap
The price is linear in characters, so the longest script under $1.00 is 21,052 characters.
| Characters | Rate per 1,000 | Total | Under $1.00 |
|---|---|---|---|
| 10,000 | $0.0475 | $0.475 | Yes |
| 20,000 | $0.0475 | $0.95 | Yes |
| 21,000 | $0.0475 | $0.9975 | Yes |
| 22,000 | $0.0475 | $1.045 | No |
Lower it for a test
A scheduled run only gets narration if the stored instructions ask for it. To test an API-triggered run cheaply, send a lower cap; the API takes the smaller of the request and the schedule cap.
curl -sS -X POST "https://api.sume.com/v1/actions/$ACTION_ID/runs" \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"generation_spend_cap_usd": 0.25}'Limits and gotchas
Nothing else in the run can cost money if the script is near the cap. Leave room for retries or keep the script shorter.
- A per-run cap can lower the schedule cap but never raise it.
0is rejected with a 400.- A skipped run, the default when one is already active, sends no webhook.
Sources
Related posts
More in Agents
- Unattended agent: stop or retry on Sume 402, 409, 429, 503?
An unattended Sume agent should stop on 402, fix on 400, retry 429 and 503 with the same idempotency key, and never reuse a key after a 409.
- Wan 3.0 clip lengths that fit a $1.00 scheduled run cap
A schedule without its own cap gets $1.00 per run. At Wan 3.0 rates that buys 16 s at 480p, 8 s at 720p or 4 s at 1080p; here is the table.
- Your agent calls generate_video, or Sume's agent does: two meters
With hosted MCP your model client runs the loop and you pay its provider; with an Agent Completion Sume's agent runs it and you set generation_spend_cap_usd.
- Planlock in front of Sume MCP: approve the plan, then the calls
Planlock is an MCP proxy that enforces a human-approved plan. Where it fits in front of Sume's hosted MCP, and which Sume gates still do work behind it.
Written by Sume