mivia-small-json, measured.

mivia-small-json is a compact structuring engine: give it any text and any output schema and it returns a strictly valid record, never a refusal, never invalid JSON.

input

any text, any language, multi-line dumps

output

strictly valid record + routing metadata, or a typed clarification

deepest

coding workflows: issues, commits, logs, diffs, diagnostics, tool calls

runtime

int8 onnx · cpu only · sha256-verified at load · no data egress

A decision pipeline of small, specialized models.

Each model is trained for one job; the stack composes them. Pick a stage to see what runs inside it.

1. 1input
2. 2schema router
3. 3schema selection
4. 4specialists
5. 5json out

What it can do.

One record type per input, every time.

Strictly validated fields per outcome; general text is a first-class record, not a failure. Pick an outcome to see its shape.

{
  "type": "tool_call",
  "name": "calculate_sum",
  "arguments": "{\"num1\":15,\"num2\":30}",
  "result": "…"
}

Measured, then published.

All numbers are measured on frozen, never-trained-on evaluation sets on CPU, and independently re-verified. Every number names its set; nothing on this page was measured on training data.

Where it earns its keep.

Eight production patterns, each with a real input and the real output from the shipped artifact, plus the measured surface that backs it.

in   "calculate the sum of 15 and 30"
out  {"type": "tool_call", "name": "calculate_sum",
      "arguments": "{\"num1\":15,\"num2\":30}"}

in   "calculate the sum"
out  {"type": "tool_clarification", "tool": "calculate_sum",
      "missing_parameters": ["num1", "num2"],
      "clarification_prompt": "Please provide num1, num2 to use calculate_sum."}

in   "explain quantum entanglement in physics"
out  {"type": "no_tool_call", "reason": "no matching tool"}

Built-in honesty guarantees.

A structuring API that guesses is worse than one that asks. The output contract makes honesty mechanical: these are properties of the release, pinned by the test suite, not aspirations.

The in / never / always rows sketch the shipped contract; they are illustrative, not a request trace.

Interfaces.

// a german incident ticket, answered locally in milliseconds
{
  "text": "Hinweise auf Schwierigkeiten bei der Datenregistrierung"
}
→ { "records": [ { "result": { "type": "issue",
                         "title": "Hinweise auf Schwierigkeiten bei der Datenregistrierung" },
                    "meta": { "valid": true, "routed_by": "model" } } ] }

// any text is a first-class outcome: same surface, same json contract
{
  "text": "Danke, dass du mir letzte Woche geholfen hast!"
}
→ { "result": { "type": "text" },
     "meta": { "valid": true, "routed_by": "model" } }

// what goes in, what comes out
in    text
out   structured records + routing meta

bearer auth · streamable-HTTP MCP at /mcp · single docker image

Footprint & guarantees.