mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-02 02:11:58 +00:00
9e9cc12a25
A FLUX.2 deployment's own prices now decide the whole bill the way the owner set them. A flat output_cost_per_image stays flat per image and covers references, a deployment input_cost_per_pixel prices every megapixel and its references, and input_cost_per_reference_pixel overrides either. Only a deployment with neither gets the catalog's first-megapixel-plus-extra pricing The generated image is billed from the image Azure returns, so an edit without size is billed at the reference's size, which is what Azure generates. A size that can't be parsed bills one megapixel instead of raising FLUX.2 edits accept any object with read() again, as main did, including NamedTemporaryFile, SpooledTemporaryFile on 3.10 and Flask uploads, and a text-mode file fails with a clear error. get_image_dimensions raises on a malformed header as it did on main, and the JPEG header scan gives up after 1024 segments, 1024 fill bytes or a segment shorter than its length field get_model_info and model group info now report input_cost_per_reference_pixel, flux.2-pro lists the edits endpoint, and the key's description says how pixels are counted. The image_edit change that passed deployment prices into logging for every provider is reverted, since it changed other providers' billing on the proxy while generations kept the old behavior |
||
|---|---|---|
| .. | ||
| baseline_db.py | ||
| check_file_length.py | ||
| check_files_match.py | ||
| cost_map_guard.py | ||
| generate_model_prices_schema.py | ||
| run_migration.py | ||
| security_scans_readme.md | ||
| TEST_KEY_PATTERNS.md | ||