实时 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": {
"task": "Review a complex customer dispute with 100k context and tool use",
"candidates": [
{
"id": "fast-model",
"description": "Fast general model with 32k context",
"cost": "low",
"latency": "low"
},
{
"id": "reasoning-model",
"description": "Strong reasoning, 200k context, and tool use",
"cost": "high",
"latency": "medium"
}
],
"priorities": [
"quality",
"context",
"tool_use",
"cost"
],
"constraints": [
"Customer data must remain within approved tools"
],
"stakes": "high"
},
"questions": {
"model": {
"type": "choice",
"instructions": "Select the best approved candidate using the stated quality, context, tools, cost, latency, and stakes. Do not assume undocumented capabilities. Choose escalate when no candidate is adequate or evidence is insufficient.",
"criteria": {
"fast-model": "Choose this approved model if its documented capabilities satisfy the task, priorities, constraints, and stakes: {\"id\":\"fast-model\",\"description\":\"Fast general model with 32k context\",\"cost\":\"low\",\"latency\":\"low\"}",
"reasoning-model": "Choose this approved model if its documented capabilities satisfy the task, priorities, constraints, and stakes: {\"id\":\"reasoning-model\",\"description\":\"Strong reasoning, 200k context, and tool use\",\"cost\":\"high\",\"latency\":\"medium\"}",
"escalate": "No approved candidate can safely satisfy the task, or the provided evidence is insufficient to select one."
}
}
}
}结构化响应
answers + probabilities + usage结构化 Jev 响应会显示在这里。
运行请求后可以检查经 OmniaKey 返回的原始 Jev 答案、置信度、概率分布、实际模型版本和 Token 用量。