Problem
ZvenoAI exposes an OpenAI-compatible endpoint, but Continue users currently have to infer the provider: openai configuration and the exact apiBase themselves.
Proposed scope
Add a short provider guide that:
- uses Continue's existing
openai provider rather than adding a runtime provider;
- shows
https://api.zveno.ai/v1 and one current model ID;
- keeps the API key in a Continue secret;
- links to the live ZvenoAI model catalog instead of duplicating a model list or prices.
The public production /v1/models endpoint currently confirms the proposed model ID and tool-calling parameters. I can send the focused docs PR if this scope is welcome.
Problem
ZvenoAI exposes an OpenAI-compatible endpoint, but Continue users currently have to infer the
provider: openaiconfiguration and the exactapiBasethemselves.Proposed scope
Add a short provider guide that:
openaiprovider rather than adding a runtime provider;https://api.zveno.ai/v1and one current model ID;The public production
/v1/modelsendpoint currently confirms the proposed model ID and tool-calling parameters. I can send the focused docs PR if this scope is welcome.