Multi-LLM routing system manages 16 AI models across 5 providers for cost and reliability

·4 views

A system called geo-orchestrator routes natural language tasks across 16 AI models from five providers including Anthropic, OpenAI, Google, Perplexity and xAI. Each of the 23 task types follows an ordered chain of models with primary and fallback options from different vendors to ensure reliability. The routing considers multiple factors including budget constraints, provider health, historical quality, cost, and latency. A FinOps component enforces spending limits per run, per day, and per provider with alert mechanisms. The system's current state as of October 7, 2026, includes 962 passing tests across all task types.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Industry expert advises defining clear workflow purpose before building MVP

A software development expert recommends establishing a clear purpose for a single workflow before defining an MVP's features. The advice involves writing a specific sentence outlining who needs to complete what task and why in a given situation. This approach helps identify the essential information and functionality needed, while separating useful but non-critical ideas for later development. The method aims to ensure the initial product directly serves the core user need.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Financial AI needs document-specific retrieval, not just chatbots, to ensure accuracy.

The Vicquant financial app's AI never performs calculations itself, only explaining results generated by deterministic code. However, to prevent inaccurate answers about user documents, it requires a specialized RAG Vault for retrieval. Standard text-splitting methods fail on financial documents containing tables, necessitating layout-aware parsing. The system uses hierarchical chunking and hybrid search techniques to precisely find and provide relevant context for accurate responses.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Minimal TypeScript sketch illustrates SAL protocol for autonomous agent lifecycle

A minimal TypeScript implementation has been published to demonstrate the core flow of the Sovereign Agent Lifecycle (SAL) protocol. The sketch shows an agent generating its own cryptographic keypair, initializing in an orphan state, and proving possession through a challenge-response mechanism. After verification, the agent can request short-lived, scoped access tokens for specific services. This approach differs from traditional API key systems by enabling self-generated identities and fresh, limited-scope authentication. The public specification is available at sal-protocol.dev, with a reference implementation in Vibebase.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Power Apps Code App licensing costs scale with user count, not app complexity

Microsoft Power Apps Code Apps require a Premium per-user license, not a per-app or free license. Accessing Dataverse through these custom applications is not covered by standard Microsoft 365 licenses most companies already own. Consequently, licensing costs are determined by the number of users, making a simple app for thousands of employees potentially more expensive than a complex one for a small team. Experts advise confirming user licenses before development begins, as procurement can be lengthy, and oversight can lead to significant, unexpected expenses.

0 comments Read more at DEV Community