feat(providers): add Requesty as an OpenAI-compatible provider - #953
Open
Thibaultjaigu wants to merge 1 commit into
Open
Thibaultjaigu wants to merge 1 commit into
Thibaultjaigu wants to merge 1 commit into
Conversation
Adds a requesty registry row (https://router.requesty.ai/v1, REQUESTY_API_KEY) in hybrid catalog mode like OpenRouter. Model discovery reads Requesty's managed models endpoint and falls back to the full /models catalog. Also adds the key group in desktop settings, the VS Code extension labels, docs and tests.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All Submissions:
New Feature Submissions:
Description
Adds Requesty, an OpenAI-compatible gateway to many model vendors, as a provider. It is a single row in the
ProviderSpecregistry, like the other hosted OpenAI-compatible vendors, and it uses hybrid catalog mode like OpenRouter: the curated list comes first and the live list is appended. It is opt-in only. It is not the default and is not part of any fallback order.Changes proposed in this pull request:
src/providers/openai_compatible_specs.py: newrequestyrow with base URLhttps://router.requesty.ai/v1, key fromREQUESTY_API_KEY, and defaultanthropic/claude-sonnet-4-5(the same default OpenRouter uses). The curated list is seeded from Requesty's managed model ids. All ids were checked against the live catalog.src/providers/model_discovery.py: newrequestydiscovery kind. It readsGET /models/managed(keeps only chat models) and falls back to the standard/modelscatalog when that fails. The existing kinds are unchanged.REQUESTY_key group. VS Code extension: label and env var entries next to OpenRouter.https://router.eu.requesty.ai/v1works throughbase_url), and a CHANGELOG entry.How to test:
Checks run locally:
pytest tests/test_provider_registry.py tests/providers/ tests/test_opencode_compat_providers.py tests/test_providers.py: 379 passednpm test: 84 passed,node scripts/lint.jscleanget_provider_class("requesty")withopenai/gpt-4o-mini: 200, the reply came back and the model was echoed asgpt-4o-mini-2024-07-18. Discovery returned 159 managed models, and the hybrid merge kept the curated ids first.npm ci). The change there is one object inPROVIDER_GROUPSthat uses the same shape as its neighbours.Disclosure: I work at Requesty. Happy to adjust anything to match project conventions.