Classify
Scores task type, complexity, context shape, and failure cost before every call.
The drop-in optimization layer that cuts agent fleet model spend by up to 90% without touching your orchestration logic.
+ client = OpenAI(base_url="https://api.hamblygmen.space/v1")One endpoint. No agent rewrite. Hamblygmen observes the signals your harness already produces and makes a better execution decision in milliseconds.

The built-in eval runs 45 rubric-graded agent calls through four routing strategies. Same prompts, same gateway, same grading — only the routing differs.
| Strategy | Pass rate | Cost | vs frontier |
|---|---|---|---|
| frontier-only | 91.1% | $0.366 | baseline |
| random routing | 80.0% | $0.118 | −11 pts quality |
| cheapest-only | 53.3% | $0.002 | −38 pts quality |
| hamblygmen | 82.2% | $0.147 | 90% quality · 40% cost |
Run it yourself: node src/cli.ts eval — the eval is built into the gateway, not a marketing page.
Optimize for the actual work—not a static provider preference or one-size-fits-all model tier.
Scores task type, complexity, context shape, and failure cost before every call.
Selects the fastest, lowest-cost model that still clears the required quality bar.
Detects semantically equivalent work across agents, loops, and retries before spend occurs.
Builds a private performance map for each harness and task pattern over time.
Adjust the operating profile. Estimates use 400 runs per agent per month and 2.2K tokens per turn.
Your orchestration remains the source of truth. Hamblygmen makes each model call more efficient and dependable.
| Capability | Hamblygmen | Generic LLM router | Orchestration framework |
|---|---|---|---|
| Agent loop awareness | — | Varies | |
| Quality-bar routing per task | Basic | — | |
| Semantic cache + deduplication | Optional | — | |
| Replaces your agent architecture | — | — | |
| Learns per-harness performance | — | — |
Start with one client call, then take the same control plane into your most demanding environments.
// unchanged harness code
+ OpenAI(base_url="https://api.hamblygmen.space/v1")
→ classified
→ routed
→ observed
Keep the harness you built. Add an intelligence layer that learns where every request should run.