Custom providers

Use custom providers when your endpoint uses an OpenAI-compatible, Anthropic-compatible, or Gemini-compatible format but is not one of Sleev's built-in providers. Most users should leave this unset.

Keep the harness pointed at the local gateway, then send sleev-harness and sleev-base-url in its request headers. See the per-harness examples in Harness Setup. Do not set sleev-provider for custom providers:

sleev-harness: opencode
sleev-base-url: https://provider.example.test/v1

Use a full http or https base API URL. Include a path such as /v1 only when it is part of the provider's API base.

Hermes custom upstreams use a named provider with the complete nested upstream in its API URL instead of routing headers. See the Hermes Agent setup for an example.