continuedev / continuedev/continue
Provider/docs request: Starveri API OpenAI-compatible gateway
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Hi! Would Starveri API be in scope for a model-provider docs page, example config, or built-in provider entry?
Starveri is an OpenAI-compatible GPT/Codex API gateway with prepaid credits, public model discovery, and documented per-token pricing. It looks like it should be usable through Continue's OpenAI-compatible/custom provider path, but a docs example could help users evaluating lower-cost GPT/Codex-style API providers.
Public config/source details:
- Base URL: https://api.starveri.net/v1
- Auth: API key / Bearer token
- Chat endpoint: OpenAI-compatible chat completions
- Model discovery: GET https://api.starveri.net/v1/models with the user's API key; public model metadata is also available at https://api.starveri.net/models
- Docs: https://api.starveri.net/docs
- Credits / key creation: https://api.starveri.net/credits
- OpenAPI: https://api.starveri.net/openapi.json
Current advertised model IDs include gpt-5.5, gpt-5.4, gpt-5.4-mini, gpt-5.3-codex-spark, gpt-5.3-codex, and gpt-5.1-codex. Pricing is documented publicly in the docs page, including cached-input, input, output, web-search, and code-interpreter charges.
If third-party OpenAI-compatible gateways are in scope for provider docs or examples, I can prepare a small docs PR using only the public source links above. If this should stay as a generic custom-provider setup, feel free to close.
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
Start by reading the existing provider documentation and custom-provider guidance, then verify the Starveri details against its public docs and OpenAPI links. Done means either a scoped provider documentation example using the listed base URL and authentication, or a clear decision that generic custom-provider instructions are sufficient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- ai, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100