01
Constraints before scores
Models that violate risk, boundary, modality, context, cost, or latency requirements are rejected before ranking.
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.
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.
I used this — send feedback
No accountNo prompt custodyDeterministic resultOpen contract
BUILT FOR MULTI-PROVIDER TEAMS
A routing decision your team can inspect.
02
Visible tradeoffs
Choose balanced, quality, cost, or latency. Component scores show exactly why the winner moved.
03
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.
04
Receipts without bodies
Local runs produce correlation digests, events, route facts, and usage without placing task or output text in receipts.
LOCAL JOB MODE
Make a multi-step route legible before anyone runs it.
Plan-only timeline
A sanitized fictional local manifest routes each ordered step with caller-supplied catalog evidence and explicit policy. It does not infer a phase from task text, learn from transcripts, or use phase labels as scoring inputs.
External handoff is visible
Read steps can be marked eligible. Write-capable or side-effecting steps are labeled as external handoffs, not executed by Nymrel Agent.
Lifecycle stays local
Callers can retain a bounded digest-and-ordinal checkpoint chain. Nymrel Agent returns the next envelope; it stores nothing and runs no background job.
Fictional 48-hour game builder · local plan only
1 research-scope objective:quality model:provider-b/fast deps:none read-only eligible
2 plan-slice objective:balanced model:provider-b/fast deps:research-scope read-only eligible
3 build-prototype objective:balanced model:provider-b/fast deps:plan-slice EXTERNAL HANDOFF
4 review-build objective:quality model:provider-b/fast deps:build-prototype read-only eligible
5 release-handoff objective:quality model:provider-a/reasoning-large deps:review-build EXTERNAL HANDOFF
Policy and caller-supplied evidence drive each selection. Phase labels do not affect scoring.Download the sanitized fictional manifest · Download the deterministic summary
The hosted API remains metadata-only routing. Job Mode, Lifecycle, and MCP planning have no hosted endpoint, provider call, or customer-data persistence.
THE LOCAL-FIRST 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