deepseek-v4-flash-free (zen) 429 FreeUsageLimitError on EVERY request from 3 distinct IPs, with and without official client headers #42074

Activity

1. github-actions

   assigned

   fwang

   on Aug 12, 2026
2. github-actions commented on Aug 12, 2026

   

   github-actionsBot

   on Aug 12, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Error: 429: {"type":"FreeUsageLimitError","message":"Error from provider (Console): Rate limit exceeded. Please try again later."} #42029: Same FreeUsageLimitError 429 on every request from zen
   • [BUG] Zen balance does not remove free usage cap; paid users still hit 200-request/free usage limit #33495: Zen balance does not remove free usage cap; paid users still hit free limit
   • [URGENT] Zen paid balance still hits FreeUsageLimitError / daily free usage limit. #33318: Zen paid balance still hits FreeUsageLimitError / daily free usage limit
   • Rate limited on OpenCode Zen despite paid subscription + balance — no support contact #37680: Rate limited on OpenCode Zen despite paid subscription + balance
   • Go subscription active but still "Free usage exceeded" — paid, no access #36265: Go subscription active but still "Free usage exceeded"

   If your issue is distinct (e.g., a different root cause or a new regression), please add a note explaining how it differs from the above.
3. cubelitblade

   closed this as duplicateon Aug 12, 2026
4. 12errh commented on Aug 13, 2026

   

   12errh

   on Aug 13, 2026

   Last edited by 12errh

   More actions

   @cubelitblade

   Root Cause

   The issue is triggered by the User-Agent header, not the API key or IP address. The upstream "Console" inference provider (which serves the -free models) gates anonymous free capacity strictly based on this header:

   • TUI request (User-Agent: opencode/<version>) → 200 OK
   • Custom request (User-Agent: curl/8.0 or any non-opencode UA) → 429 FreeUsageLimitError

   Testing confirmed that x-opencode-client, x-opencode-version, and session headers alone do not unlock the capacity. Only the User-Agent value matters.

   According to the source code (packages/opencode/src/session/llm/request.ts), the TUI always sends User-Agent: opencode/<version>. The gateway strips all x-opencode-* headers before forwarding upstream but passes the User-Agent through untouched, allowing the upstream provider to use it for free-pool validation.

   ---

   Fix

   Set the opencode User-Agent directly on your request:

   curl -s https://opencode.ai \
     -H "Authorization: Bearer <key-or-public>" \
     -H "Content-Type: application/json" \
     -H "User-Agent: opencode/1.18.16" \
     -d '{"model":"deepseek-v4-flash-free","messages":[{"role":"user","content":"hi"}],"max_tokens":5}'

   Verified: Including the opencode/ UA returns an HTTP 200 (including streaming). Excluding it results in a 429 error, regardless of IP or key.

   ---

   Notes

   • This restriction only affects -free models. Paid and balance-backed models are not gated by the User-Agent.
   • This is an anti-abuse gate designed to reserve free capacity for the official client. Because of this, it may change at any time. For long-term stability, it is better to Bring Your Own Key (BYOK) with a non-free model.
   • If you are writing a custom client, inject User-Agent: opencode/<version> into the request. Please also forward the user's real IP so per-IP quotas remain fair.
   • The solution i make is this simple proxy https://github.com/12errh/zen-proxy it just change the agent header line so it can work.

   👍React with 👍3Reacted by lailo3, Karim Ben Amara and Deuri Vasquez
5. zqy1-1 commented on Aug 15, 2026

   

   zqy1-1

   on Aug 15, 2026

   More actions

   Thank you

   Fix

   Set the User-Agent directly on your request:opencode

   curl -s https://opencode.ai
   -H "Authorization: Bearer "
   -H "Content-Type: application/json"
   -H "User-Agent: opencode/1.18.16"
   -d '{"model":"deepseek-v4-flash-free","messages":[{"role":"user","content":"hi"}],"max_tokens":5}'
   Verified: Including the UA returns an HTTP 200 (including streaming). Excluding it results in a 429 error, regardless of IP or key.opencode/
6. cubelitblade commented on Aug 15, 2026

   

   cubelitblade

   on Aug 15, 2026

   Author

   More actions

   @cubelitblade

   Root Cause

   The issue is triggered by the User-Agent header, not the API key or IP address. The upstream "Console" inference provider (which serves the -free models) gates anonymous free capacity strictly based on this header:

   • TUI request (User-Agent: opencode/<version>) → 200 OK
   • Custom request (User-Agent: curl/8.0 or any non-opencode UA) → 429 FreeUsageLimitError

   Testing confirmed that x-opencode-client, x-opencode-version, and session headers alone do not unlock the capacity. Only the User-Agent value matters.

   According to the source code (packages/opencode/src/session/llm/request.ts), the TUI always sends User-Agent: opencode/<version>. The gateway strips all x-opencode-* headers before forwarding upstream but passes the User-Agent through untouched, allowing the upstream provider to use it for free-pool validation.

   Fix

   Set the opencode User-Agent directly on your request:

   curl -s https://opencode.ai
   -H "Authorization: Bearer "
   -H "Content-Type: application/json"
   -H "User-Agent: opencode/1.18.16"
   -d '{"model":"deepseek-v4-flash-free","messages":[{"role":"user","content":"hi"}],"max_tokens":5}'
   Verified: Including the opencode/ UA returns an HTTP 200 (including streaming). Excluding it results in a 429 error, regardless of IP or key.

   Notes

   • This restriction only affects -free models. Paid and balance-backed models are not gated by the User-Agent.
   • This is an anti-abuse gate designed to reserve free capacity for the official client. Because of this, it may change at any time. For long-term stability, it is better to Bring Your Own Key (BYOK) with a non-free model.
   • If you are writing a custom client, inject User-Agent: opencode/<version> into the request. Please also forward the user's real IP so per-IP quotas remain fair.
   • The solution i make is this simple proxy https://github.com/12errh/zen-proxy it just change the agent header line so it can work.

   Thanks. It seems that after that day, the 429 errors have become much less noticeable—maybe it was just a temporary service fluctuation on their end. Anyway, your analysis and the proxy solution are very helpful.

   👍React with 👍1Reacted by Rehan Mazhar
7. 12errh commented on Aug 15, 2026

   

   12errh

   on Aug 15, 2026

   More actions

   @cubelitblade
   i get know another thing i am using mimo code. and priviously i set the contex window to 500k for deepseek v4 flash even everywhere it say the contex limit 200k. but now if the contex limit is grow from 200k then it start giving me 429 error . so i set the contex limit to 200k and see i make about 250 request and i do not get the 429 error.

   

   👍React with 👍1Reacted by thumb2086