FOR MULTI-PROVIDER TEAMS

See which model wins under your constraints.
Keep prompts and keys out of the hosted router.

For teams using multiple model providers and strict data boundaries. Send request constraints and caller-supplied catalog metadata; get a deterministic route plan with rejection reasons and a visible tradeoff. Use the customer-local harness when you want to call a configured provider.

Run the live route Use the API, CLI, or MCP

route-decision.txt

LIVE ROUTE · METADATA ONLY

Ready on the public router.

REQUEST
  workspace_write · tool_use · structured_output
  ≥32k context · approved_provider · ≤50,000 µUSD · ≤10,000ms

REJECTED  local/text-small
  context_too_small · data_boundary_unsupported
  risk_class_unsupported · tool_use_unsupported

RANKED
  8,810  provider-b/fast             WINNER
  7,373  provider-a/reasoning-large

TRADEOFF · CALLER-SUPPLIED CATALOG EVIDENCE
  8 fewer catalog quality points for 30,000 µUSD lower catalog cost,
  3,300ms lower catalog latency, and 90 bp higher catalog reliability.

Quality, reliability, cost, and latency are caller-supplied catalog facts—not Nymrel benchmarks. No prompt, provider key, or output body is sent to Nymrel’s hosted router.

No accountNo prompt custodyDeterministic resultOpen contract

BUILT FOR MULTI-PROVIDER TEAMS

A routing decision your team can inspect.

Constraints before scores

Models that violate risk, boundary, modality, context, cost, or latency requirements are rejected before ranking.

Visible tradeoffs

Choose balanced, quality, cost, or latency. Component scores show exactly why the winner moved.

Low-custody by default

The hosted service accepts routing metadata only. The optional customer-local harness makes provider calls in your environment with your provider account.

Receipts without bodies

Local runs produce correlation digests, events, route facts, and usage without placing task or output text in receipts.

THE V0.1 BOUNDARY

Useful now. Honest about what is next.

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 →

OPTIONAL IMPLEMENTATION HELP

Need this fitted to your model stack?

Nymrel can configure your catalog, routing policy, evals, local adapters, and body-free receipts. Scope and pricing are provided on request.

Tell us about your setup

See which model wins under your constraints.Keep prompts and keys out of the hosted router.