Endpointprobe: HTTP Desk

You are about to ship an API change and someone asks the question that matters: does the new build answer exactly like the old one, or only close enough to fool a glance? Endpointprobe: HTTP Desk exists for that moment. You describe a scenario once — method, path template, headers, assertions — and point it at two environments, baseline and candidate. The workbench replays both sides and reads back a semantic verdict instead of a wall of raw text. The diff engine compares structure, not noise. Declare a timestamp, request id, or server-date header volatile and it is canonicalized out of the comparison — with every normalization disclosed on screen beside the verdict, so the proof stays honest. Stored tokens live in the device Keychain. Previews and exports use placeholders for bound secrets. Before writing a checksummed evidence bundle, the app checks for bound secret values in text, parsed JSON and Base64 and blocks export when it finds a match. Inspect exported content before sharing. A recorded sample contract loads on first launch, so the whole flow is visible before you configure anything. • Scenario-by-environment run matrix with one-tap replays • Transcripts: redacted request, redirect ledger, response checksums, eight assertion kinds • Structural JSON diff with declared-volatility canonicalization • Deterministic .endpointprobe evidence bundles with SHA-256 manifests, verified on import • Redirect policies, bounded response bodies, typed transport failures • iPad split-view workbench with keyboard shortcuts Requests you choose can send data to your configured endpoints. Workspace records stay in app storage; evidence bundles go to the destination you choose when exporting. No subscription, sign-in, or advertising.