Deprecate operating_point in favor of model where applicable

[mnemitz]

Summary

This PR updates the batch API spec and docs to reflect the deprecation of operating_point in favour of the new model field.

Batch API spec (spec/batch.yaml)

• Adds a dedicated model field to TranscriptionConfig with values standard and enhanced (previously called operating points)
• Marks operating_point as deprecated with a note to use model instead; the field is retained for backward compatibility
• Adds a dedicated type for the model field and updates its description

Documentation (MDX files)

• Updates all JSON code examples across speech-to-text, realtime, and integration docs to use "model": "enhanced" instead of "operating_point": "enhanced"
• Renames the "Operating points" section in the languages reference to "Models" (anchor #operating-points preserved to avoid breaking existing links)
• Updates prose throughout to use "model" / "enhanced model" / "standard model" rather than "operating point" terminology

Not in scope for this PR

• Third-party integration SDK docs (pipecat, livekit) — parameter names are controlled by those libraries
• Python RT SDK and Voice SDK code examples — SDK not yet updated (will update next)
• Container/virtual appliance deployment docs — separate config surface

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 3, 2026 4:37pm