OpenCode - HiLinkup Docs

The examples on this page use Chat Completions. If the current OpenCode version exposes a dedicated Responses provider, select that mode instead.

Prepare

export HILINKUP_API_KEY="YOUR_HILINKUP_API_KEY"

curl https://api.hilinkup.com/v1/models \
  -H "Authorization: Bearer $HILINKUP_API_KEY"

Environment variables

export HILINKUP_API_KEY="YOUR_HILINKUP_API_KEY"
export HILINKUP_BASE_URL="https://api.hilinkup.com/v1"
export HILINKUP_MODEL="aliyun/kimi-k3"

Provider mapping

OpenCode field	Value
Provider	OpenAI-compatible / Custom OpenAI
API key	`$HILINKUP_API_KEY`
Base URL	`https://api.hilinkup.com/v1`
Model	A model ID returned by `/v1/models`

Configuration file template

If your OpenCode version supports provider config files, keep the key in the environment and store only provider metadata in the config:

{
  "providers": {
    "hilinkup": {
      "type": "openai-compatible",
      "name": "HiLinkup",
      "apiKey": "${HILINKUP_API_KEY}",
      "baseURL": "https://api.hilinkup.com/v1",
      "models": {
        "aliyun/kimi-k3": {
          "name": "aliyun/kimi-k3"
        }
      }
    }
  },
  "defaultProvider": "hilinkup",
  "defaultModel": "aliyun/kimi-k3"
}

OpenCode config field names can differ by release. If your version uses baseUrl, base_url, or api_key, keep the values the same and adapt the field names to the current schema.

Verify

Test a plain cURL chat request.
Create an OpenAI-compatible provider in OpenCode.
Run a read-only task in a temporary project.
Enable tool calls and file edits only after plain chat works.

A successful standalone API call does not prove that a full agent request with tools and a large prompt will succeed. Test the complete workflow.

Last modified on August 12, 2026