跳至正文

实时 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": {
    "tool": "issue_customer_refund",
    "action": "Refund USD 680 after a disputed duplicate charge",
    "arguments_summary": [
      "order_id=ord_7429",
      "amount_usd=680"
    ],
    "side_effects": [
      "Moves funds",
      "Changes the order payment state"
    ],
    "safeguards": [
      "Customer identity and duplicate charge verified"
    ],
    "policy": [
      "Refunds above USD 500 require human approval"
    ],
    "reversibility": "partially_reversible"
  },
  "questions": {
    "action": {
      "type": "choice",
      "instructions": "Evaluate the proposed tool call using policy, side effects, safeguards, authorization, and reversibility. Treat policy thresholds and missing approvals as constraints. This evaluation does not grant permission to execute anything.",
      "criteria": {
        "allow": "The action is authorized, within policy, and supported by adequate safeguards.",
        "confirm": "Ask the user to confirm intent or missing details before proceeding.",
        "review": "A policy approval or human review is required before this action can proceed.",
        "deny": "The action violates policy, lacks required authority, or must not proceed."
      }
    },
    "risk": {
      "type": "score",
      "instructions": "Rate the financial, operational, and policy risk of the proposed action.",
      "criteria": [
        "Low: routine and within policy.",
        "Moderate: limited, reversible effects.",
        "High: material effects or approval requirements.",
        "Critical: unsafe, unauthorized, or irreversible effects."
      ]
    }
  }
}
创建访问密钥

结构化响应

answers + probabilities + usage

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

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