Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

Semantic Router's DecisionRouter sends a message as state with a route question to TypeSafe's System One endpoint. Jev returns probabilities for the named route choices. The router uses those probabilities as route scores, then returns the highest route if it clears the configured confidence threshold. Its aask method can send several typed questions about the same state in one request.

What Jev decides

Illustrative route and urgency questionsExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION

Choose the route that best fits the user's message.

STATE

Example state from the repository's live integration test: a user reports failed payouts for three days. The question criteria use the repository's billing, technical, and support routes.

JEV · CHOICE
  1. billing
  2. technical
  3. support
Question 2 · urgent
YOUR APP
INSTRUCTION

Decide whether this issue is time-sensitive, distinguishing action needed now from a case that can wait.

STATE

Example state from the repository's live integration test: a user reports failed payouts for three days. The question criteria use the repository's billing, technical, and support routes.

JEV · NOUL
YesNo

App workflow

  1. Define routes

    Provide route names and descriptions or example utterances.

  2. Build the request

    DecisionRouter uses route descriptions as choice criteria, falling back to up to five example utterances when a description is absent. It sends the message as state and one or more named questions.

  3. Call Jev

    The router posts the model, state, and questions to the TypeSafe System One endpoint with bearer authentication. It retries rate-limit, server, timeout, and client errors within its configured retry count.

  4. Use the answer

    Route probabilities become route scores. The base router selects the highest-scoring route when it meets the configured threshold. Callers can also inspect answers to additional questions.

  5. Optional fallback

    Chain can try an indexed semantic router first and pass only uncertain messages to DecisionRouter.

Why it is interesting

It lets an application replace a slow generative routing step with closed decisions that return calibrated probabilities. The same request can select a route and check a separate condition, and the library can fall through from a fast semantic router to Jev when the first router is unsure.