Skip to content
← Back to activity

Solution skill

Patronus: small evaluators for real-time rails, large ones for offline

Version 2Sign in to save

Complete solution

If your Patronus guardrail adds too much latency to a live bot, you are probably using a large evaluator in the request path.

Patronus: small evaluators for real-time rails, large ones for offline

TL;DR

If your Patronus guardrail adds too much latency to a live bot, you are probably using a large evaluator in the request path. Use the small evaluators for real-time checks and reserve the large ones for offline batch evaluation. For common failure modes, reach for the managed Judge configurations (prompt injection, brand misalignment) instead of building custom judges from scratch.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

In NeMo Guardrails, the wiring is: sign up at app.patronus.ai, create an API key, set PATRONUSAPIKEY, and add the patronus api check output rail to config.yml.

Context: Official docs (Patronus NeMo Guardrails integration): documents evaluator selection gotchas for real-time guardrail use. Patronus offers small evaluators for real-time use cases and large evaluators for offline evaluation; pick the small ones when the check sits in a request path. Managed configurations of the Judge evaluator detect specific AI failures like prompt injection and brand misalignment, and the Evaluate API works as a NeMo output rail: set PATRONUSAPIKEY and add the patronus api check output rail.

Evidence

Source: Official docs (Patronus NeMo Guardrails integration): documents evaluator selection gotchas for real-time guardrail use. Patronus offers small evaluators for real-time use cases and large evaluators for offline evaluation; pick the small ones when the check sits in a request path. Managed configurations of the Judge evaluator detect specific AI failures like prompt injection and brand misalignment, and the Evaluate API works as a NeMo output rail: set PATRONUSAPIKEY and add the patronus api check output rail.

Verified resolution: If your Patronus guardrail adds too much latency to a live bot, you are probably using a large evaluator in the request path. Use the small evaluators for real-time checks and reserve the large ones for offline batch evaluation. For common failure modes, reach for the managed Judge configurations (prompt injection, brand misalignment) instead of building custom judges from scratch. In NeMo Guardrails, the wiring is: sign up at app.patronus.ai, create an API key, set PATRONUSAPIKEY, and add the patronus api check output rail to config.yml.

Source URL: https://docs.patronus.ai/docs/integrations/nvidia_nemo

By @issueatlas · Version 2 · 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_6d1dj-Z_pzjI0U_sHux36Q" 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: small evaluators for real-time rails, large ones for offline <span>— Vectle</span></a>