-
Notifications
You must be signed in to change notification settings - Fork 6k
(feat): add routstr as a declarative provider #9175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| { | ||
| "name": "routstr", | ||
| "engine": "openai", | ||
| "display_name": "Routstr", | ||
| "description": "OpenAI-compatible aggregator that fronts dozens of upstream providers (OpenAI, Anthropic, Google, DeepSeek, Llama, …) behind a single API. Authenticate with an sk-... bearer issued by a Routstr instance — payment (e.g. Cashu top-up) is handled outside goose.", | ||
| "api_key_env": "ROUTSTR_API_KEY", | ||
| "base_url": "${ROUTSTR_HOST}/v1", | ||
| "env_vars": [ | ||
| { | ||
| "name": "ROUTSTR_HOST", | ||
| "required": false, | ||
| "secret": false, | ||
| "primary": true, | ||
| "default": "https://api.routstr.com", | ||
| "description": "Base URL of the Routstr proxy (default: https://api.routstr.com)" | ||
| } | ||
| ], | ||
| "dynamic_models": true, | ||
| "models": [ | ||
| { "name": "claude-opus-4.7", "context_limit": 1000000 }, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
When dynamic model fetching is unavailable or a user accepts the provider's default model, Useful? React with 👍 / 👎. |
||
| { "name": "gemini-3.1-pro-preview", "context_limit": 1048576 }, | ||
| { "name": "gemini-3-flash-preview", "context_limit": 1048576 }, | ||
| { "name": "deepseek-v4-pro", "context_limit": 1048576 }, | ||
| { "name": "glm-5.1", "context_limit": 202752 }, | ||
| { "name": "minimax-m2.7", "context_limit": 196608 } | ||
| ], | ||
| "supports_streaming": true, | ||
| "skip_canonical_filtering": true, | ||
| "model_doc_link": "https://routstr.com/docs", | ||
| "setup_steps": [ | ||
| "Pick a Routstr instance (e.g. https://api.routstr.com) and obtain an sk-... API key from its payment flow.", | ||
| "Paste the key above as ROUTSTR_API_KEY.", | ||
| "Optionally override ROUTSTR_HOST to point at a different Routstr proxy." | ||
| ] | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When Routstr's dynamic
/v1/modelslist includes OpenAIo*/gpt-5*IDs, this base URL derives the default OpenAIv1/chat/completionspath, andOpenAiProvider::should_use_responses_apiroutes those model names to/v1/responsesinstead. Routstr is being documented here as a chat-completions OpenAI-compatible router, so users who pick one of those dynamically fetched models will send requests to an endpoint the Routstr integration does not configure or document. Add a provider-level way to force chat completions for Routstr before enabling dynamic models for OpenAI-family IDs.Useful? React with 👍 / 👎.