Upstream timeout (504)

What engineers usually see

  • •HTTP 504 Gateway Timeout received
  • •Intermediate proxy or gateway timed out
  • •Provider may still be processing request
  • •Cannot verify execution status

Why this is hard to debug

504s indicate a timeout between proxies, not necessarily the provider. The request might complete successfully on the provider while you see a timeout. Receipts track actual provider execution.

Minimal repro

curl https://aibadgr.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_OPENAI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "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

  • Gateway vs provider timeout distinction
  • Actual provider processing status
  • Whether response was generated
  • Billing impact
  • Retry safety indicator

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.