Can't track cost per request

What engineers usually see

  • •No way to see cost of individual requests
  • •Billing is aggregated at account level
  • •Cannot identify expensive requests
  • •Unable to optimize high-cost operations

Why this is hard to debug

Provider billing doesn't expose per-request costs. You have to calculate costs manually from token usage. Receipts include automatic cost calculation for every request.

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"}]
  }' -i | grep X-Badgr-Request-Id

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

  • Exact cost per request
  • Cost breakdown by input/output
  • Cost comparison to similar requests
  • Historical cost trends
  • Cost optimization recommendations

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.