Astralane / Developers
Routing and auto selection
Hard eligibility filters first. A deterministic score second.
Eligibility
Routes must satisfy model/key restrictions, approved/enabled account and supplier state, privacy, region, tools/context/output constraints, public price ceiling, platform margin, health, and Redis-backed capacity admission. Candidates are rechecked at admission.
Policies
cheapest prioritizes customer cost; fastest emphasizes predicted latency; balanced weighs cost, reliability, and latency; quality favors configured quality tiers. The model aliases auto, auto/fast, auto/balanced, and auto/best select from eligible models using deterministic prompt/task heuristics.
Workspace restrictions
Workspace and request provider allowlists and regions are intersected. Blocklists are combined. ZDR is a logical OR; max request cost is the stricter ceiling. A request cannot weaken the workspace privacy or price policy.
No trained orchestration claim
This version does not train a router, run an LLM classifier, or launch multi-agent verification. The standalone routing package is designed so its selector can be replaced later.
Native core and mock HTTP checks have run. Full dependency install, PostgreSQL/Redis integration, production builds, and browser flows still require local verification. See the repository verification report before deployment.