OpenCode integration
Connect OpenCode to an explicitly configured DarkSeek endpoint.
Select the correct protocol#
Configure a custom provider only if this client supports it. Use the account-issued DarkSeek key and supplied HTTPS API origin. OpenAI-compatible clients use chat/Responses as supported; Anthropic-compatible clients use the Messages contract. Never send a DarkSeek key to the reference provider.
Model and endpoint#
Use the deployed model alias darkseek-v4.1. A base URL, credential and protocol are independent settings. Do not copy undocumented client environment variables or assume an endpoint path is automatically appended. Follow the client’s current provider documentation.
Verify before production#
Run a bounded one-turn request, then tool calls and streaming cancellation using a nonproduction credential. Confirm both the request and response formats. This page is not certification of every version of OpenCode. Interactive account login, built-in search and client subscriptions do not transfer to DarkSeek.