Pay for OpenCode

The two paid products price very differently. OpenCode Go is $10 a month flat and gives you access to roughly thirty open-weight models — the Grok, DeepSeek, Qwen, Kimi, GLM and MiMo families among them — under spend caps of about $12 per five hours, $30 per week and $60 per month. OpenCode Zen has no monthly fee at all: you top up a credit balance and pay each model’s per-token rate, which ranges from a few cents per million tokens on the small open models up to tens of dollars per million output tokens on frontier ones, with some models free during promotional periods. OpenCode is a young, fast-moving product and both the prices and the model roster change often, so treat the figure in the OpenCode Zen console at the moment you pay as the real one, not anything you read here.

One number worth knowing before you top up: OpenCode passes card processing fees through at cost on Zen credit purchases — its own documentation puts that at 4.4% plus $0.30 per transaction. A $10 credit purchase therefore shows up on the card as a little more than $10. That is OpenCode’s disclosed pass-through of what its payment processor charges, not a Mehbit fee, and it is why you should never fund the card with the exact amount to the cent.

On 2026-09-02, and again on 2026-09-04, a real Mehbit card was entered at OpenCode’s checkout for $10.00. In both cases OpenCode’s checkout accepted the card and sent the charge to the network — it passed the BIN, merchant-category and country checks that block cards at some merchants — and the charge was then declined for one reason only: the card itself had no balance. So what these two attempts prove is that OpenCode accepts Mehbit cards. They are not a record of money that settled, and we are not going to pretend otherwise. That distinction is the whole point of the tip below.

Those two declines are, almost word for word, the failure mode this page exists to warn you about. OpenCode bills Go monthly on the day you subscribed, and Zen auto-reloads your credit balance the moment it drops below its threshold — neither event asks you first, and neither waits for you. If the card is empty at that moment, the charge fails; Go lapses and Zen simply stops serving requests mid-session. Nothing dramatic happens to your account, but your agent stops working in the middle of whatever you were doing. Keep the card funded ahead of the date rather than on it.

A few setup details save time. You sign up through the OpenCode Zen console, usually with a GitHub account, subscribe to Go or add credits there, and get an API key you then paste into the client with the /connect command; /models lists what that key can reach. Zen also lets you set a monthly spend ceiling for the workspace and per member, which is worth doing on day one — but note that automatic reload is a separate mechanism and can still charge the card after a monthly limit is hit, so the ceiling is a usage control, not a guarantee about what your card will see.