AI API receipt · BerriAI/litellm

Claude Code to Bedrock: per-turn-control beta is dropped but the per-message output_config is still sent

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

✓ Badgr rejects this response

Bedrock answered 400 "messages.1.output_config: Extra inputs are not permitted" on a mid-conversation turn.

Outcome contract verdict: stream ended without a terminal [DONE] or message_stop event. The attempt is recorded as failed (invalid_outcome) instead of a verified success, so it is not billed as a good answer and can fall back to another route.

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.

data: {"error": {"message": "messages.1.output_config: Extra inputs are not permitted", "type": "invalid_request_error"}}

Badgr receipt

Written by Badgr’s receipt ledger and read back from GET /v1/receipts/replay-litellm-45411-bedrock-per-turn-control-400.

{
  "request_id": "replay-litellm-45411-bedrock-per-turn-control-400",
  "status": "failed",
  "endpoint": "/v1/chat/completions",
  "stream": true,
  "failure_stage": "outcome_contract",
  "error_code": "invalid_outcome",
  "error_message": "Response did not satisfy the outcome contract: stream ended without a terminal [DONE] or message_stop event",
  "retryable": true,
  "provider_mode": "replay",
  "routing_decision": "replayed_upstream_output",
  "created_at": "1791542228.510365"
}

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