AI API receipt · BerriAI/litellm

Responses streaming bridge omits sequence_number on most events and hardcodes output_item.done to 1

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

Badgr cannot tell this response is wrong

A complete Responses stream arrived with sequence_number missing on 8 of 9 events and 1 on output_item.done.

the stream is complete and well-formed; Badgr's check does not verify event numbering. 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.

event: response.created\ndata: {"type": "response.created"}
event: response.output_item.added\ndata: {"type": "response.output_item.added"}
event: response.output_text.delta\ndata: {"type": "response.output_text.delta", "delta": "hello"}
event: response.output_item.done\ndata: {"type": "response.output_item.done", "sequence_number": 1}
event: response.completed\ndata: {"type": "response.completed"}

Badgr receipt

Written by Badgr’s receipt ledger and read back from GET /v1/receipts/replay-litellm-44923-responses-stream-missing-sequence-numbers.

{
  "request_id": "replay-litellm-44923-responses-stream-missing-sequence-numbers",
  "status": "success",
  "endpoint": "/v1/chat/completions",
  "stream": true,
  "failure_stage": null,
  "error_code": null,
  "error_message": null,
  "retryable": null,
  "provider_mode": "replay",
  "routing_decision": "replayed_upstream_output",
  "created_at": "1791543162.324626"
}

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