Add Requesty as an OpenAI-compatible LLM provider - #529
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
Mirror the existing OpenRouter provider for Requesty, an OpenAI-compatible LLM router that uses the same provider/model naming. Adds a dedicated 'requesty' provider (base URL https://router.requesty.ai/v1, REQUESTY_API_KEY), registers it in available_providers and unsafe_providers, applies the same message-format handling as OpenRouter in memory, and lists it in .env.example and the README provider table. 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.
Add Requesty as an OpenAI-compatible LLM provider
This adds Requesty as an LLM provider by mirroring the existing OpenRouter integration.
Requesty is an OpenAI-compatible LLM router exposing 400+ models behind a single API, using the same
provider/modelnaming convention as OpenRouter, so it fits the existing provider dispatch cleanly.Changes
sources/llm_provider.py— addrequesty_fn, a mirror ofopenrouter_fnusingOpenAI(base_url="https://router.requesty.ai/v1"); registerrequestyinavailable_providersandunsafe_providers. The API key is resolved by the existing generic{PROVIDER}_API_KEYlogic (REQUESTY_API_KEY).sources/memory.py— apply the same message-format handling torequestyasopenrouter..env.example— addREQUESTY_API_KEY.README.md— add Requesty to the provider table.Testing
Verified live against the Requesty endpoint (same base URL + Bearer auth
requesty_fnuses): a call toopenai/gpt-4o-minireturned the expected completion with HTTP 200.Config:
provider_name = requestyinconfig.ini,is_local = False, setREQUESTY_API_KEY. Get a key at https://app.requesty.ai/api-keys, model list at https://app.requesty.ai/router/list, docs at https://docs.requesty.ai.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.