Summary
The r1-1776 model was officially retired by Perplexity on August 1, 2025, replaced by sonar-reasoning-pro. The catalog entry at line ~2925 has no deprecated or deprecation_date fields. Without these fields, markModelsPastDeprecationDate() in packages/proxy/schema/models.ts will not auto-flag it as deprecated, and the model will continue to appear in the UI despite being unavailable.
Affected Model
| Model ID |
Gap |
Line |
r1-1776 |
Missing deprecated: true and deprecation_date |
~2925 |
Current catalog entry:
"r1-1776": {
"format": "openai",
"flavor": "chat",
"input_cost_per_mil_tokens": 2,
"output_cost_per_mil_tokens": 8,
"displayName": "R1 1776"
}
Verification
Cross-source confirmation: The Perplexity changelog explicitly states r1-1776 was retired on August 1, 2025. The current models documentation page does not list r1-1776 among active models, confirming it is no longer available.
The sonar-reasoning model in the catalog already has correct deprecation markers ("deprecated": true, "deprecation_date": "2025-12-15"), so this pattern is established for Perplexity models.
Local files inspected
packages/proxy/schema/model_list.json — r1-1776 at line ~2925 has no deprecated or deprecation_date fields
packages/proxy/schema/index.ts — mapped to ["perplexity"] at line 242
packages/proxy/schema/models.ts — markModelsPastDeprecationDate() at line 217 requires deprecation_date per entry
Proposed change
"r1-1776": {
"format": "openai",
"flavor": "chat",
"input_cost_per_mil_tokens": 2,
"output_cost_per_mil_tokens": 8,
"displayName": "R1 1776",
"deprecated": true,
"deprecation_date": "2025-08-01"
}
{
"kind": "deprecation",
"provider": "perplexity",
"models": ["r1-1776"],
"status": "deprecated",
"model_specs": {
"r1-1776": {
"deprecated": true,
"deprecation_date": "2025-08-01"
}
},
"source_urls": [
"https://docs.perplexity.ai/changelog",
"https://docs.perplexity.ai/docs/agent-api/models"
]
}
Summary
The
r1-1776model was officially retired by Perplexity on August 1, 2025, replaced bysonar-reasoning-pro. The catalog entry at line ~2925 has nodeprecatedordeprecation_datefields. Without these fields,markModelsPastDeprecationDate()inpackages/proxy/schema/models.tswill not auto-flag it as deprecated, and the model will continue to appear in the UI despite being unavailable.Affected Model
r1-1776deprecated: trueanddeprecation_dateCurrent catalog entry:
Verification
Cross-source confirmation: The Perplexity changelog explicitly states r1-1776 was retired on August 1, 2025. The current models documentation page does not list r1-1776 among active models, confirming it is no longer available.
The
sonar-reasoningmodel in the catalog already has correct deprecation markers ("deprecated": true, "deprecation_date": "2025-12-15"), so this pattern is established for Perplexity models.Local files inspected
packages/proxy/schema/model_list.json—r1-1776at line ~2925 has nodeprecatedordeprecation_datefieldspackages/proxy/schema/index.ts— mapped to["perplexity"]at line 242packages/proxy/schema/models.ts—markModelsPastDeprecationDate()at line 217 requiresdeprecation_dateper entryProposed change
{ "kind": "deprecation", "provider": "perplexity", "models": ["r1-1776"], "status": "deprecated", "model_specs": { "r1-1776": { "deprecated": true, "deprecation_date": "2025-08-01" } }, "source_urls": [ "https://docs.perplexity.ai/changelog", "https://docs.perplexity.ai/docs/agent-api/models" ] }