Skip to content

feat(providers): add EURouter as an OpenAI-compatible gateway (147 models, passthrough) #12985

Closed

Description

@diegosouzapw

Feature Request

Source: Discussion #12944 by @dfigos-2000 (live curl evidence supplied by the reporter)

Summary

Add EURouter as an OpenAI-compatible API-key gateway. Not on docs/reference/REMOVED_PROVIDERS.md.

Verified against the live API (2026-09-07)

Check Result
GET https://api.eurouter.ai/api/v1/models HTTP 200, 274 KB, 147 models, no auth required
GET https://api.eurouter.ai/v1/models HTTP 200 — the short path works too
POST /v1/chat/completions with a key HTTP 402 Insufficient balance — auth accepted, account had no credits
Catalog shape OpenRouter-style: canonical_slug, hugging_face_id, architecture, context_length, top_provider, pricing, per_request_limits, supported_parameters, supported_api_endpoints, providers, tags

So passthroughModels: true is viable and the base URL can be https://api.eurouter.ai/v1.

Implementation

Registry entry in src/shared/constants/providers/apikey/gateways.ts — the mnn-ai / meganova-ai shape. No executor, no translator.

Still to confirm before merge:

  1. Streaming SSE conformance — not exercised (the test account had no credits). This is where "OpenAI-compatible" gateways usually diverge, and a passthrough entry breaks there silently.
  2. Free tier, if any, for freeNote — precise, published sources only.

Sovereignty caveat — must be recorded, not implied away

EURouter is a router, not an inference provider. Its own catalog says so: anthropic/claude-sonnet-5 carries providers: [{ "name": "AWS Bedrock", "slug": "aws-bedrock" }]. Upstream owners across the catalog include openai (19 models), anthropic (9), amazon (7), alongside mistral (24), alibaba (21) and zhipu (18).

An EU-based router is a routing layer in the EU. Where a given model actually executes, and under whose terms, is a per-upstream property. The registry entry must not carry freeNote/apiHint copy implying EU data residency for inference.

This is also the concrete case for #12938: the providers[] field per model is exactly the per-upstream granularity the tri-state trainsOnPrompts flag needs. A single gateway-level value would be wrong here.

Acceptance criteria

  • Registry entry with passthroughModels: true, base https://api.eurouter.ai/v1
  • Streaming verified against a credited account before merge
  • apiHint states plainly that it is a router and that inference may run outside the EU
  • Unit tests under tests/unit/

Additional Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions