{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibxmuqexlyrjtiu4o42rbdwtu6c7mdxk26c7abdl7stayuejyw3l4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjtndi35ves2"
  },
  "path": "/t/model-status-uncertainty-in-modelslist-api/1379282#post_1",
  "publishedAt": "2026-04-19T08:03:05.000Z",
  "site": "https://community.openai.com",
  "textContent": "Problem:\n\nThe current /v1/models API returns all models (active, deprecated, preview, legacy) with no clear distinction.\n\nExample current response:\n\n{\n\n“id”: “gpt-4.5-preview”,\n\n“created”: 1690000000,\n\n“owned_by”: “openai”\n\n}\n\nIssue:\n\n- No way to know if a model is active or deprecated\n\n- Developers must manually filter using naming conventions\n\n- Leads to confusion and risk of using outdated models\n\nContext:\n\nOpenAI docs mention deprecations separately, but the API itself does not expose lifecycle info.\n\nSuggested improvement:\n\n{\n\n“id”: “gpt-5.2”,\n\n“lifecycle”: “active”, // active | deprecated | retired | preview\n\n“created”: 1690000000,\n\n“owned_by”: “openai”\n\n}\n\nImpact:\n\n- Cleaner developer experience\n\n- Safer production usage\n\n- Eliminates fragile string-based filtering\n\n- Aligns with standard API lifecycle practices\n\nCurrent workaround:\n\nDevelopers must maintain allow-lists or filter by name patterns (e.g. “preview”, “legacy”), which is brittle.\n\nAsk:\nCan we expose lifecycle metadata or a “recommended models” subset directly in the API?",
  "title": "Model status uncertainty in modelsList API"
}