OPEN-SOURCE GATEWAY
Two ways to get a decision out of a local LLM
- Model writes a sentence
- You regex or JSON-parse it
- Confidence uncalibrated
- Extra tokens, extra latency
vs
- Answer set defined up front
- Probability per option
- Calibrated, no parsing
- No fine-tune, same server
hearim wraps the endpoint you already run — the answer set becomes the API, not the prose.
Fronts llama.cpp, vLLM, SGLang or Ollama for routing, relevance and moderation gates.
Why it matters: Classification-style steps in an agent pipeline (routing, relevance scoring, moderation gates) are often served by full text generation you then parse — slower, costlier, and less calibrated than getting a probability distribution directly from a model you already run.
How to apply: Point hearim at your existing local/hosted model server, define the allowed answer set, and swap out open-ended classification calls in your pipeline for its decision endpoint instead of building a proprietary decision-API integration.
local-llmagentsclassification