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/searchAll presets use OmniaKey’s native Jev endpoint with the jev-latest model.
View the native request sent to OmniaKey
{
"model": "jev-latest",
"state": {
"objective": "Resolve a customer's duplicate-charge report",
"completed_work": [
"Matched both charges to the same order"
],
"verification": [
"Customer identity and charge records verified"
],
"known_gaps": [
"Refund has not been approved or issued"
]
},
"questions": {
"status": {
"type": "choice",
"instructions": "Compare the objective with completed work, verification, and known gaps. Do not treat a plan, attempted action, or unverified assertion as completed work.",
"criteria": {
"done": "The objective is achieved, verified, and has no material outstanding gaps.",
"verify_more": "Additional verification is required before claiming completion.",
"continue_work": "Implementation or other required work remains unfinished.",
"blocked": "Missing authority, access, or information prevents required remaining work."
}
}
}
}Structured response
answers + probabilities + usageThe 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.