What happens if the key powering frustration runs out of credit?

It pauses rather than erroring or running silently: when the key funding frustration runs dry, Tessary marks the classifier no_credit, stops sending scoring calls, and skips every turn until the key is topped up or swapped for one with funds left.

An org’s own OpenRouter or TypeSafe key running dry pauses as no_credit; Tessary Cloud’s own key running dry pauses as a distinct platform_unavailable instead, since that failure is the deployment’s to fix, not the org’s. Enabling frustration doesn’t check credit at all: turning it on only fails when the lane has no key to run on, so an already-empty key can still be saved and switched on, and the classifier pauses the first time it tries to spend credit that isn’t there. Frustration is a hosted classifier call, not a per-trace LLM judge call, which is cheaper by design, but it still draws on the org’s own key.

The pause lifts on its own: saving a new key, topping up the old one, or pressing Retry on the rail all clear it immediately, and a background sweep rechecks a paused key on a fixed interval regardless. A turn skipped while paused stays unscored; nothing is scored retroactively.