Kimi K3 in OpenCode: the zero-config setup (we're in the built-in model catalog)

OpenCode is the open-source terminal coding agent from the SST team — a TUI you run inside your project directory, with a provider catalog it syncs from models.dev. That last part is why this guide is short: Wallaby Token is in that catalog, so OpenCode already knows our endpoint, our auth variable, and our model id. There is no base URL to copy and no config file to edit. Disclosure: Wallaby Token sells API access to kimi-k3, and the endpoint used here is ours.

What the setup actually looks like:

• One environment variable — WALLABY_API_KEY. The catalog entry tells OpenCode exactly which variable to read.
• One refresh — opencode models --refresh pulls the latest catalog; wallaby/moonshotai/kimi-k3 shows up in the list.
• Then it behaves like any built-in provider — pick the model in the TUI with /models, or pass it with -m in one-shot runs.

What you need

• A Wallaby Token account (create one at wallabytoken.com; new accounts receive $0.50 in free credit) and an API key from the console
• macOS or Linux (on Windows, use WSL)
• Two minutes

Step 1: Install OpenCode

curl -fsSL https://opencode.ai/install | bash

This installs the binary to ~/.opencode/bin/opencode. One real gotcha from our install run: the installer adds the PATH line to ~/.bash_profile only. If your shell is zsh — the macOS default — a new terminal won't find the command. Fix it once:

echo 'export PATH="$HOME/.opencode/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
opencode --version    # 1.18.31 at the time of writing

Step 2: Set your key

export WALLABY_API_KEY=sk-your-wallaby-key

Add the same line to ~/.zshrc so it survives new terminals.

Step 3: Refresh the catalog and find us

opencode models --refresh
opencode models | grep wallaby

You should see:

wallaby/moonshotai/kimi-k3

Nothing in that line was configured by hand — it comes from the public models.dev catalog that OpenCode syncs. Two notes from testing: the refresh step is required (a stale cache won't show newly listed providers), and the catalog only surfaces paid providers once the matching key variable is set.

Step 4: Run it

One-shot from the shell:

opencode run -m wallaby/moonshotai/kimi-k3 "Write a Python function that checks whether a string is a palindrome"

Or the interactive way — cd into a project, run opencode, type /models, select Kimi K3 under the Wallaby provider, and start working.

Our verification run, unedited:

$ opencode run -m wallaby/moonshotai/kimi-k3 "Reply with exactly three words: Wallaby funnel works"
> build · moonshotai/kimi-k3
Wallaby funnel works

Verify on the billing side

A working reply is leg one and two of the test. Leg three: open your console's Usage Logs. Seconds after the request, there is a line with the model, token counts, and cost — our smoke prompt above cost about $0.019, itemized immediately:

The line will show the model as moonshotai/kimi-k3. That is the models.dev canonical id, not a different model and not a mis-bill — same model, same price as kimi-k3, just the namespaced name the catalog ecosystem uses.

Troubleshooting (only what we actually hit)

Rolling out to a team

OpenCode's zero-config path doubles as the fastest team-evaluation path we know: every developer runs the same four steps, no per-machine endpoint babysitting. The account side then carries the team mechanics — one prepaid balance as a hard ceiling on the whole team's spend, one named key per developer with its own dollar cap and optional expiry, and usage logs itemized per key so per-person cost attribution is the default view, not a spreadsheet project. There are no seat fees: adding a teammate costs exactly their token usage. The full walkthrough is in One endpoint, one bill.

Pricing

Per 1M tokens, as of September 2026 (current rates always on the pricing page):

The $0.50 trial credit covers this entire guide many times over — the verification call above cost under two cents.

Your code, your business

Three commitments, verbatim from our privacy policy: No content logs. No training on your data. No usage reports built from your traffic. Usage lines record token counts, costs, and timing — never prompts, never completions.

Reliability you can verify

We operate a public status page so you can verify availability independently before troubleshooting your own setup. Our terms are written in plain language and publicly accessible. Wallaby Token is a registered Australian company with an ABN on file, and we run our own development workloads through the same gateway we sell — the calls behind this guide ran on it.

Get started

Create an account at wallabytoken.com, mint a key, set one environment variable, refresh the catalog. It is the shortest path from zero to Kimi K3 in a terminal agent that we are aware of — it took us about two minutes, end to end.