Problem
The Anthropic provider supports a custom apiBase, but the provider page only shows the default Anthropic-hosted configuration. Users of Anthropic-compatible Messages API endpoints do not currently have an example showing the required /v1/ suffix.
Proposed documentation change
Add a focused section to the existing Anthropic provider page that:
- explains that
provider: anthropic can use a third-party Anthropic-compatible endpoint;
- shows
apiBase in both YAML and legacy JSON;
- uses API Token Sale as a concrete tested example; and
- clearly states that it is an independent provider, not affiliated with Anthropic or Continue.
This is documentation-only and uses Continue’s existing native Anthropic transport.
Problem
The Anthropic provider supports a custom
apiBase, but the provider page only shows the default Anthropic-hosted configuration. Users of Anthropic-compatible Messages API endpoints do not currently have an example showing the required/v1/suffix.Proposed documentation change
Add a focused section to the existing Anthropic provider page that:
provider: anthropiccan use a third-party Anthropic-compatible endpoint;apiBasein both YAML and legacy JSON;This is documentation-only and uses Continue’s existing native Anthropic transport.