OrcaRouter provider support for LeanType

[armyluki-wq]

Project value / context

LeanType is a thoughtful evolution of the open-source Android keyboard: it keeps HeliBoard's lightweight, privacy-first base and layers proofreading, grammar, rewriting, translation, and OCR on top while making network access optional — the Offline flavor ships with no Internet permission at all. That is a level of user control worth supporting.

Your Multi-Provider Cloud AI design is what makes this relevant: under Settings → AI Integration → Set AI Provider, users already choose Gemini, Groq, OpenAI, or a Custom OpenAI-compatible endpoint, and LeanType auto-fetches the available model list. Since users pick providers freely, each additional compatible provider is a real choice rather than friction.

Is your feature request related to a problem?

Not a bug — an opportunity. Cloud-flavor users configure a single provider key and are tied to its models, pricing, and uptime; when it rate-limits or drops a model, they must switch endpoints and keys by hand.

Describe the solution you'd like

I'd like to propose OrcaRouter as an optional additional provider, sitting alongside Gemini, Groq, and OpenAI without replacing or altering any existing provider.

I'm an engineer on the OrcaRouter team. OrcaRouter exposes an OpenAI-compatible API and uses standard API-key authentication, so it maps onto LeanType's existing OpenAI-compatible abstraction — the "Custom (OpenAI-compatible)" path under AI Integration. Users point it at OrcaRouter's base URL, paste a key, and dynamic model fetching populates the model list, so it works today with no code change; a dedicated preset would reduce setup to one tap. Nothing is implemented or tested yet; this issue asks whether maintainers would welcome a preset or a follow-up PR.

For LeanType users the appeal is one key in front of many chat and reasoning models, automatic routing with provider failover when an upstream provider is down or rate-limited, and per-key usage tracking with budgets.

Use case

A Standard Full user who proofs long emails could set OrcaRouter as their AI provider and get automatic failover at peak hours instead of manually swapping Groq/Gemini keys, with budgets as a hard cost cap.

Alternatives considered

Users can already type a custom OpenAI-compatible base URL manually; OrcaRouter's added value is routing/failover, usage visibility, and budgets. Staying strictly additive and never the default respects LeanType's optionality guidelines.

Ecosystem & disclosure

OrcaRouter is already integrated into open-source projects including Dify, goose, and promptfoo (see the built-with page). OrcaRouter also runs an optional open-source partner program: approved OSS projects can receive a 5% revenue share from usage attributed to their integration. Participation is not a prerequisite, and I'm happy to follow LeanType's disclosure and governance rules.

App version & Flavor

Relevant to cloud/online flavors (Standard Full / Standard FOSS) with Multi-Provider Cloud AI; the Offline flavor is unaffected.

I'd welcome maintainers' thoughts on an OrcaRouter preset, and I'm glad to open an implementation PR if you approve the direction.