The problem is not “yet another playground.” The problem is every blueprint inventing its
own provider client. MVS is the routing layer: mvs.router.dispatch() reads
active config (primary + optional fallback), hits OpenRouter / Ollama / MiniMax /
DeepSeek, normalises output (fences, <think>, sycophantic preambles). External:
POST /api/v1/chat with X-MVS-App-Token. Internal:
shared.ai_helpers.dispatch API(..., via_mvs=True) hits localhost /api/v1/dispatch
and falls back direct if MVS is down. Dashboard: live monitor, today’s totals, top apps. Test UI
with provider override, PRL load, saved labels. Per-app hashed tokens. Costs to
the call log and ai_operations_log. FMR provisions models here. EBD/EBI
score via the MVS client. OpenRouter adapter is on purpose.
If MiniMax 402s, fallback config is the next hop — not a silent empty string dressed as success.
Not OpenRouter usage dashboard screenshots.
PRL library load + saved run label. Not ChatGPT.
Public landing never prints a live token.
FMR finds. OMR tracks :free chain. MVS serves.
Will not be the A3 image generator. Will not hide adapter failures as empty 200s if the caller asked via_mvs.
Platform inference spine. Humans use the test UI; apps use dispatch().
No invented fifth vendor.
Login for /mvs/app. This page is not a free playground.
Open MVSRequires a MelTuc account. Create one free.
Model vault — providers, models, tokens, and unified chat/dispatch. Platform default usually MiniMax when active. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.