feat: add Requesty as an OpenAI-compatible provider - #61
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for rad-granita-26ed35 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
This adds a dedicated
requestyprovider, mirroring the existing OpenRouter provider as closely as possible.Changes:
packages/models/provider_catalog.py: a newProviderDefinitionforrequesty, mirroring the OpenRouter entry (transportopenai_chat_compatible, base URLhttps://router.requesty.ai/v1,provider_kind="aggregator", env varREQUESTY_API_KEY).packages/models/model_metadata.py: addrequestyto the provider to models.dev slug map androuter.requesty.aito the host to provider map, so model metadata resolution works for Requesty too.Requesty is an OpenAI-compatible LLM gateway and uses the same
provider/modelnaming as OpenRouter, so it reuses the existingopenai_chat_compatibletransport (no new client code). Requesty also exposes the standard OpenAI/v1/models, and it is listed on models.dev under therequestyslug, so the metadata path resolves.Verification:
default_provider_definitions()andprovider_definition("requesty")resolve as expected (base URL, transport, env var). I also tested the endpoint live:GET https://router.requesty.ai/v1/modelsreturned 200 (578 models), and a chat completion withopenai/gpt-4o-minireturned 200.Docs: https://requesty.ai , https://app.requesty.ai/api-keys
I work at Requesty. This mirrors the existing OpenRouter provider as closely as possible. Happy to adjust or close it if it's not a fit.