Skip to main content
PRYSM’s routing engine receives a prompt and returns a routing decision in under 5 ms — before any model call happens. This post explains how it works.

The ten intent signals

The classifier scores each prompt on ten dimensions simultaneously (no sequential calls, no embedding round-trips):
Each signal produces a float in [0, 1]. The final routing decision combines signal strengths with the chosen routing mode.

Routing modes

The decision logic

The fallback chain

If the selected provider has no API key configured, the engine falls back through providers in cost order:
This means a deployment with only DEEPSEEK_API_KEY still gets cost-optimized routing — it just uses DeepSeek’s full model lineup.

Dry-run: see the routing decision

PrysmProof: cryptographic attestation of every decision

Every response includes a prysm.proof field:
The hash is sha256(request_id + timestamp + model + provider + mode + prompt_sha256 + response_sha256)[:16]. Verify offline:

Benchmarks

All measured on a single-core container, no GPU. The classifier is a pure Python bitfield operation over pre-compiled signal patterns — no embedding calls, no ML inference.