feat: add Requesty as an OpenAI-compatible provider#662
Open
Thibaultjaigu wants to merge 1 commit into
Open
Conversation
|
@Thibaultjaigu is attempting to deploy a commit to the op7418's projects Team on Vercel. A member of the Team first needs to authorize it. |
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 provider
This adds Requesty (
https://router.requesty.ai/v1) as a first-class provider preset, mirroring how the existing gateway providers are wired.How it fits the existing architecture
Providers in this repo are config-driven:
VENDOR_PRESETSinsrc/lib/provider-catalog.tsis the single source of truth, and the quick-add UI, search-and-add, and model discovery are all generated from it. This PR adds arequestypreset there rather than adding any bespoke code path.src/lib/provider-catalog.ts— newrequestypreset: base URLhttps://router.requesty.ai/v1,openai-compatibleprotocol,api_keyauth, a few curatedprovider/modeldefaults, and meta doc links. Because the base URL ends in/v1and the preset isn't catalog-only, Requesty automatically flows through the generic/v1/modelssearch-and-add path (canReliablyFetchModels/discoverModels) — no dedicated catalog fetcher needed.src/lib/provider-icon-rule.ts— added"requesty"toProviderIconKeyplus a brand-scoped matcher (requesty.aihost /requestyname).src/components/settings/provider-presets.tsx— added aRequestyIconand wired it into the icon maps (the model-selector already referenced arequestylogo slug; this makes the backend match it).OpenRouter's preset uses the
openrouterprotocol (an Anthropic-skin for the Claude Code SDK). Requesty's gateway is OpenAI-compatible, so the faithful mirror is a brandedopenai-compatiblepreset, exactly like the existing branded OpenAI-compatible presets in the catalog.Verification
tsc --noEmit: clean before and after.test:unit: 4540 pass / 0 fail.openai/gpt-4o-mini→ 200;GET /v1/models→ 200 with 596 models (context_window/supports_tool_callingfields present).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.