Noul: yes-probability

Noul asks a yes/no question and returns the probability that the answer is yes (0–1).

Request

{
  "type": "noul",
  "instructions": "The customer explicitly requests a refund",
  "criteria": {
    "true": "Explicitly mentions a refund, cancellation, or money back",
    "false": "Complains but asks for nothing"
  }
}

• criteria is optional, with true / false keys describing what counts as yes and no
• Clearer boundaries make the probability more usable

Answer

{ "type": "noul", "noul": 0.91 }

A single field: noul, i.e. P(yes). Noul carries no confidence (official docs, verified 2026-09-22) — a binary question has one degree of freedom; the probability is the whole story.

Official threshold guidance

From the official docs (verified 2026-09-22):

Range	Suggested action
≥ 0.8	Treat as yes
≤ 0.2	Treat as no
0.2 – 0.8	Middle ground — route to human review
0.5	Theoretical breakpoint when both error costs are equal

Don’t default to 0.5

0.5 only holds when right and wrong cost the same. If wrongly auto-refunding costs far more than a missed refund, raise the “yes” threshold above 0.9 and send the middle band to humans. The official cookbook demonstrates exactly this pattern — routing uncertain probabilities to review while keeping the values visible (via the llms.txt index).

Typical uses

• Guardrails: the official cookbook screens every message entering and leaving an LLM app (“is this a jailbreak?”, “any hidden instruction?”) and thresholds the probabilities — see Tool approval
• Ticket triage: binary signals like “asks for a refund” or “needs same-day handling” — see Ticket triage and the runnable site examples (JavaScript / Python)
• Retrieval pre-check: the official cookbook asks one Noul (“does this document contain an answer?”) before selecting among 218 lines of terms of service with a Choice

Pairing advice

Because Noul lacks a confidence signal, our advice is to pair it in the same request with a Choice or Score (both carry confidence) whenever you also need “should this automate?” Back to Capabilities.