01
Constraints before scores
Models that violate risk, boundary, modality, context, cost, or latency requirements are rejected before ranking.
EXPLAINABLE MULTI-MODEL ROUTING
Nymrel Agent selects a model from your catalog using explicit health, risk, capability, data-boundary, cost, and latency constraints. The public router never receives prompts or provider credentials.
ONE CORE, THREE SURFACES
The hosted endpoint routes metadata only. The CLI can route locally. The MCP server lets compatible agents ask Nymrel Agent for the same explainable decision.
{
"ok": true,
"plan": {
"selectedModelId": "provider-b/fast",
"objective": "balanced",
"decisionCodes": [
"objective_balanced",
"eligible_candidates_ranked",
"deterministic_tie_break",
"model_selected"
]
}
}
DESIGNED FOR OPERATORS
01
Models that violate risk, boundary, modality, context, cost, or latency requirements are rejected before ranking.
02
Choose balanced, quality, cost, or latency. Component scores show exactly why the winner moved.
03
The hosted service accepts routing metadata only. Optional live execution runs locally with your own provider account.
04
Local runs produce correlation digests, events, route facts, and usage without placing task or output text in receipts.
THE V0.1 BOUNDARY
The public product routes; it does not execute model calls. The local harness executes read-only requests through configured adapters. Write-capable tools, hosted provider-key custody, billing, and autonomous side effects are outside this release.
Read the security model →NYMREL IMPLEMENTATION SERVICE
We configure evidence-backed model catalogs, routing policies, evals, local provider adapters, and operational receipts around your workflow. Scope and pricing are provided on request.
Start a brief