OpenAI offers both a plain model name (an alias, such as a model's short identifier) and a dated snapshot identifier for the same underlying model family. According to OpenAI's documentation, how do these two kinds of identifiers differ, and why might a production application choose one over the other?
- a dated snapshot identifier automatically updates over time to point at the newest underlying model, while a plain alias always stays pinned to whichever exact version existed when the application first started calling it
- a plain alias name is a moving pointer that OpenAI can repoint to a newer underlying snapshot over time, while a dated snapshot identifier stays fixed to one specific model version indefinitely; production applications often pin to a dated snapshot specifically to avoid the model's behavior changing underneath them without warning
- aliases and dated snapshots are billed at different per-token prices for otherwise identical model capability, with the alias name always priced lower than any dated snapshot of the same model
- dated snapshot identifiers are available only to enterprise customers under a custom contract, while every other developer can only ever call the plain alias name
Why B? And why not the others?
Correct answer: B. a plain alias name is a moving pointer that OpenAI can repoint to a newer underlying snapshot over time, while a dated snapshot identifier stays fixed to one specific model version indefinitely; production applications often pin to a dated snapshot specifically to avoid the model's behavior changing underneath them without warning
OpenAI documents plain model names as aliases that can be repointed to a newer underlying snapshot as the model family is updated, while a dated snapshot identifier, which includes a specific release date in its name, stays fixed to that one version indefinitely; this is why production applications that need stable, reproducible behavior commonly pin to a dated snapshot rather than the alias, so an unannounced model update does not silently change outputs, latency, or capabilities the application depends on. The option reversing which identifier is the moving one gets the mechanism backwards relative to what is documented. The option inventing a pricing difference between an alias and a dated snapshot of the same underlying model is not supported by documented pricing, which is tied to the model family and capability tier rather than to whether the identifier is dated. The option restricting dated snapshots to enterprise contracts is wrong because dated snapshots are documented as available to any developer calling the API, not gated behind a special contract tier.
Source: OpenAI, Models documentation, https://developers.openai.com/api/docs/models