Skip to content

The models the world offers, declared once and routed with reasons

One declared catalogue of vendors and models — capabilities, context, lifecycle, no fabricated facts — and a routing answer that names why every candidate was chosen or excluded.

status
feature status: stable
domain
Coordination
on the homepage
featured

What it does

share/models.yaml declares the vendors and models this tool's world can name: canonical ids, the vendors' native ids, aliases, typed capability words, context windows and lifecycle standings, in an order that is also routing's preference. majordomus models list renders the catalogue with each vendor's credential-presence; majordomus models route --require vision,tools --min-context 500000 answers which model qualifies first, which stand behind it as the fallback chain, and why every other model fell out — the same answer over HTTP, OpenAPI, the MCP tools and the Cockpit's Models page, because all of them project the same two capabilities. The catalogue's own findings — a duplicate alias, an undeclared vendor — ride along in every listing.

What it does not do

It calls no model and reads no secret: credential facts are the presence of a named environment variable, never a value, and the catalogue's schema has no field a secret could hide in (a test holds it). It states no price and no unverified vendor — what cannot carry provenance stays absent. And it does not yet record which model actually executed a session's work; that belongs to the capture adapters, whose schema already declares the fields (ADR 0049 names it as the follow-up).

How it works

The capability modules of the executable this feature names, each with the capabilities it composes. The interfaces each one reaches are listed under Interfaces below: they are projections of one declaration, not separate registrations.

Models models experimental

The model catalogue the distribution declares — vendors, canonical model references, typed capabilities, context windows, lifecycle — and the explainable routing over it: what a stated need selects, what stands behind it, and why every excluded model fell out. Declared data; nothing here calls a model or reads a credential's value.

Where it sits

domain
Coordination — Every worker declares the paths it will touch, sees who else is working and where, and hears about a collision before it is committed.
areas of work
coordination
names
Mesh
named by
EconomicsReasoning

Interfaces

Each capability behind it, on every interface it is projected onto. A link goes to this site's reference for that interface; an HTTP route and an MCP tool are answered by a running majordomus serve, not by this site.

The capabilities behind this feature, by interface
capabilitycommand lineHTTPMCP tool
models.list majordomus models list GET /api/v1/models majordomus_models
models.route majordomus models route GET /api/v1/models/route majordomus_models_route
in the Cockpit, of a running server
/cockpit/models Models

Evidence

What is guaranteed

Each claim this feature names, with the status its row declares, the verdict the recorded runs support, and the test that settles it.

The decisions behind it

Using it

From the executable's command line

The synopsis of each, as the executable's own help prints it.

Where this page comes from

the file
.ai/repo/features/models.md
the same answer
majordomus product show models
read further

The model catalogue

Searches the titles and descriptions of every page this site publishes.