Killswitches
getKillswitch reads an operational killswitch from the cached rules blob. A killswitch is the panic lever: true means "killed" (the protected path should be…
/docs/ — also served raw at https://shipeasy-ai.github.io/sdk-java/pages/killswitches.md.getKillswitch reads an operational killswitch from the cached rules blob.
A killswitch is the panic lever: true means "killed" (the protected path
should be disabled).
Whole killswitch
import ai.shipeasy.Client;
import java.util.Map;
Client c = new Client(Map.of("user_id", "u_123"));
boolean killed = c.getKillswitch("panic_button");
if (killed) {
// disable the protected path
}getKillswitch(name) returns true when the whole killswitch is killed.
Unknown killswitches return false.
Named per-key switches
A killswitch can carry named per-key switches. Pass the switch key to read one:
boolean checkoutOff = c.getKillswitch("panic_button", "checkout");With switchKey, the call returns true when that specific named switch is on.
An unconfigured switch key falls back to the killswitch's top-level value,
so a switch you haven't explicitly set tracks whether the whole killswitch is
killed. A null switchKey reads the whole-kill-switch killed state directly.
Killswitches are not user-scoped — the bound user is irrelevant to the result,
but reading them off the same Client keeps everything one-stop.
Dynamic configs
getConfig fetches a typed JSON value (a "dynamic config" / remote config) by name from the cached rules blob. Configs are not user-scoped — they resolve to…
Error reporting — `see()`
The Java SDK ships the see() surface: structured error reporting that documents an error's product consequence, not just its stack. It mirrors @shipeasy/sdk…