Get config (redacted)
api_key redacted (e.g. hOjm***vY2) so it can be safely surfaced in the Settings UI. If no config is set, returns an empty object with empty strings and an empty enabled_guardrails array.
Response — ProtectorConfig
Upsert config
api_key must be provided in the body. The response is returned in redacted form so the UI does not see its freshly-sent key echoed back.
Request body — ProtectorConfigUpsert
Errors
400—endpoint_url is required400—api_key is required400— URL fails SSRF validation (private/loopback/reserved IP, bad scheme, DNS failure)400—unknown guardrails: [...]if a name is not inPROTECTOR_GUARDRAILS
Response
SameProtectorConfig shape as the GET above (redacted).
Test config
{endpoint_url}/api/protectorplus/v1/health with a 5s timeout. Rejects non-public targets so the test cannot be turned into an SSRF probe.
Response — ProtectorTestResult
SDK config fetch
with tracectrl.guardrails(): setup. There is no authentication in v1 — the deployment is expected to bind the port to loopback or front it with an authenticated proxy. Returns an empty config (rather than 404) if none is set so the SDK can no-op cleanly.

