Agents
The Sume video agent from code: Agent Completions, scheduled runs, MCP tools and timeouts, programmatic tool calling, and guardrails for paid APIs.
Start with What is a video agent? How Sume defines and runs one
Pro key: 300 writes and 12,000 reads a minute for an agent on Sume MCP
On Sume Pro, each key gets 300 writes and 12,000 reads per minute. An agent polling 20 jobs every 5 s uses 240 reads, 2 percent of the read budget.
A Sume image job at 50 seconds: slow, queued, or stuck?
Sume's docs say an image still running after a 50 s jobs_wait is usually stuck, not slow. Check queued vs processing and events first; never submit twice.
Old prompt says video-router_create? Sume now takes generate_video
Sume retired the hosted MCP tool name video-router_create for generate_video and maps dots to underscores. Update the prompt, then check tools_list.
dry_run or generation_admission_preview first for 12 Sume clips?
Use dry_run on a paid call for its estimate, and generation_admission_preview before a burst of 12 clips to check balance and queue room. Neither submits a job.
After generate_image on sume/auto, why can't the agent name the model?
Sume never discloses which family ran for sume/auto: job.model stays sume/auto and the model list omits it. To name a model, pin an id from image-models_list.
MCP wants a human in the loop: Sume gates for unattended agents
MCP says a human SHOULD be able to deny tool calls. For unattended agents, Sume adds scopes, idempotency keys and a required Agent Completions cap.
Auditing agent tool calls: MCP log advice, Sume script_run journal
The MCP spec tells clients to log tool usage for audit. For Sume's script_run, the response includes a calls[] journal and child jobs[] to use with jobs_wait.
Build a run status chip from the Format events phase timeline
Sume has no SSE stream for Format runs. Poll status_url and events_url to show queued, preparing, running and finalizing in your UI without faking progress.
A video agent run takes 15 to 30 minutes: design the waiting
Long-form video from an agent is minutes of work, not seconds. Email-me-when-ready, saved drafts and honest limits for a Sume Format run in your product.
Scheduled or Format API: does the clock or your user start the run?
A Sume Scheduled run fires on a cron; a Format run fires when your backend calls it. Same agent, same receipt, new trigger. How to choose without dupes.
Three ways to run the Sume video agent from code
Format runs, Scheduled runs and Agent Completions all start the same Sume agent. Pick by how often your task changes, then read the receipt the same way.
Agent Completion cost: cap, billable_amount_usd_micros, or usage?
Where to read what an Agent Completion cost: the required spend cap, the receipt's usage.billable_amount_usd_micros, and GET /v1/usage as the billing record.
Claude Code routine artifacts: link Sume media, don't paste it
Claude Code 2.1.292 lets Scheduled and Run now routines publish a private artifact without approval. Hand off Sume results as durable media.sume.com links.
Claude Code scheduled task never fired? Compare with a Sume cron run
Claude Code 2.1.292 fixed scheduled tasks that never fired after /resume, /branch or /clear. A Sume schedule runs on Sume's clock, so check it separately.
Codex keeps your computer on reconnect: find Sume jobs first
Codex CLI 0.161.0 keeps a new task on the selected computer while it reconnects or is offline. After a gap, list Sume jobs before you resubmit any paid call.
Mistral Large 4 preview: Sume's agent model field takes one value
Mistral Large 4 is reported in preview. Sume lists no Mistral Large id; Agent Completions accepts only sume-agent. What to send instead, and what it bills.
One webhook handler for Sume agent, Format and schedule runs
A single receiver can handle all three Sume run types: verify the HMAC over timestamp.body, dedupe on request_id, and branch on outcome (ok, degraded, error).
Run a weekly short video series on autopilot with a Sume schedule
A weekly short-video series needs a schedule with a cron expression, an IANA timezone and a spend cap, plus an optional API trigger. How to set it up on Sume.
Stop an AI video agent overspending: the four Sume spend gates
An unattended Sume agent can only spend what four gates allow: the wallet, a per-run cap, a schedule ceiling, and a Format cap. Values and failure codes inside.
Polling a Sume agent run: next_action values and backoff
Poll Sume runs by branching on next_action (poll_status, retry_later, none), using status_url and result_url, backing off on 429 and 503.
Nightly UGC ad job: Agent Completion, Format run or schedule?
Pick the Sume surface for a nightly UGC ad job: Format run when inputs change, schedule when only the clock starts it, Agent Completion for one-off tasks.
Get a structured ad pack back from one Sume Agent Completion
Bind an output_schema to a Sume Agent Completion to get hook, caption, CTA and a video URL as named fields, with the strict-subset rules and failure modes.
Codex 0.160.0 resumes queued messages after reconnect: Sume key rule
Codex 0.160.0 resumes unsent queued messages after a reconnect without duplicates. A paid Sume call still needs its own idempotency_key to be safe.
Claude Code 2.1.287 tool heartbeats and Sume jobs_wait slices
Claude Code 2.1.287 fixed tool heartbeats not reaching SDK hosts during a stalled response stream. Sume's jobs_wait holds up to 55 s, so heartbeats matter.
script_run or bulk runs: where to fan out 20 ad variants
script_run fans out three or more Sume tool calls inside one 55-second request; bulk runs queue up to 100 Format runs for hours. Limits and a rule of thumb.
Cursor iOS remote control for local agents: keep paid Sume calls safe
Cursor can now show and answer local agents from its iOS app. If one holds Sume MCP, grant read-only, send dry_run first, and cap max_spend_usd.
Agent Completion plans the season; a Format bulk queue renders it
One Agent Completion drafts episode beats as JSON; each beat becomes an item in a Format bulk run. Spend caps at both steps.
Let a video agent read before it spends: MCP OAuth read, then write
Hosted MCP OAuth gives mcp:read by default and mcp:write by a consent toggle. Let an agent plan with reads, then enable write for paid calls.
Agent Completion 400: generation_spend_cap_usd has no default
Your POST to /v1/agent/completions returns 400? generation_spend_cap_usd is required and has no default. Add it, and pick a number from a real run.
Lower the spend cap for one scheduled Sume run: overrides only go down
A per-run generation_spend_cap_usd on a scheduled run is clamped to the schedule's own cap. You can lower it for one run but never raise it. How it works.
Captions drift after cutting pauses: burn them on the final render
Cut pauses first, then caption. Word times from the original clip no longer match once silence is gone. Run Sume video-captions on the trimmed render.
Trim pauses from ten clips: inspect segments, then one timeline render
Rough-cut apps trim pauses in their own editor. For a batch by API, inspect each clip for sentence segments, keep the speech, and render one timeline.
Create a Sume schedule by API? Dashboard first, then trigger by API
The Sume API cannot create or edit schedules. Create it in the dashboard with a cron or an api trigger, then call it from code. What each trigger type means.
Sume scheduled run returned skipped: detect previous_run_active
A Sume scheduled run that overlaps another returns 200 with status skipped, not an error. Check skip_reason in code, and choose reject if a drop must be loud.
Cut a video to 15 seconds for Reddit Engaged Video Views
Reddit began a 15-second Engaged Video Views beta in September. Cut any hosted clip to 15 seconds with Sume video-trim for a flat $0.02, exact or keyframe.
Keyframe or exact video trim for pause cuts: read actual_start_seconds
Exact trim cuts where you say; keyframe trim is faster but snaps to a keyframe. For pause cuts that decides whether words get clipped. How to choose and check.
Guardrails for an agent calling paid APIs: key, cap, and what to log
An agent calling a paid media API needs three habits: an idempotency key on each write, a spend cap per run, and logs that hold ids, never signed URLs or keys.
Render a Short from an agent: hosted MCP tool order
Which Sume hosted MCP tools an agent calls, in order, to import, inspect, cut and render a vertical Short, with idempotency_key rules and what stays on REST.
Weekly video: Agent Completion, Format or schedule on Sume?
A weekly video fits a Format or a schedule, not a fresh Agent Completion each time. How to choose among the three Sume surfaces for a recurring job.
assets_download_url MCP tool: a short-lived link for an uploaded asset
The hosted MCP tool assets_download_url returns a short-lived signed URL for a first-party asset. Use it only when asked, and never echo the URL in a report.
Scheduled run 400 because the instructions are empty: where to fix it
A Sume schedule with empty instructions can not run. The API run request returns 400 invalid_request, and the text can only be edited in the dashboard.
Did my Sume cron schedule fire? Read last_run_at and next_run_at
GET /v1/actions/{id} returns last_run_at and cron.next_run_at. Compare them with the run list to see if a schedule fired, without opening the dashboard.
Sume schedule slug rules: 2-64 characters, and runs is reserved
A Sume schedule slug is lowercase alphanumerics with single hyphens, 2 to 64 characters, unique in your account. The word runs is reserved. See the vanity path.
Scheduled Sume run missing from /v1/jobs: it is not a job
A schedule run is not a generation job, so it never appears in /v1/jobs and jobs_wait cannot wait on it. Read it from /v1/action-runs/{run_id} instead.
Why Sume's scheduled-run API does not return instructions text
The public scheduled-run shape omits the instructions text. Read and edit it in the dashboard; schedules have no MCP tool or write endpoint.
Skipped Sume scheduled run: no webhook, read the create response
A skipped or canceled Sume run sends no webhook. For api-trigger, on_active_run=skip is the default, so check the create response, not just your webhook inbox.
Agent Completions input: JSON data the agent reads from a file
Send caller data in input, not in instruction. Sume writes it to /workspace/inputs/sume-action-input.json and tells the agent to read it as data. curl sample.
Agent Completions request limits: 100,000 characters, 50 messages
The Sume Agent Completions schema caps instruction at 100,000 characters, messages at 50, and images at 30. Know where each limit is enforced before you send.