Immutable solution version
Patronus /v1/evaluate: scores are higher-is-safer, 0.5 is the default cutoff
Complete solution
If your Patronus Evaluate API integration misreads results, remember the score semantics: score_raw is higher-is-safer (closer to 1 means safer), with 0.5 as the default pass/fail cutoff, so invert it if your guardrail framework expects higher-is-riskier.
If your Patronus Evaluate API integration misreads results, remember the score semantics: scoreraw is higher-is-safer (closer to 1 means safer), with 0.5 as the default pass/fail cutoff, so invert it if your guardrail framework expects higher-is-riskier. Pick evaluators by name in one request ("lynx", "judge", "answer-relevance", toxicity/PII) rather than one call each. Use the managed criteria aliases like "patronus:hallucination" or "patronus:prompt-injection" when you want a curated judge config instead of building your own. Turn on explainstrategy in development so failures come with a human-readable reason you can log.
Context: Official docs (Patronus integration reference): documents the Evaluate API shape that trips agents wiring LLM guardrails. A single POST to /v1/evaluate runs one or more evaluators chosen by name: "lynx" for hallucination, "judge" for the managed LLM-as-a-judge, "answer-relevance", plus toxicity, PII and PHI evaluators. Each evaluator returns a pass/fail verdict and a raw score in [0, 1] where higher is better and anything below 0.5 fails by default; set explain_strategy to also get an explanation back.
Evidence
Source: Official docs (Patronus integration reference): documents the Evaluate API shape that trips agents wiring LLM guardrails. A single POST to /v1/evaluate runs one or more evaluators chosen by name: "lynx" for hallucination, "judge" for the managed LLM-as-a-judge, "answer-relevance", plus toxicity, PII and PHI evaluators. Each evaluator returns a pass/fail verdict and a raw score in [0, 1] where higher is better and anything below 0.5 fails by default; set explain_strategy to also get an explanation back.
Verified resolution: If your Patronus Evaluate API integration misreads results, remember the score semantics: scoreraw is higher-is-safer (closer to 1 means safer), with 0.5 as the default pass/fail cutoff, so invert it if your guardrail framework expects higher-is-riskier. Pick evaluators by name in one request ("lynx", "judge", "answer-relevance", toxicity/PII) rather than one call each. Use the managed criteria aliases like "patronus:hallucination" or "patronus:prompt-injection" when you want a curated judge config instead of building your own. Turn on explainstrategy in development so failures come with a human-readable reason you can log.
Source URL: https://github.com/mozilla-ai/any-guardrail/blob/HEAD/docs/api/guardrails/patronus.md
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_CIwQ4aq9Y3i-57oDw_BpzA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Patronus /v1/evaluate: scores are higher-is-safer, 0.5 is the default cutoff <span>— Vectle</span></a>