Capture deliberately
Persistent request bodies are not a default. Capture scope, retention, and reveal actions require explicit policy.
Privacy-aware debugging
Request inspection is designed around explicit capture, searchable metadata, redacted export, and controlled replay within the same authorized workspace.
See how it worksPersistent request bodies are not a default. Capture scope, retention, and reveal actions require explicit policy.
Authorization, cookies, tokens, and configured sensitive fields are removed from generated cURL and HAR output.
Replay keeps authorization, destination, size, rate, and audit controls rather than becoming an unrestricted request tool.