Typed judgment

Ask a typed question about any content and get an answer your code can branch on, not prose to parse. Three question types: choice (pick one of your named options, with a probability for each and a confidence), score (a position on levels you describe), and noul (a yes/no as a probability from 0 to 1). Up to 8 questions per call, answered in parallel over one piece of state. Model-backed, not deterministic.

TRY IN PLAYGROUND →

Input

Example output

{}

Try it - see the 402 challenge (free)

curl -i -X POST https://agent402.tools/v1/judge \
  -H "Content-Type: application/json" \
  -d '{"state":"The export button crashes the settings page in Safari. It works in Chrome, but a few of our customers only use Safari.","questions":{"severity":{"type":"score","instructions":"How severe is the reported issue?","criteria":["Cosmetic; no impact to functionality","Broken or degraded feature, but a workaround exists","Blocking issue; no workaround exists"]},"is_reproducible":{"type":"noul","instructions":"Does this report describe steps that would let an engineer reproduce the problem?"}}}'

The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
import { metaTitle, metaDescription } from "./seo-meta.js";

const client = new x402Client();
client.setSpendControls?.(false); // @x402/core 2.23+ refuses anything over $1 or off the pegged-asset list by default; keep your own ceiling in code instead
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/v1/judge", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "state": "The export button crashes the settings page in Safari. It works in Chrome, but a few of our customers only use Safari.",
    "questions": {
      "severity": {
        "type": "score",
        "instructions": "How severe is the reported issue?",
        "criteria": [
          "Cosmetic; no impact to functionality",
          "Broken or degraded feature, but a workaround exists",
          "Blocking issue; no workaround exists"
        ]
      },
      "is_reproducible": {
        "type": "noul",
        "instructions": "Does this report describe steps that would let an engineer reproduce the problem?"
      }
    }
  }),
});

Related tools