Repository navigation
Proposal: API Route as an optional OpenAI-compatible provider #1061
Closed
DennyHo0917
started this conversation in
Proposals
Replies: 1 comment
|
Hi @DennyHo0917, thank you for asking before you started, and for being open about your affiliation. We've looked into API Route and decided not to add it as a provider to AI Studio. The way API Route provides access to the models it offers conflicts with the goals and values of our project, and with what our users, many of them organizations in Europe, expect from the providers we support. We wish you all the best. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi! I’m affiliated with API Route and would like to ask whether an optional API Route provider would fit AI Studio’s plans before implementing it, as requested in CONTRIBUTING.md.
API Route provides an OpenAI-compatible endpoint at https://global.api-route.com/v1. The proposed integration would let users select API Route, enter their own key, discover available models and chat through the existing compatible transport, following the recently merged Requesty provider (#1006). It would not change existing users’ provider selections.
I would keep the change focused and include provider tests and setup documentation. I understand EU routing was valuable in the Requesty discussion; this proposal is for the global endpoint and does not claim EU-only processing.
Would you welcome this provider, and are there any inclusion requirements I should address first? Thank you.
All reactions