实时 Jev API 调试

在 Agent 执行前，检查这次决策。

使用工作流预设或自定义 Jev 原生协议，通过 OmniaKey 运行决策。编辑 JSON 输入，检查模型实际返回的答案、概率和 Token 用量。OmniaKey API Key 仅保留在内存中，不会保存。

阅读当前预设的接入教程 →

选择工作流预设并提供任务上下文。预设会定义有限的 Jev 问题，通过 OmniaKey 评估输入，并返回模型原始答案。展开原生请求预览，即可检查实际发送的内容。

OmniaKey API Key

只用于本次请求，页面不会持久化保存。

请求地址

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

所有预设均通过 OmniaKey 的原生 Jev 接口调用 jev-latest 模型。

工作流预设输入

{
  "task": "Resolve a request involving account access and a disputed charge",
  "evidence": [
    "Customer identity is verified",
    "Refund eligibility is unclear"
  ],
  "constraints": [
    "Do not change account state without confirmation"
  ]
}

查看发送给 OmniaKey 的原生请求

{
  "model": "jev-latest",
  "state": {
    "task": "Resolve a request involving account access and a disputed charge",
    "evidence": [
      "Customer identity is verified",
      "Refund eligibility is unclear"
    ],
    "constraints": [
      "Do not change account state without confirmation"
    ]
  },
  "questions": {
    "route": {
      "type": "choice",
      "instructions": "Choose the next workflow path from the task, available evidence, and constraints. Preserve all approval and permission boundaries.",
      "criteria": {
        "execute_quick": "A bounded, straightforward task has sufficient evidence and authority to proceed.",
        "review_deep": "Ambiguity, stakes, or conflicting evidence requires deeper review.",
        "decompose": "The task should be split into smaller independent steps before execution.",
        "blocked": "Required information, access, or authority is missing and prevents progress."
      }
    }
  }
}

创建访问密钥

结构化响应

answers + probabilities + usage

结构化 Jev 响应会显示在这里。

运行请求后可以检查经 OmniaKey 返回的原始 Jev 答案、置信度、概率分布、实际模型版本和 Token 用量。