Add Requesty as an OpenAI-compatible provider - #2163
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
Register Requesty in the openai_compatible provider config, mirroring the existing OpenRouter entry: name Requesty, base URL https://router.requesty.ai/v1. The env var (REQUESTY_API_KEY) is derived from the provider name by the existing plugin machinery, same as OPENROUTER_API_KEY. Also lists Requesty in the OpenAI-compatible providers section of the README. Signed-off-by: Thibault Jaigu <thibault.jaigu@gmail.com>
Thibaultjaigu
force-pushed
the
add-requesty-provider
branch
from
September 11, 2026 16:32
d85a50f to
b5b6433
Compare
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.
Add Requesty as an OpenAI-compatible provider
This adds Requesty as an OpenAI-compatible AI provider by mirroring the existing OpenRouter entry.
Requesty is an OpenAI-compatible LLM router that exposes 400+ models behind a single endpoint using
provider/modelnaming, so it fits the existingopenai_compatibleprovider mechanism directly.Changes
internal/plugins/ai/openai_compatible/providers_config.go: add aRequestyentry toProviderMap, mirroringOpenRouter: nameRequesty, base URLhttps://router.requesty.ai/v1. The provider is auto-registered by the existing registry loop, and theREQUESTY_API_KEYenv var is derived from the provider name by the existing plugin machinery (same asOPENROUTER_API_KEY).README.md/README.zh.md: list Requesty in the OpenAI-compatible providers section.Testing
go build ./...: cleango vet ./internal/plugins/ai/openai_compatible/: cleangofmt -lon the changed file, no outputgo test ./internal/plugins/ai/openai_compatible/: okopenai/gpt-4o-minireturned the expected completion with HTTP 200.Note:
internal/server/configuration.go(web-UI config endpoint) only lists a subset of the compatible providers, so I left it untouched to keep the diff minimal and matching the actual OpenRouter wiring, happy to add the web-UI key field too if you'd like.Config: 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.