Request Replay

Re-send any logged request to its original provider for debugging and regression testing.

How It Works

  1. Every request through Proxle is fully logged (headers, body, response)
  2. From the request detail page, click Replay to re-send the exact same request
  3. The replay hits the actual provider API with the original parameters
  4. Compare the original and replayed responses side by side

Prerequisites

Request replay requires stored provider credentials because the original API keys are pass-through only (never stored).

Setting Up Provider Credentials

  1. Go to Dashboard > Settings > Providers
  2. Click Add Credential for the provider you want to replay
  3. Enter your provider API key
  4. The key is encrypted at rest using AES-256 (Fernet encryption)

Provider credentials are only used for replay. Normal proxy requests use pass-through keys from the SDK.

Running a Replay

  1. Go to Dashboard > Requests
  2. Click on any request to view its details
  3. Click the Replay button
  4. Wait for the replay to complete
  5. The replayed response appears alongside the original

Use Cases

Debugging

When a request produces unexpected output, replay it to check:

  • Was it a transient error?
  • Does the model give consistent responses?
  • Has the model behavior changed?

Regression Testing

After a prompt change:

  1. Find a representative request in the logs
  2. Replay it to see how the new model version responds
  3. Compare the outputs to verify quality

Cost Verification

Replay a request and compare the token counts and costs to verify pricing accuracy.

Limitations

  • Replay uses your stored provider credentials, which may have different rate limits
  • Non-deterministic models may return different responses
  • The replayed request is logged as a new request with a replay_of reference
  • Streaming requests can be replayed but the response is captured as non-streaming
Cost TrackingMetadata & Attribution