Playground/Tool router
API ACTIVITY

Usage & budget

Your TypeSafe API key

Import your key to override the shared server default.

Saved on this browser until removed or site data is cleared. Masked on screen; sent only with Jev requests through this app. The saved value is never displayed.

Connecting
LANGGRAPH-STYLE · MOCK EXECUTION

Jev tool router

Find the right tool for a request. Follow each decision, approval, and policy stop.

WORKSPACE GUIDE

Tool router

Follow a request through a graph with blocked tools and approval stops.

RequestPolicy gatePermitted step

What you provide

A request, a starting graph node, and the demo's policy. Available next nodes depend on the current position.

What happens

Policy excludes forbidden candidates before selection. Jev or the seeded mock chooses a next node; confidence and approval gates can stop the path.

What you get

The permitted next step, simulated tool output, and a trace of each edge. Decision details expose confidence, selection probability, and policy overrides.

Walk through a run

  1. 01

    Choose a request

    Try reading settings, changing production, or requesting a secret.

  2. 02

    Follow the path

    Run a live routing step or the complete seeded mock scenario. Continue from the decision to follow another edge.

  3. 03

    Inspect the stop

    Review policy blocks and approval checkpoints. Expand the inspector for candidates and the full graph. Open Decision details or Step evidence for scores.

Try this

Compare reading settings with modifying production. Follow the path until the approval checkpoint, then try a request for secrets.

Execution limits

Live Jev chooses a node; mock mode uses seeded choices. All agent and tool execution is simulated.

Explore the example. Check the evidence.
Choose a requestCheck the next stepFollow the pathAll execution is simulated

Your request

Expected demo path: Operations → read configuration → complete. No approval required.

Live step: Jev chooses. Mock scenario: seeded choices. All execution is simulated.

Routing inspector

Available next nodes

Start
Research agentresearch_agent

Investigate concepts, compare approaches and answer research questions.

Support agentsupport_agent

Help with product usage and customer support problems.

Operations agentops_agent

Inspect or change service settings and production configuration.

Needs clarificationneeds_clarification

The request is ambiguous, unsupported, or cannot be routed confidently.

View the full workflow
Start → choose a specialist
Research agentagent
  • CompleteAllowed
Support agentagent
  • CompleteAllowed
Operations agentagent
  • Read configurationAllowed
  • Modify configurationPause for approval
  • Export secretsAlways blocked

Permitted tools lead to Complete. Needs clarification is always available. Policy may stop a request before any graph step.

How policy overrides Jev
  1. Sensitive-data keywords block the entire request before any model call.
  2. Always-blocked nodes are removed from the candidate set.
  3. Both Jev scores must meet 85%; otherwise the path stops for clarification.
  4. Configuration changes pause for explicit mock approval.

The keyword rule is intentionally broad for this demo. It is not a complete production intent detector. The fixed graph also makes secret export impossible regardless of phrasing.

The next step

RequestPolicy gatePermitted step

See the decision, then follow the path

Run one live routing step, or try the full seeded scenario without an API call.