I want to confirm when the model alias started pointing to a specific snapshot.
For example, ‘gpt-4o’ currently points to ‘gpt-4o-2024-08-06’, and I want to know when that started.
How about right here?
model_alias = {
"gpt-3.5-turbo" :"gpt-3.5-turbo-0125",
"gpt-4-turbo" :"gpt-4-turbo-2024-04-09",
"gpt-4o" :"gpt-4o-2024-08-06",
"gpt-4" :"gpt-4-0613",
"gpt-4-turbo-preview" :"gpt-4-0125-preview",
"gpt-4o-audio-preview" :"gpt-4o-audio-preview-2025-06-03",
"gpt-4o-mini" :"gpt-4o-mini-2024-07-18",
"gpt-4o-mini-audio-preview" :"gpt-4o-mini-audio-preview-2024-12-17",
"gpt-4o-mini-search-preview" :"gpt-4o-mini-search-preview-2025-03-11",
"gpt-4o-search-preview" :"gpt-4o-search-preview-2025-03-11",
"gpt-4.1" :"gpt-4.1-2025-04-14",
"gpt-4.1-mini" :"gpt-4.1-mini-2025-04-14",
"gpt-4.1-nano" :"gpt-4.1-nano-2025-04-14",
"o1-mini" :"o1-mini-2024-09-12",
"o1" :"o1-2024-12-17",
"o1-pro" :"o1-pro-2025-03-19",
"o3-deep-research" :"o3-deep-research-2025-06-26",
"o3-mini" :"o3-mini-2025-01-31",
"o4-mini-deep-research" :"o4-mini-deep-research-2025-06-26",
"gpt-5" :"gpt-5-2025-08-07",
"gpt-5-mini" :"gpt-5-mini-2025-08-07",
"gpt-5-nano" :"gpt-5-nano-2025-08-07",
"o3" :"o3-2025-04-16",
"o3-pro" :"o3-pro-2025-06-10",
"o4-mini" :"o4-mini-2025-04-16",
#"gpt-3.5-turbo-instruct" :"gpt-3.5-turbo-instruct-0914",
}
then, just in case you need something to apply that alias map against…
model_dict = {
# === table of model capabilities | context| max | reas- | Tier rate limits TPM (limits even 1 request)
# model | window|tokens| oning | t1 | t2 | t3 | t4 | t5 |
"gpt-3.5-turbo-0125" :( 16385, 4096, False, 200000,2000000, 800000,10000000, 50000000),
"gpt-3.5-turbo-1106" :( 16385, 4096, False, 200000,2000000, 800000,10000000, 50000000),
"gpt-4-0125-preview" :( 128000, 4096, False, 30000, 450000, 600000, 800000, 2000000),
"gpt-4-1106-preview" :( 128000, 4096, False, 30000, 450000, 600000, 800000, 2000000),
"gpt-4-turbo" :( 128000, 4096, False, 30000, 450000, 600000, 800000, 2000000),
"gpt-4-turbo-2024-04-09" :( 128000, 4096, False, 30000, 450000, 600000, 800000, 2000000),
"gpt-4o-2024-05-13" :( 128000, 4096, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-4-0314" :( 8192, 8192, False, 10000, 40000, 80000, 300000, 1000000),
"gpt-4-0613" :( 8192, 8192, False, 10000, 40000, 80000, 300000, 1000000),
"chatgpt-4o-latest" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-3.5-turbo-16k" :( 16385, 4096, False, 200000,2000000, 800000,10000000, 50000000), # jerks locked the output lower
"gpt-4o-2024-08-06" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-4o-2024-11-20" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-4o-audio-preview-2024-12-17" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-4o-audio-preview-2025-06-03" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000), # wrong: org is defaults on 2025-06-03
"gpt-4o-mini-2024-07-18" :( 128000, 16384, False, 200000,2000000,4000000,10000000,150000000),
"gpt-4o-mini-audio-preview-2024-12-17" :( 128000, 16384, False, 200000,2000000,4000000,10000000,150000000),
"gpt-4o-mini-search-preview-2025-03-11":( 128000, 16384, False, 200000,2000000,4000000,10000000,150000000), # wrong: t5 org is 3M not 150M
"gpt-4o-search-preview-2025-03-11" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 30000000),
"gpt-5-chat-latest" :( 128000, 16384, False, 30000, 450000, 800000, 2000000, 40000000), # max in: 128k - true
"gpt-4.1-2025-04-14" :(1047576, 32768, False, 30000, 450000, 800000, 2000000, 30000000), # gpt 4.1 models also have lower "long context" limits
"gpt-4.1-mini-2025-04-14" :(1047576, 32768, False, 200000,2000000,4000000,10000000,150000000),
"gpt-4.1-nano-2025-04-14" :(1047576, 32768, False, 200000,2000000,4000000,10000000,150000000),
"o1-2024-12-17" :( 200000,100000, True , 30000, 450000, 800000, 2000000, 30000000),
"o1-mini-2024-09-12" :( 128000, 65536, True , 200000,2000000,4000000,10000000,150000000), # shutdown 2025-10-27
"o1-pro-2025-03-19" :( 200000,100000, True , 30000, 450000, 800000, 2000000, 30000000),
"o3-deep-research-2025-06-26" :( 200000,100000, True , 200000, 450000, 800000, 2000000, 30000000),
"o3-2025-04-16" :( 200000,100000, True , 30000, 450000, 800000, 2000000, 30000000),
"o3-mini-2025-01-31" :( 200000,100000, True , 100000, 200000,4000000,10000000,150000000),
"o3-pro-2025-06-10" :( 200000,100000, True , 30000, 450000, 800000, 2000000, 30000000),
"o4-mini-2025-04-16" :( 200000,100000, True , 200000,2000000,4000000,10000000,150000000),
"o4-mini-deep-research-2025-06-26" :( 200000,100000, True , 200000,2000000,4000000,10000000,150000000),
"gpt-5-2025-08-07" :( 400000,128000, True , 30000, 450000, 800000, 2000000, 40000000), # max in: 272000 for gpt-5 models
"gpt-5-mini-2025-08-07" :( 400000,128000, True , 200000,2000000,4000000,10000000,180000000),
"gpt-5-nano-2025-08-07" :( 400000,128000, True , 200000,2000000,4000000,10000000,180000000),
}
print(f"Extending {len(model_dict.keys())} models with {len(model_alias.keys())} aliases")
# Extend model_dict with aliases
for alias, target in model_alias.items():
if target not in model_dict:
raise KeyError(f"Alias target '{target}' not found in model_dict")
model_dict[alias] = model_dict[target]
1 Like
Thanks for your immediate reply.
But I wanna know WHEN the alias direction changed.
Does this include the information?
Some are done in sneaky stealth, like the audio models being repointed.
gpt-4o, you line of inquiry, was moved forward from 2024-05-13 about a month after the new model’s release. It likely hasn’t advanced further forward because 2024-11-20 is more chatgpt-like, and also doesn’t support predictions, which an alias repointing could break.
You’ll notice the vast majority only have one possible destination.
1 Like