continuedev / continuedev/continue
Docs: document custom Anthropic-compatible endpoints
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
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: anthropiccan use a third-party Anthropic-compatible endpoint; - shows
apiBasein 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the existing Anthropic provider page and compare its current configuration examples with the requested custom endpoint guidance. Add YAML and legacy JSON examples using the /v1/ suffix, the API Token Sale example, and the stated independence disclaimer; done when the page covers all four requested points without changing transport code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, yaml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100