Use OpenCode with any model

Set it up

1. 01

   The configuration surface

   The file is opencode.json, either at your repository root or globally at ~/.config/opencode/opencode.json, and the two are merged. Add a provider:

   opencode.json

   {
     "provider": {
       "hopscotch": {
         "npm": "@ai-sdk/openai-compatible",
         "name": "Hopscotch",
         "options": {
           "baseURL": "https://api.hopscotchlabs.ai/v1",
           "apiKey": "{env:HOPSCOTCH_API_KEY}"
         },
         "models": {
           "openai/gpt-4o-mini": {
             "name": "GPT-4o mini via Hopscotch"
           }
         }
       }
     }
   }

   OpenCode does not append /v1. Its documentation says the baseURL should end at the version prefix the provider uses, so include it.

2. 02

   Pick the right package

   npm names the adapter, and the choice is not cosmetic. @ai-sdk/openai-compatible speaks chat completions, which is what this API serves.

3. 03

   List the models yourself

   OpenCode does not ask a custom provider what it can serve. It has no discovery step for one, so the models it offers are the keys of your models object, and those keys are pinned ids. Adding a model means editing the file again.

   Each model may carry a limit object with context and output. Fill both in from GET /v1/models, which publishes the context window and the maximum output for every model.

4. 04

   The key, and the file that gets committed

   OpenCode's own documentation says the project-level config is safe to check into version control, which it is right up until somebody writes a key into it. Use the interpolation instead: {env:VARIABLE_NAME} reads the value from your environment, as in the block above, and resolves to an empty string when the variable is unset.

   bash

   export HOPSCOTCH_API_KEY=ub_live_YOUR_KEY_HERE

These models support tool calling and take at least 128K tokens of context. Prices are per million tokens.

What changes when OpenCode runs through Hopscotch