开发者反思API访问风险：为何需要备用AI订阅
英文摘要
A V2EX user reported that a friend purchased a GLM annual subscription as a backup while primarily using OpenAI's Codex and ChatGPT. After recent policy-driven access restrictions (possible reference to “Fable” or similar incidents), that backup proved strategically valuable. The user warns against sole dependence on providers like OpenAI or Anthropic, whose policies can cut off access without notice, and plans to similarly secure a GLM annual plan. The post highlights growing community concerns over API dependency and the importance of having fallback options.
中文摘要
一位V2EX用户提到，朋友在主要使用OpenAI的Codex和ChatGPT的同时，购买了GLM年度订阅作为备用。在近期政策驱动的访问限制（可能涉及“Fable”等事件）后，这一备用方案显现出战略价值。发帖者警告不应完全依赖OpenAI或Anthropic等随时可能因政策切断访问的供应商，并计划办理GLM年度套餐。该帖反映出社区对API依赖风险的担忧以及保留备用方案的重要性。
关键要点
A developer's friend maintained a backup GLM annual subscription while using OpenAI Codex and ChatGPT.
一位开发者的朋友在使用 OpenAI Codex 和 ChatGPT 的同时，保留了 GLM 年度订阅作为备用。
Recent policy-driven access restrictions made the backup subscription strategically valuable.
近期的政策驱动访问限制使得这个备用订阅具有战略价值。
The poster advises against sole dependence on API providers like OpenAI or Anthropic and plans to secure a GLM backup.
发帖者建议不要完全依赖 OpenAI 或 Anthropic 等 API 提供商，并计划办理 GLM 年度备用套餐。