NodeBB

<p>Ayon sa pinakabagong mga panuntunan sa billing ng OpenAI, gumagamit ang mga modelong gaya ng GPT-5.6 Sol ng tiered pricing para sa mga request na may napakahabang context.</p><p>Kapag lumampas sa 272K tokens ang context ng isang request, maaaring singilin ang input, cache read, at output ayon sa mas mataas na tier ng presyo. Galing ang panuntunang ito sa opisyal na pricing ng OpenAI; hindi ito pansamantalang dagdag-singil o maling billing ng AI-ROUTER.</p><p></p><p>Halimbawa, gamit ang standard na presyo ng GPT-5.6 Sol:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Item Sa loob ng 272K Lampas sa 272K</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Input $5 / 1M tokens $10 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Cache read $0.50 / 1M tokens $1 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Output $30 / 1M tokens $45 / 1M tokens</code></pre><p></p><p>Ang aktuwal na bayarin ay kakalkulahin pa rin batay sa partikular na grupo, account multiplier, at iba pang configuration ng billing.</p><p></p><p>Ang paglitaw ng x2 flag sa usage records ay nangangahulugang na-trigger ng request na ito ang tiered billing para sa long context. Pangunahing ipinapahiwatig ng flag na pumasok ang input/cache read sa mas mataas na tier; hindi nito ibig sabihin na basta na lang nadoble ang lahat ng bayarin para sa buong request. Maaaring gumamit ang output ng ibang tier multiplier.</p><p></p><p><strong> ## Paano Maiiwasang Ma-trigger ang Tiered Billing</strong></p><p>Kung hindi kailangan ang 1M-token context window, inirerekomendang ibalik ang limitasyon ng Codex context sa loob ng 272K.</p><p></p><p>Buksan ang:</p><p> ~/.codex/config.toml</p><p></p><p>Palitan ang dating 1M configuration:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 1000000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 900000</code></pre><p> </p><p>Gawin itong:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 272000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 250000</code></pre><p> </p><p>Pagkatapos i-save, i-restart ang Codex at gumawa ng bagong session.</p><p></p><p>Kung nais lamang itong ilapat pansamantala sa isang session, gamitin ang:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code>codex -m gpt-5.6-sol -c model_context_window=272000 -c model_auto_compact_token_limit=250000</code></pre><p> Inirerekomenda rin ang mga sumusunod:</p><p> - I-enable agad ang automatic compaction;</p><p> - Hatiin ang mahahabang task sa maraming session;</p><p> - Bawasan ang dami ng tool output na ibinabalik nang sabay-sabay;</p><p> - Regular na ibuod at linisin ang mas lumang bahagi ng usapan.</p><p></p><p>Kung talagang kailangan ang 1M-token context window, maaari mong ipagpatuloy ang dating configuration, ngunit ang bahaging lalampas sa 272K ay sisingilin ayon sa mas mataas na tier ng presyo ng OpenAI.</p><p></p><p>Para sa orihinal na mga tagubilin sa configuration, sumangguni sa: <a target="_blank" rel="noopener noreferrer nofollow" href="https://ai-router.dev/blog/post-g-677aa3e043912838-how-to-enable-a-1m-token-context-window-in-codex-for-gpt-5-6-sol">Paano Paganahin ang 1-Milyong-Token Context Window para sa GPT-5.6 Sol sa Codex </a></p><p></p><p>Salamat sa inyong pag-unawa at suporta.</p>

