Skip to content

feat: add Requesty client options mirroring OpenRouter#158

Open
Thibaultjaigu wants to merge 1 commit into
magnitudedev:mainfrom
Thibaultjaigu:add-requesty-provider
Open

feat: add Requesty client options mirroring OpenRouter#158
Thibaultjaigu wants to merge 1 commit into
magnitudedev:mainfrom
Thibaultjaigu:add-requesty-provider

Conversation

@Thibaultjaigu

Copy link
Copy Markdown

This adds Requesty client definitions, mirroring the existing OpenRouter clients in clients.baml.

Requesty is an OpenAI-compatible LLM gateway, so the clients use the same openai-generic provider as the existing GeminiProOpenRouter / GeminiFlash clients, pointed at https://router.requesty.ai/v1 with REQUESTY_API_KEY.

Changes:

  • packages/magnitude-core/baml_src/clients.baml: add GeminiProRequesty (model google/gemini-2.5-pro) and GeminiFlashRequesty (model google/gemini-2.5-flash), parallel to the OpenRouter clients.

Verification: I tested the endpoint live before opening this. Chat completions for both google/gemini-2.5-pro and google/gemini-2.5-flash against https://router.requesty.ai/v1/chat/completions returned 200.

Docs: https://requesty.ai , https://app.requesty.ai/api-keys

I work at Requesty. This mirrors the existing OpenRouter clients as closely as possible. Happy to adjust or close it if it is not a fit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant