GPT-6.1 Sol structured outputs or a Sume Format output_schema?

GPT-6.1 Sol supports structured outputs and function calling in OpenAI's API. A Sume Format run adds media, a spend cap and a receipt. Pick by the job.

5 min readSume
All posts

Choose the model's structured outputs when the answer is text that fits in one request. Choose a Sume Format run when the job makes media or calls tools over several steps and you want a typed result plus a spend ceiling. OpenAI's GPT-6.1 Sol page lists structured outputs and function calling as supported features, so a plain extraction needs no run at all.

The unit of work

The difference is the unit of work. A model call returns tokens. A Format run is one agent turn in a sandbox: it can generate files, and the receipt lists artifacts, usage and output.

Model call or Format run (read 2026-10-05)
NeedModel structured outputsSume Format run
Typed text answerFitsWorks, but heavier
Generated video or imageNot the jobartifacts[] and primary_output_url
Spend ceilingYour own codegeneration_spend_cap_usd on the request
Retry safetyYour own codeIdempotency-Key header
Result shapeSchema you sendoutput_schema, filled_by, output_error

What a run adds

A run is asynchronous. It answers 202 with a receipt, and you read status_url or take one terminal webhook. See Calling a Format for the request fields.

Check the docs before you ship

Sume's limits and field names change faster than blog posts do. Read the linked docs pages for the current request fields before you ship, and send a dry_run or a low spend cap on your first real call.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume