Sonnet 5.5 vs GPT-6.1 Sol for video scripts: both $2 in, $10 out
Claude Sonnet 5.5 and GPT-6.1 Sol list the same $2 input and $10 output per million tokens (read 2026-10-05), so pick on fit, not price.

If a script writer step feeds a video agent, the LLM bill is rarely the large number, and the two newest mid-tier models list identical prices. Anthropic's models overview lists Claude Sonnet 5.5 (claude-sonnet-5-5) at $2 per million input tokens and $10 per million output tokens, with a 1M-token context window and 128K max output. OpenAI's models page lists GPT-6.1 Sol (gpt-6.1-sol) at $2 and $10 with a 1.05M context window and 128K max output (both read 2026-10-05).
| Claude Sonnet 5.5 | GPT-6.1 Sol | |
|---|---|---|
| API id | claude-sonnet-5-5 | gpt-6.1-sol |
| Input per 1M tokens | $2 | $2 |
| Output per 1M tokens | $10 | $10 |
| Context window | 1M tokens | 1.05M tokens |
| Max output | 128K tokens | 128K tokens |
What a script call costs
A 600-word voiceover script is roughly 800 output tokens. At $10 per million that is $0.008, under one cent, with the same figure on either model. Even with a 20,000-token brief as input ($0.04), the writing step stays far below one generated clip. The decision is therefore about whether the model follows your structure, not the rate card.
Where Sume's side differs
Sume's Agent Completions take an instruction or messages[] and require generation_spend_cap_usd, which bounds generation spend (clips, images, voice), not tokens. The Scheduled object carries a model field alongside its instructions, cron expression and cap. The docs do not list which LLMs the agent can use, so check the dashboard before you plan a model-by-model test.
Run the same brief through both for a week, keep the one whose scripts need fewer edits, and re-read both vendor pages first: prices and ids moved more than once this year.
Sources
Related posts
More in Agents
- Spend guard layers for an unattended Sume video agent, in order
Five layers cap a Sume agent that runs unattended: key scope, per-run cap, max_spend_usd and dry_run, generation admission, and the wallet. What each one stops.
- One Sume schedule on a clock and on call: api_trigger_enabled
A Sume cron schedule can also set api_trigger_enabled to accept API runs. trigger_type is fixed at create time, so choose once. Overlap defaults to skip.
- What a Sume MCP create result tells the agent to call next
A Sume MCP create result carries agent.next_step: jobs_wait with the job_id and timeout 50, plus poll_after_seconds 5. Follow it; do not resubmit.
- Agent says Sume MCP is down after one timeout: retry once, name it
One errored or timed-out Sume MCP call is just that call failing. Retry it once, report that tool's error, and never say the server is down.
Written by Sume