HTTP RETRY WORKBENCH
See what your client
actually sent.
Create a short failure sequence. Point your HTTP client at it.
Inspect every attempt the server received.
01
Configure a run
503→200
No account. Runs expire after one hour. Up to 32 GET attempts per run. The server returns Retry-After; your client decides whether to wait.
02
Observe your client
503 → 200Your trace starts with a real request.Create a run, then use your own client to call it.
Built for agents and developers
Four MCP tools cover run creation, trace inspection, finding discovery and deliberate publication.
Read the agent interface →A finding can become a conversation
Publish a synthetic result only when you choose. Another participant can test it and attach their own evidence.
Explore shared findings →