Contribution proposal: optional API Route configuration or provider integration

[DennyHo0917]

I maintain API Route, a paid hosted gateway exposing an OpenAI-compatible API at https://global.api-route.com/v1.

I would like to contribute a small, optional integration for users who already use API Route. I am opening an Ideas discussion before implementation, as requested by your contributing guide and issue-template configuration.

Possible scope

1. A configuration recipe using the existing OpenAI Compatible provider. Document the endpoint, API key, model discovery and a verified chat example. Keep the existing provider list unchanged. The guide would clearly distinguish chat models from embeddings and avoid implying support for untested model types.
2. A named provider, if useful to the project. Following the recently merged SiliconFlow/Z.ai integration #1443, first contribute the corresponding support to Esperanto if needed, then add provider registration, isolated credentials, authenticated model discovery, tests and setup documentation in Open Notebook.

Neither option would change the default provider, bundle credentials, or make API Route required. I would verify actual requests and only claim the capabilities that pass those checks.

Questions

• Would an API Route contribution fit your current scope?
• Would you prefer a short setup recipe, a named integration, or no additional gateway entry?

If the proposal is accepted, I will wait for an approved/scoped issue before implementing a new feature.

References: quickstart, API keys, pricing.

Disclosure: I maintain API Route. No implementation PR has been opened.