<p>According to OpenAI's latest billing rules, models such as GPT-5.6 Sol use tiered pricing for extra-long context requests.</p><p>When the context of a single request exceeds 272K tokens, input, cached reads, and output may be billed at higher-tier prices. This rule comes from OpenAI's official pricing and does not represent a temporary surcharge or abnormal charge from AI-ROUTER.</p><p></p><p>Using GPT-5.6 Sol's standard pricing as an example:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Item Within 272K Over 272K</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Input $5 / 1M tokens $10 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Cached read $0.50 / 1M tokens $1 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Output $30 / 1M tokens $45 / 1M tokens</code></pre><p></p><p>The final cost is still calculated based on the specific group, account multiplier, and other billing settings.</p><p></p><p>An x2 indicator in usage records means that the request triggered long-context tiered billing. This indicator mainly means that input and cached reads entered a higher tier; it does not mean that all costs for the entire request are simply doubled. Output may use a different tier multiplier.</p><p></p><p><strong> ## How to Avoid Triggering Tiered Billing</strong></p><p>If you do not need a 1M-token context window, it is recommended that you adjust Codex's context limit back to 272K or below.</p><p></p><p>Open:</p><p> ~/.codex/config.toml</p><p></p><p>Change the 1M configuration from the original article:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 1000000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 900000</code></pre><p> </p><p>to:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 272000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 250000</code></pre><p> </p><p>Save the file, restart Codex, and start a new session.</p><p></p><p>If you only want this to apply temporarily to a single session, you can use:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code>codex -m gpt-5.6-sol -c model_context_window=272000 -c model_auto_compact_token_limit=250000</code></pre><p> It is also recommended that you:</p><p> - Enable automatic compaction promptly;</p><p> - Split extra-long tasks across multiple sessions;</p><p> - Reduce the amount of tool output returned at once;</p><p> - Regularly summarize and clear older conversation content.</p><p></p><p>If you do need a 1M-token context window, you can continue using the original configuration, but usage beyond 272K will be billed according to OpenAI's higher-tier pricing.</p><p></p><p>For the original configuration instructions, see: <a target="_blank" rel="noopener noreferrer nofollow" href="https://ai-router.dev/blog/post-g-677aa3e043912838-how-to-enable-a-1m-token-context-window-in-codex-for-gpt-5-6-sol">How to Enable a 1M-Token Context Window in Codex for GPT-5.6 Sol </a></p><p></p><p>Thank you for your understanding and support.</p>

<p>According to OpenAI's latest billing rules, models such as GPT-5.6 Sol use tiered pricing for ultra-long context requests.</p><p>When the context of a single request exceeds 272K tokens, input, cached reads, and output may be billed at higher tier prices. This rule comes from OpenAI's official pricing and is not a temporary surcharge or abnormal charge from AI-ROUTER.</p><p></p><p>Using GPT-5.6 Sol's standard prices as an example:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Item Within 272K Over 272K</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Input $5 / 1M tokens $10 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Cached reads $0.50 / 1M tokens $1 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Output $30 / 1M tokens $45 / 1M tokens</code></pre><p></p><p>The final cost is still calculated based on the specific group, account multiplier, and other billing settings.</p><p></p><p>If an x2 flag appears in usage records, it means that the request triggered tiered billing for long contexts. This flag mainly indicates that input or cached reads entered a higher tier; it does not mean that all charges for the request were simply doubled. Output may use a different tier multiplier.</p><p></p><p><strong> ## How to Avoid Triggering Tiered Billing</strong></p><p>If you do not need a 1M-token context window, we recommend adjusting Codex's context limit back to within 272K.</p><p></p><p>Open:</p><p> ~/.codex/config.toml</p><p></p><p>Change the 1M configuration from the original article:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 1000000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 900000</code></pre><p> </p><p>To:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 272000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 250000</code></pre><p> </p><p>Save the changes, restart Codex, and start a new session.</p><p></p><p>If you only want this to apply temporarily to a single session, you can use:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code>codex -m gpt-5.6-sol -c model_context_window=272000 -c model_auto_compact_token_limit=250000</code></pre><p> We also recommend:</p><p> - Enable automatic compaction promptly;</p><p> - Split ultra-long tasks across multiple sessions;</p><p> - Reduce the amount of tool output returned at once;</p><p> - Periodically summarize and clear older conversation content.</p><p></p><p>If you do need a 1M-token context window, you can continue using the original configuration, but usage beyond 272K will be billed according to OpenAI's higher tier pricing.</p><p></p><p>For the original configuration instructions, see: <a target="_blank" rel="noopener noreferrer nofollow" href="https://ai-router.dev/blog/post-g-677aa3e043912838-how-to-enable-a-1m-token-context-window-in-codex-for-gpt-5-6-sol">How to Enable a 1M-Token Context Window in Codex for GPT-5.6 Sol </a></p><p></p><p>Thank you for your understanding and support.</p>

