Skip to main content

​
Protocols and model capabilities

The four generation protocols support adapters for text, multimodal input, reasoning, structured output, and client-side tools. Availability depends on model, channel, and upstream support. Cross-protocol conversion uses an allow loss policy and records conversion losses: parameters may not be semantically equivalent. System One stays separate from chat. Hosted tools and standalone audio/video services require native upstream support. Protocol declarations alone do not guarantee them. Current restrictions include conversation, prompt, file_ids, vector_store_ids, container, and item/file references not owned by the current user.

​
State and regions

See Responses for storage, continuation, background execution, and cancellation. store=true defaults to 30-day retention; store=false keeps no platform content copy. Existing responses bind to the user, original account, credentials, and region. Switching regions does not bypass access rules.

​
Sizes and lifetimes

These values follow the current compatibility matrix. Stricter model, channel, or deployment limits still apply.

​
Billing and retries

Generation is settled from actual usage, compact is metered, and token counting has no generation charge. Cancellation, errors, and disconnection do not imply no execution or no usage. Unknown cost requires reconciliation, not an assumption of zero. Disable client retries and avoid replaying commands with uncertain execution. Use the console for current prices and model capabilities. Balance, key permissions, budgets, and healthy routes jointly determine admission.