实时 Jev API 调试
在 Agent 执行前,检查这次决策。
使用工作流预设或自定义 Jev 原生协议,通过 OmniaKey 运行决策。编辑 JSON 输入,检查模型实际返回的答案、概率和 Token 用量。OmniaKey API Key 仅保留在内存中,不会保存。
阅读当前预设的接入教程 →选择工作流预设并提供任务上下文。预设会定义有限的 Jev 问题,通过 OmniaKey 评估输入,并返回模型原始答案。展开原生请求预览,即可检查实际发送的内容。
只用于本次请求,页面不会持久化保存。
请求地址
https://api.omniakey.com/v1/alpha/search所有预设均通过 OmniaKey 的原生 Jev 接口调用 jev-latest 模型。
查看发送给 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."
}
}
}
}结构化响应
answers + probabilities + usage结构化 Jev 响应会显示在这里。
运行请求后可以检查经 OmniaKey 返回的原始 Jev 答案、置信度、概率分布、实际模型版本和 Token 用量。