Skip to content
Jev AI

Live Jev API debugger

Inspect the decision before your agent acts.

Run Jev through OmniaKey with a workflow preset or your own native decision contract. Edit the JSON input and inspect the model’s actual answers, probabilities, and token usage. Your OmniaKey API key stays in memory and is never saved.

Choose a workflow preset and provide the task context. The preset defines bounded Jev questions, evaluates your input through OmniaKey, and returns the model’s original answers. Open the native request preview to inspect what will be sent.

Used only for this request. The page does not persist the key.

Request endpoint

https://api.omniakey.com/v1/alpha/search

All presets use OmniaKey’s native Jev endpoint with the jev-latest model.

View the native request sent to OmniaKey
{
  "model": "jev-latest",
  "state": {
    "claim": "This order qualifies for an expedited refund under the policy",
    "evidence": [
      "Order arrived three days late",
      "Policy requires five days"
    ],
    "source_quality": "mixed",
    "stakes": "medium"
  },
  "questions": {
    "verdict": {
      "type": "choice",
      "instructions": "Judge whether the supplied evidence supports the claim, considering coverage, contradictions, source quality, timeliness, and stakes. Do not invent missing sources or facts.",
      "criteria": {
        "sufficient": "The evidence adequately supports the claim at the stated stakes.",
        "insufficient": "Evidence is missing, incomplete, or too weak to support the claim.",
        "contradictory": "The evidence materially contradicts the claim or conflicts internally.",
        "stale": "The evidence is too old for a time-sensitive claim."
      }
    }
  }
}
Create an access key

Structured response

answers + probabilities + usage

The typed Jev response will appear here.

Run the request to inspect the original Jev answers, confidence, probability distributions, resolved model version, and token usage returned through OmniaKey.