feat: add Requesty as an OpenAI-compatible provider#155
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
Signed-off-by: Thibault Jaigu <thibault.jaigu@gmail.com>
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.
This adds a dedicated
requestyprovider, mirroring the existing OpenRouter provider as closely as possible.Changes:
backend_api_python/app/services/llm.py: addREQUESTYto theLLMProviderenum, aPROVIDER_CONFIGSentry (base URLhttps://router.requesty.ai/v1), theget_api_keykey map, and the auto-detect priority list.backend_api_python/app/config/api_keys.py: add aREQUESTY_API_KEYproperty mirroringOPENROUTER_API_KEY(env var first, then addon config).backend_api_python/app/utils/config_loader.py: add theREQUESTY_API_KEYtorequesty.api_keyenv mapping.Requesty is an OpenAI-compatible LLM gateway and uses the same
provider/modelnaming as OpenRouter, so it reuses the same OpenAI-compatible client path (no new request code).Verification: I tested the endpoint live before opening this.
GET https://router.requesty.ai/v1/modelsreturned 200 (around 578 models), and a chat completion withopenai/gpt-4o-miniagainsthttps://router.requesty.ai/v1/chat/completionsreturned 200. I confirmed the enum, config, key map, and priority list all resolverequestyconsistently.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 is not a fit.