@velum-labs/routekit-gateway
v1.3.2
Published
Product-neutral model router, provider egress, wire dialect translation, streaming, catalog, and call provenance.
Maintainers
Readme
@velum-labs/routekit-gateway
Product-neutral model routing and provider egress for RouteKit.
The package owns the Backend interface, HTTP gateway, OpenAI Chat,
Responses, Anthropic Messages and Cursor adapters, SSE handling, ACP support,
normalized call provenance, model catalogs, provider sources, and
provider-native egress. Canonical router configuration belongs to
@velum-labs/routekit-config-core.
At startup RoutingBackend authenticates every explicitly configured provider,
performs live model discovery, and publishes source-qualified
provider/model IDs. Dispatch removes the source prefix before provider-native
egress. An unavailable provider fails startup rather than silently shrinking
the catalog.
import {
RoutingBackend,
startGateway
} from "@velum-labs/routekit-gateway";
import { parseRouterConfig } from "@velum-labs/routekit-config-core";API-key providers use registry-defined credentials and URLs. Multi-account
subscription providers and relays are in @velum-labs/routekit-accounts; they expose the
same source interface with per-model account eligibility and quota-aware
selection. RouteKit hosts wire this package into the singleton daemon gateway.
Compositional routing accepts explicit named repository selectors as
model: "auto:<name>", or as x-routekit-routing-profile: <name> with
model: "auto". The host supplies trusted repository context (the singleton
uses its repository-bound launcher credential); request headers never select a
filesystem root. The gateway rejects malformed, unbound, and conflicting
selectors before routing.
