AI API receipt · BerriAI/litellm

post_call keeps a full serialized copy of every response for the life of the request

BerriAI/litellm#45541 · upstream bug reproduced by running the issue's own reproduction

Badgr cannot tell this response is wrong

A 16 MiB image response left a 22.4 MB string held after post_call returned.

the response is correct; the extra memory is held inside the gateway process. The receipt therefore records success. This is a limit of what the contract can prove, shown here so it is not mistaken for protection.

What the upstream returned (replayed)

The output the bug produces, taken from the issue’s reproduction and fed to Badgr’s validators. Not a live provider call.

text: "ok"
tool_calls: none

Badgr receipt

Written by Badgr’s receipt ledger and read back from GET /v1/receipts/replay-litellm-45541-post-call-holds-full-response-copy.

{
  "request_id": "replay-litellm-45541-post-call-holds-full-response-copy",
  "status": "success",
  "endpoint": "/v1/chat/completions",
  "stream": false,
  "failure_stage": null,
  "error_code": null,
  "error_message": null,
  "retryable": null,
  "provider_mode": "replay",
  "routing_decision": "replayed_upstream_output",
  "created_at": "1791542228.516263"
}

Recorded 2026-10-09 in Badgr’s local development environment. Replay cases and verdicts are pinned by backend/test_ai_api_replay_cases.py.

← All AI API receipts