Orchestrator · Layer 3
Walt gives your tools one endpoint to call for AI. Behind it he decides which model answers, records what each request cost, and also builds and ships releases.
Apps and services send requests to Walt in a familiar messages-style API. They don't need to know which provider or local model sits behind it.
Requests go through the carousel to local models on Ollama or to cloud providers such as OpenRouter, Groq and Anthropic, picked by cost and capability.
Every request is metered, so you can see what each call, project and provider actually cost.
Callers present a Grant-issued token or a shared ingress key. Walt uses his own upstream provider credentials, so callers never pass provider keys through.
Walt builds a release from a specific commit, runs a smoke test and writes a manifest, so what you ship is what you tested.
Providers and routing rules live in config files. Change the plan by editing a file, not by rebuilding.
A request takes four steps, and Walt owns all of them.
Walt sits in layer 3. He doesn't call the other layers directly: Grant decides who may call him, and the cost and request events go out on the bus where Mona shows them.
Copyright (c) 1998-2026 spw1.com and steven p williams All Rights Reserved