Repository navigation
HTTP 500 api_error: insufficient balance (1008) when using free model opencode/big-pickle via Clawdbotย #10718
Description
Summary
I am consistently seeing this error from OpenCode when using it through Clawdbot:
HTTP 500: api๐ฆ๐ณ๐ณ๐ฐ๐ณ: ๐ช๐ฏ๐ด๐ถ๐ง๐ง๐ช๐ค๐ช๐ฆ๐ฏ๐ต ๐ฃ๐ข๐ญ๐ข๐ฏ๐ค๐ฆ (1008)
๐๐ฉ๐ช๐ด ๐ฉ๐ข๐ฑ๐ฑ๐ฆ๐ฏ๐ด ๐ฆ๐ท๐ฆ๐ฏ ๐ต๐ฉ๐ฐ๐ถ๐จ๐ฉ:
โข ๐ ๐ฉ๐ข๐ท๐ฆ ๐ข ๐ฑ๐ฐ๐ด๐ช๐ต๐ช๐ท๐ฆ ๐ฃ๐ข๐ญ๐ข๐ฏ๐ค๐ฆ ๐ช๐ฏ ๐ฎ๐บ ๐๐ฑ๐ฆ๐ฏ๐๐ฐ๐ฅ๐ฆ ๐ข๐ค๐ค๐ฐ๐ถ๐ฏ๐ต (๐ข๐ณ๐ฐ๐ถ๐ฏ๐ฅ $20).
โข ๐ ๐ฉ๐ข๐ท๐ฆ ๐ช๐ฏ๐ต๐ฆ๐ฏ๐ต๐ช๐ฐ๐ฏ๐ข๐ญ๐ญ๐บ ๐ค๐ฐ๐ฏ๐ง๐ช๐จ๐ถ๐ณ๐ฆ๐ฅ ๐๐ญ๐ข๐ธ๐ฅ๐ฃ๐ฐ๐ต ๐ต๐ฐ ๐ถ๐ด๐ฆ ๐ฐ๐ฏ๐ญ๐บ ๐ต๐ฉ๐ฆ ๐ง๐ณ๐ฆ๐ฆ ๐ฎ๐ฐ๐ฅ๐ฆ๐ญ "๐ฐ๐ฑ๐ฆ๐ฏ๐ค๐ฐ๐ฅ๐ฆ/๐ฃ๐ช๐จ-๐ฑ๐ช๐ค๐ฌ๐ญ๐ฆ".
๐๐ต ๐ญ๐ฐ๐ฐ๐ฌ๐ด ๐ญ๐ช๐ฌ๐ฆ ๐ค๐ข๐ญ๐ญ๐ด ๐ต๐ฐ "๐ฐ๐ฑ๐ฆ๐ฏ๐ค๐ฐ๐ฅ๐ฆ/๐ฃ๐ช๐จ-๐ฑ๐ช๐ค๐ฌ๐ญ๐ฆ" ๐ข๐ณ๐ฆ ๐ฃ๐ฆ๐ช๐ฏ๐จ ๐ต๐ณ๐ฆ๐ข๐ต๐ฆ๐ฅ ๐ข๐ด ๐ฃ๐ช๐ญ๐ญ๐ข๐ฃ๐ญ๐ฆ ๐ฐ๐ณ ๐ณ๐ฐ๐ถ๐ต๐ฆ๐ฅ ๐ต๐ฉ๐ณ๐ฐ๐ถ๐จ๐ฉ ๐ข ๐ฑ๐ข๐ช๐ฅ ๐ฑ๐ข๐ต๐ฉ, ๐ค๐ข๐ถ๐ด๐ช๐ฏ๐จ ๐ต๐ฉ๐ฆ "๐ช๐ฏ๐ด๐ถ๐ง๐ง๐ช๐ค๐ช๐ฆ๐ฏ๐ต ๐ฃ๐ข๐ญ๐ข๐ฏ๐ค๐ฆ (1008)" ๐ฆ๐ณ๐ณ๐ฐ๐ณ. ๐ณ๐ฆ๐ฅ๐ฅ๐ช๐ต (๐ฉ๐ต๐ต๐ฑ๐ด://๐ธ๐ธ๐ธ.๐ณ๐ฆ๐ฅ๐ฅ๐ช๐ต.๐ค๐ฐ๐ฎ/๐ณ/๐ฐ๐ฑ๐ฆ๐ฏ๐ค๐ฐ๐ฅ๐ฆ๐๐๐/๐ค๐ฐ๐ฎ๐ฎ๐ฆ๐ฏ๐ต๐ด/1๐ฒ8๐ฐ๐ด6๐ด/๐ฅ๐ฐi๐ฉ๐ข๐ท๐ฆto๐ฅ๐ฆ๐ฑ๐ฐ๐ด๐ช๐ตmoney๐ช๐ฏ๐ต๐ฐmy๐ข๐ค๐ค๐ฐ๐ถ๐ฏ๐ตto๐ถ๐ด๐ฆ/)
๐๐ฏ๐ท๐ช๐ณ๐ฐ๐ฏ๐ฎ๐ฆ๐ฏ๐ต
โข ๐๐ฑ๐ฆ๐ฏ๐๐ฐ๐ฅ๐ฆ ๐ข๐ค๐ค๐ฐ๐ถ๐ฏ๐ต: ๐ฑ๐ข๐ช๐ฅ ๐ฃ๐ข๐ญ๐ข๐ฏ๐ค๐ฆ (๐ข๐ฃ๐ฐ๐ถ๐ต $20 ๐ข๐ท๐ข๐ช๐ญ๐ข๐ฃ๐ญ๐ฆ)
โข ๐๐ฐ๐ฅ๐ฆ๐ญ: ๐ฐ๐ฑ๐ฆ๐ฏ๐ค๐ฐ๐ฅ๐ฆ/๐ฃ๐ช๐จ-๐ฑ๐ช๐ค๐ฌ๐ญ๐ฆ (๐ข๐ฅ๐ท๐ฆ๐ณ๐ต๐ช๐ด๐ฆ๐ฅ ๐ข๐ด ๐ข ๐ง๐ณ๐ฆ๐ฆ/๐ด๐ต๐ฆ๐ข๐ญ๐ต๐ฉ ๐ฎ๐ฐ๐ฅ๐ฆ๐ญ ๐ง๐ฐ๐ณ ๐ฏ๐ฐ๐ธ) ๐ณ๐ฆ๐ฅ๐ฅ๐ช๐ต (๐ฉ๐ต๐ต๐ฑ๐ด://๐ธ๐ธ๐ธ.๐ณ๐ฆ๐ฅ๐ฅ๐ช๐ต.๐ค๐ฐ๐ฎ/๐ณ/๐ฐ๐ฑ๐ฆ๐ฏ๐ค๐ฐ๐ฅ๐ฆ๐๐๐/๐ค๐ฐ๐ฎ๐ฎ๐ฆ๐ฏ๐ต๐ด/1๐ฑ๐ณ๐ซ๐ฉ๐ถ๐ฃ/๐ช๐ดopencode๐ป๐ฆ๐ฏbig๐ฑ๐ช๐ค๐ฌ๐ญ๐ฆfree/)
โข Client: Clawdbot (local gateway)
โข Channel: Telegram bot connected to Clawdbot
โข OS: Windows 11 with WSL2 (Ubuntu) running Clawdbot
โข Clawdbot version: 2026.1.24-3 (885167d)
โข Network: Telegram connectivity from Clawdbot is now working (DNS issue fixed by pinning api.telegram.org to IPv4 in /etc/hosts)
What I did
- Set my default model to the free OpenCode model:
clawdbot config set agents.defaults.model.primary "opencode/big-pickle"
clawdbot gateway restart
-
Verified with "clawdbot logs" that:
โข The gateway starts with: agent model: opencode/big-pickle
โข Telegram provider is ok (my bot username shows correctly)
โข There are no more "fetch failed" or "setMyCommands failed" errors to Telegram -
Ran "clawdbot doctor" and then "clawdbot doctor --fix":
โข No critical provider/model warnings were reported
โข Config file ~/.clawdbot/clawdbot.json was updated and Clawdbot appears healthy -
Sent a normal chat message to my Telegram bot, which triggers a Clawdbot run with provider "opencode" and model "big-pickle".
Actual behavior
The model run starts and then fails with an error like:
HTTP 500: api๐ฆ๐ณ๐ณ๐ฐ๐ณ: ๐ช๐ฏ๐ด๐ถ๐ง๐ง๐ช๐ค๐ช๐ฆ๐ฏ๐ต ๐ฃ๐ข๐ญ๐ข๐ฏ๐ค๐ฆ (1008) (๐ณ๐ฆ๐ฒ๐ถ๐ฆ๐ด๐ตid: 05c6cd5820af43aca312bd84ebc5f963)
From my perspective:
โข I have sufficient account balance.
โข I am not intentionally using any paid models.
โข All agent defaults are set to "opencode/big-pickle". github (#7499)
Expected behavior
โข Requests using "opencode/big-pickle" should be treated as free and should not fail due to balance checks, as long as the free tier is active. reddit (https://www.reddit.com/r/opencodeCLI/comments/1q8os6s/do๐ชhave๐ต๐ฐdeposit๐ฎ๐ฐ๐ฏ๐ฆ๐บinto๐ฎ๐บaccount๐ต๐ฐuse/)
โข If there are specific limits, quotas, or regional restrictions for this model, the error message should explain that instead of a generic "insufficient balance (1008)".
Additional context
โข This error started surfacing clearly after I fixed a separate Telegram connectivity issue. Previously, the gateway could not reach api.telegram.org, so responses failed earlier in the chain.
โข Now that Telegram connectivity is fixed, the only remaining failure is this "insufficient balance (1008)" from OpenCode when calling "opencode/big-pickle".
โข I am happy to run test commands, provide additional log snippets, or confirm organization/project IDs on my account if that helps debug whether this is a routing or billing configuration issue on the backend. github (#7499)
Activity
github-actions commentedon Jan 26, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
github-actions commentedon Mar 29, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.