<p>Ayon sa pinakabagong tuntunin sa billing ng OpenAI, gumagamit ang mga modelong gaya ng GPT-5.6 Sol ng tiered pricing para sa mga request na may napakahabang context.</p><p>Kapag lumampas sa 272K tokens ang context ng isang request, maaaring singilin ang input, cache read, at output ayon sa mas mataas na tier ng presyo. Nagmula ang tuntuning ito sa opisyal na pricing ng OpenAI at hindi ito pansamantalang dagdag-singil o maling pagsingil ng AI-ROUTER.</p><p></p><p>Bilang halimbawa, narito ang standard na presyo ng GPT-5.6 Sol:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Item Sa loob ng 272K Higit sa 272K</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Input $5 / 1M tokens $10 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Cache read $0.50 / 1M tokens $1 / 1M tokens</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> ────────── ─────────────────── ─────────────────</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> Output $30 / 1M tokens $45 / 1M tokens</code></pre><p></p><p>Ang aktuwal na halaga ay kakalkulahin pa rin batay sa partikular na grupo, account multiplier, at iba pang configuration sa billing.</p><p></p><p>Kapag lumitaw ang x2 flag sa usage record, nangangahulugan itong na-trigger ng request na ito ang tiered billing para sa long context. Pangunahing ipinapahiwatig ng flag na pumasok ang input o cache read sa mas mataas na tier; hindi ito nangangahulugang basta na lang dodoble ang lahat ng bayarin para sa buong request. Maaaring gumamit ang output ng ibang tier multiplier.</p><p></p><p><strong> ## Paano maiiwasang ma-trigger ang tiered billing</strong></p><p>Kung hindi kailangan ang 1M Token context window, inirerekomendang ibalik sa loob ng 272K ang context limit ng Codex.</p><p></p><p>Buksan ang:</p><p> ~/.codex/config.toml</p><p></p><p>Palitan ang 1M configuration mula sa naunang artikulo:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 1000000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 900000</code></pre><p> </p><p>ng:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model = "gpt-5.6-sol"</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_context_window = 272000</code></pre><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code> model_auto_compact_token_limit = 250000</code></pre><p> </p><p>Pagkatapos mag-save, i-restart ang Codex at gumawa ng bagong session.</p><p></p><p>Kung pansamantala lamang itong gagamitin para sa isang session, maaaring gamitin ang:</p><pre class="rounded-lg bg-slate-950 px-4 py-3 text-slate-100"><code>codex -m gpt-5.6-sol -c model_context_window=272000 -c model_auto_compact_token_limit=250000</code></pre><p>Inirerekomenda rin ang mga sumusunod:</p><p> - Agad na paganahin ang awtomatikong compression;</p><p> - Hatiin ang mahahabang gawain sa maraming session;</p><p> - Bawasan ang dami ng tool output na ibinabalik nang sabay-sabay;</p><p> - Regular na ibuod at linisin ang mas naunang nilalaman ng pag-uusap.</p><p></p><p>Kung talagang kailangan ang 1M Token context window, maaari pa ring gamitin ang orihinal na configuration, ngunit kapag lumampas sa 272K, sisingilin ito ayon sa mas mataas na tier ng presyo ng OpenAI.</p><p></p><p>Para sa orihinal na paliwanag tungkol sa configuration, sumangguni sa: <a target="_blank" rel="noopener noreferrer nofollow" href="https://ai-router.dev/blog/post-g-677aa3e043912838-how-to-enable-a-1m-token-context-window-in-codex-for-gpt-5-6-sol">Paano paganahin ang 1 milyong Token context window para sa GPT-5.6 Sol sa Codex </a></p><p></p><p>Salamat sa inyong pag-unawa at suporta.</p>