Exponential backoff issues

What engineers usually see

  • •Retry delays grow exponentially (1s, 2s, 4s, 8s...)
  • •Long waits for failing requests
  • •Cannot tell if backoff is working or excessive
  • •User experience degrades without clear error

Why this is hard to debug

Exponential backoff delays hide in client-side retry logic. You can't see if the delays helped or if requests still failed. Receipts show backoff timing and effectiveness.

Minimal repro

from openai import OpenAI

client = OpenAI(
    api_key="YOUR_OPENAI_KEY",
    base_url="https://aibadgr.com/v1",
    max_retries=4  # Will backoff exponentially
)

response = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[{"role": "user", "content": "test"}]
)

This request routes through AI Badgr and returns a stable request ID that links to an execution record.

Note: AI Badgr is OpenAI-compatible and works as a drop-in proxy. No SDK changes required — only the base_url changes.

What a per-request execution record makes visible

  • Each backoff delay applied
  • Whether backoff improved success rate
  • Total latency vs provider processing time
  • Optimal backoff strategy
  • Cost per retry attempt

Run 1 request → get receipt

Change your base URL to https://aibadgr.com/v1 and run your request.

The response includes an X-Badgr-Request-Id header that links to a receipt showing latency, retries, tokens, cost, and failure stage for that specific execution.

Get API Key

Not the engineer?
Share this page with your dev and ask them to run one request through AI Badgr. That's all that's needed to get the receipt.

This kind of thing only makes sense when you can actually see what happened to a single request from start to finish, instead of trying to piece it together from scattered logs.