← All use cases

Tool-call risk gate

Screen an agent's action before it runs.

Refund gate · thresholds 0.9 / 0.1 · <$0.0001, <600msOpenRouter cookbook

OpenRouter's official cookbook builds this exact gate for refunds: it hands Jev the policy, the ticket with order records, and the proposed refund call, then asks a few noul checks (did the customer ask for a refund? does the order match? does policy cover this amount?). Plain Python keeps control — if every check is ≥0.9 the call runs, ≤0.1 it's blocked, anything in between goes to a human. In their runs a decision cost under $0.0001 and returned in under 600ms, so a safe refund clears instantly and only the genuinely ambiguous 0.41 case reaches a person.

Live toolRun this on your own data with the Agent Risk Checker →

Try it live

This is the real thing, not a mockup. Edit the input, hit Run, and Jev returns every typed answer in one round trip — free, no signup. Now picture the same call fired across thousands of items in parallel.

POST jevtypesafeai.com/api/v1/decide
state — the input software gives Jev200c
questions — the typed decisions you want back
scorerisk
How risky is it to run this command automatically?
→ 0…3 · 4 levels
noultouches_prod
Does this action touch production or delete data?
→ probability 0.0 … 1.0
choicegate
What should the agent harness do?
→ one of: allow, confirm, block
real API · free · no signup
Typed, calibrated output appears here.
Pick a demo, tweak the input, and hit Run Jev.
Get an API key →← All use cases

The decisions Jev makes

In a single call, Jev evaluates each of these — in parallel, against the same input:

scorerisk

How risky is it to run this command automatically?

rates it on an ordered scale:

  1. safe
  2. low
  3. needs a careful look
  4. high — could destroy data or affect prod
noultouches_prod

Does this action touch production or delete data?

returns a calibrated yes/no probability.

choicegate

What should the agent harness do?

picks one of these options:

  • allow — run it automatically
  • confirm — pause and ask a human to confirm
  • block — block and require a safer approach

The exact request

This is the real payload behind the live demo — copy it, change the state, and you're building:

{
  "model": "jev-latest",
  "state": "An autonomous coding agent is about to run this shell command in the project root:\n\n  rm -rf ./dist && aws s3 sync ./build s3://prod-assets --delete\n\nContext: it's mid-task deploying a frontend build.",
  "questions": {
    "risk": {
      "type": "score",
      "instructions": "How risky is it to run this command automatically?",
      "criteria": [
        "safe",
        "low",
        "needs a careful look",
        "high — could destroy data or affect prod"
      ]
    },
    "touches_prod": {
      "type": "noul",
      "instructions": "Does this action touch production or delete data?"
    },
    "gate": {
      "type": "choice",
      "instructions": "What should the agent harness do?",
      "criteria": {
        "allow": "run it automatically",
        "confirm": "pause and ask a human to confirm",
        "block": "block and require a safer approach"
      }
    }
  }
}

Wire it into your code

Read the typed answers and branch in plain code — no parsing. Auto-handle the high-confidence cases and route the uncertain ones to a bigger model or a human. It's one API call and output is free, so ask every question you need at once.

Build your own

Every scenario above is a single API call. Try any of them free in the playground, then get a hosted key to ship it in minutes.

Run this demo ▶Get an API key →
Tool-call risk gate — a Jev use case with a live demo · Jev by TypeSafe AI