Skip to content

feat: add Meta Model API provider and muse-spark-1.1 (day-0) - #32701

Merged
mateo-berri merged 5 commits into
litellm_internal_stagingfrom
litellm_meta_model_api_muse_spark
Jul 10, 2026
Merged

feat: add Meta Model API provider and muse-spark-1.1 (day-0)#32701
mateo-berri merged 5 commits into
litellm_internal_stagingfrom
litellm_meta_model_api_muse_spark

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Relevant issues

Day-0 support for Meta's newly announced Meta Model API and the muse-spark-1.1 model (https://ai.meta.com/blog/introducing-muse-spark-meta-model-api)

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have added meaningful tests
  • My PR passes all CI/CD checks (e.g., lint, format, unit tests)
  • My PR's scope is as isolated as possible; it only solves 1 specific problem
  • I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Screenshots / Proof of Fix

Real billed call against https://api.meta.ai/v1 through a live proxy on localhost:4000, using a real META_API_KEY, captured at commit 6cbedcc

Proxy config (meta_test_config.yaml)

model_list:
  - model_name: muse-spark-1.1
    litellm_params:
      model: meta/muse-spark-1.1
      api_key: os.environ/META_API_KEY

Start the proxy

META_API_KEY=<real-key> LITELLM_LOCAL_MODEL_COST_MAP=True \
  litellm --config meta_test_config.yaml --port 4000 --detailed_debug

Call it (real network call, real key, costs real $)

$ curl -sS -D - http://localhost:4000/v1/chat/completions \
    -H "Content-Type: application/json" -H "Authorization: Bearer sk-1234" \
    -d '{"model":"muse-spark-1.1","messages":[{"role":"user","content":"Say hello in exactly 3 words."}],"reasoning_effort":"minimal"}'

x-litellm-model-api-base: https://api.meta.ai/v1
x-litellm-response-cost: 0.00180015
x-litellm-model-group: muse-spark-1.1
...
{
  "id": "chatcmpl-d72dfa4a-a034-4730-8791-c7850e391ef4",
  "model": "muse-spark-1.1",
  "object": "chat.completion",
  "choices": [{"finish_reason": "stop", "index": 0,
    "message": {"content": "Hello there friend", "role": "assistant"}}],
  "usage": {
    "completion_tokens": 348, "prompt_tokens": 15, "total_tokens": 363,
    "completion_tokens_details": {"reasoning_tokens": 335},
    "prompt_tokens_details": {"cached_tokens": 11}
  }
}

The x-litellm-model-api-base header confirms the request reached https://api.meta.ai/v1, reasoning_effort is accepted, and the response cost is computed from the new cost-map entry with the 335 reasoning tokens billed as output and the 11 cached prompt tokens priced at the cached-read rate

Native /v1/messages passthrough (real billed call, captured at commit 6f980e8)

$ curl -sS -D - http://localhost:4000/v1/messages \
    -H "Content-Type: application/json" -H "Authorization: Bearer sk-1234" \
    -d '{"model":"muse-spark-1.1","max_tokens":2048,"messages":[{"role":"user","content":"Say hello in exactly 3 words."}]}'

x-litellm-response-cost: 0.0025677499999999997
x-litellm-model-group: muse-spark-1.1
...
{
  "content": [
    {"data": "Q-PaDgHJO4WqRwHnZG1-...", "type": "redacted_thinking"},
    {"text": "Hello there friend", "type": "text"}
  ],
  "id": "msg_6a5048ca04f887e987e94243",
  "model": "muse-spark-1.1",
  "role": "assistant",
  "stop_reason": "end_turn",
  "type": "message",
  "usage": {
    "cache_creation_input_tokens": 0, "cache_read_input_tokens": 11,
    "input_tokens": 4, "output_tokens": 603,
    "output_tokens_details": {"thinking_tokens": 590}
  }
}

The Anthropic-format response (including the redacted_thinking block Meta returns) comes back untranslated and the cost is tracked from the anthropic-format usage block. Streaming through /v1/messages was also verified against the live API and emits proper Anthropic SSE events (message_start, content_block_delta, message_delta with usage, message_stop)

Type

🆕 New Feature

Changes

Registers the Meta Model API as a lightweight JSON-configured OpenAI-compatible provider (slug meta, base https://api.meta.ai/v1, key env META_API_KEY, base override env META_API_BASE), following the same pattern as recent pinstripes and darkbloom additions. The API is drop-in OpenAI-compatible for chat completions and the Responses API, and additionally exposes a native Anthropic-compatible /v1/messages endpoint, so no bespoke transformation module is needed

For /v1/messages, this generalizes the existing per-deployment OpenAILikeAnthropicMessagesConfig opt-in into a provider-level JSONProviderAnthropicMessagesConfig: any JSON-configured provider that lists /v1/messages in its supported_endpoints in providers.json now forwards Anthropic Messages requests untranslated to {api_base}/v1/messages, resolving the api key and base from the provider's configured env vars. Meta is the first provider to use it; providers without the endpoint keep routing through the existing chat-completions bridge

muse-spark-1.1 is added to the model cost map (and the bundled backup) with $1.25/M input, $4.25/M output and $0.15/M cached-read pricing, a 1,048,576-token context window, a 131,072-token output cap (per Meta's dev docs, https://dev.meta.ai/docs/getting-started/overview), multimodal input (text, image, video, pdf), tool calling, parallel tool calls, structured output, prompt caching and web search grounding

While wiring this up I found that JSON-configured providers never advertised reasoning_effort, so passing it to any reasoning-capable JSON provider raised UnsupportedParamsError. Since reasoning_effort (minimal through xhigh) is the headline feature of Muse Spark 1.1, I extended the shared capability-based param logic in dynamic_config.py (which already strips tool params when a model lacks function calling) to add reasoning_effort when the model's metadata sets supports_reasoning, gated so non-reasoning models are unaffected

Wiring lives in providers.json, the LlmProviders enum, the openai_compatible_endpoints / openai_compatible_providers lists in constants.py, base auto-detection in get_llm_provider_logic.py, and provider_endpoints_support.json. Tests cover provider resolution and base override, router config, cost calculation, model metadata, main/backup cost-map sync, and the reasoning_effort support plus its capability gating

The docs page backing the provider_endpoints_support.json url (https://docs.litellm.ai/docs/providers/meta) is added in BerriAI/litellm-docs#525, with the /v1/messages support documented in BerriAI/litellm-docs#526

Link to Devin session: https://app.devin.ai/sessions/11f0b1401cdb424ea29ffdbd14db7d79
Requested by: @mateo-berri

mateo-berri and others added 2 commits July 10, 2026 00:00
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@mateo-berri mateo-berri self-assigned this Jul 10, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 96.77419% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...itellm/llms/openai_like/messages/transformation.py 94.44% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

@greptile-apps

greptile-apps Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Registers Meta Model API as a JSON-configured OpenAI-compatible provider (meta, base https://api.meta.ai/v1) and adds muse-spark-1.1 to the cost map with full pricing, capability flags, and a 1 M context / 131 K output token envelope.

  • New JSONProviderAnthropicMessagesConfig in transformation.py generalises the per-deployment Anthropic passthrough into a provider-level mechanism: any JSON-configured provider that lists /v1/messages in providers.json now forwards Anthropic Messages payloads untranslated; Meta is the first consumer.
  • reasoning_effort capability gate added to dynamic_config.py: JSON providers whose model metadata sets supports_reasoning: true now advertise reasoning_effort in supported params, fixing an UnsupportedParamsError that would otherwise hit Muse Spark's headline feature.
  • Tests are all unit/mock-only (reads JSON files and calls local routing helpers); no real network calls reach the test suite.

Confidence Score: 5/5

Safe to merge; all changes are additive, follow the established JSON provider pattern, and are gated so existing providers and models are unaffected.

The provider wiring is consistent with recent pinstripes/darkbloom additions across all required registration points. The Anthropic Messages passthrough resolves credentials at call time, making it safe under the existing lru_cache. The reasoning_effort gate reads model metadata via supports_reasoning() rather than hardcoding model names, which satisfies the repo's model-flag rule. Tests are comprehensive and mock-only.

No files require special attention.

Important Files Changed

Filename Overview
litellm/llms/openai_like/messages/transformation.py Adds JSONProviderAnthropicMessagesConfig; resolves api_key/api_base from provider env vars at call time (not init), so the lru_cache in the dispatcher is safe. API-base resolution is correctly deferred to get_complete_url, avoiding the ValueError raise in the parent when api_base=None.
litellm/llms/openai_like/dynamic_config.py Adds reasoning_effort to supported params when supports_reasoning is true; gating via supports_reasoning() reads model metadata, keeping it data-driven and backward-compatible.
litellm/utils.py Dispatches to JSONProviderAnthropicMessagesConfig for JSON providers that declare /v1/messages support; runs after all provider-specific branches so existing behaviour is unaffected.
litellm/llms/openai_like/providers.json Adds meta provider config with base_url, api_key_env, api_base_env, and supported_endpoints including /v1/messages; follows the same schema as pinstripes/darkbloom.
model_prices_and_context_window.json Adds meta/muse-spark-1.1 with correct pricing ($1.25/M in, $4.25/M out, $0.15/M cached-read), max_input_tokens=1048576, max_output_tokens=131072 sourced from Meta dev docs, and full capability flags.
tests/test_litellm/llms/openai_like/test_meta_provider.py New test file; all tests are unit/mock-only (local routing, JSON reads, in-process litellm calls). No real network calls. Covers provider resolution, base override, Anthropic messages config dispatch, reasoning_effort gating, and cost calculation.
litellm/constants.py Adds https://api.meta.ai/v1 to openai_compatible_endpoints and 'meta' to openai_compatible_providers; minimal, correct additions.
litellm/litellm_core_utils/get_llm_provider_logic.py Adds URL-based auto-detection for https://api.meta.ai/v1, consistent with the pinstripes pattern.
litellm/model_prices_and_context_window_backup.json Backup cost map kept in sync with main; sync is enforced by test_muse_spark_1_1_backup_matches_main.
litellm/types/utils.py Adds LlmProviders.META enum entry; no issues.
provider_endpoints_support.json Adds meta entry with correct endpoint flags; docs URL follows the same convention as every other JSON-configured provider.
tests/test_litellm/test_muse_spark_1_1_model_metadata.py Verifies cost-map fields and backup/main sync; reads files locally, no network calls.

Reviews (5): Last reviewed commit: "feat: native Anthropic Messages passthro..." | Re-trigger Greptile

Comment thread model_prices_and_context_window.json Outdated
Comment thread provider_endpoints_support.json
@codspeed-hq

codspeed-hq Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 31 untouched benchmarks


Comparing litellm_meta_model_api_muse_spark (6f980e8) with litellm_internal_staging (65d90fd)1

Open in CodSpeed

Footnotes

  1. No successful run was found on litellm_internal_staging (592510e) during the generation of this report, so 65d90fd was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

@mateo-berri

Copy link
Copy Markdown
Contributor

@greptileai

@mateo-berri

Copy link
Copy Markdown
Contributor

@greptileai

@mateo-berri

Copy link
Copy Markdown
Contributor

@greptileai

@mateo-berri mateo-berri left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; thanks!

@mateo-berri
mateo-berri merged commit d82645d into litellm_internal_staging Jul 10, 2026
127 of 128 checks passed
@mateo-berri
mateo-berri deleted the litellm_meta_model_api_muse_spark branch July 10, 2026 03:45
@mateo-berri
mateo-berri restored the litellm_meta_model_api_muse_spark branch July 10, 2026 15:29
@mateo-berri

Copy link
Copy Markdown
Contributor

@greptileai

yuneng-berri added a commit that referenced this pull request Jul 11, 2026
…1.92.0 stable cut (#32959)

* fix(utils): resolve bedrock regional inference profiles to regional pricing in get_model_info (LIT-4056) (#32389)

* fix(utils): resolve bedrock regional inference profiles to regional pricing in get_model_info (LIT-4056)

* test(register_model): use a triple provider prefix as the unresolvable-key fixture

get_model_info now resolves bedrock/bedrock/... like a routing prefix, so the
double-prefix fixture stopped exercising the register_model fallback path.
Lock the new double-prefix resolution in as a model-info regression test

(cherry picked from commit 734fd29)

* fix(guardrails): walk Responses-API text taxonomy in shared content helpers (#32542)

* fix(guardrails): walk Responses-API text taxonomy in shared content helpers

Every guardrail sharing litellm/proxy/guardrails/_content_utils.py silently
drops all text on the /v1/responses path. AIM turns it into a loud 422 (
{"error":"No messages in the request"}); every other guardrail (Lakera v2,
Cato, Lasso, Repello, IBM, Azure Content Safety, enterprise secret
detection) scans an empty payload and lets the request through unscanned.

Three defects, all in _content_utils.py:

1. _iter_text_parts_in_content recognised only part.type == "text", but the
   Responses API uses input_text (request) and output_text (assistant).
2. _coerce_input_to_messages gated on "every item has a role key"; any
   Responses input list containing a function_call or function_call_output
   item failed the check and was wrapped as one opaque blob.
3. build_inspection_messages forwarded any role through, including a bare
   tool role missing tool_call_id, which validators like AIM's /fw/v1/analyze
   reject with a schema error.

Fix walks the actual Responses item taxonomy (message, function_call,
function_call_output, bare content parts and strings), recognises
{text, input_text, output_text} everywhere, and coerces any role outside
{system, user, assistant} to user in the outbound inspection payload.

* style: ruff-format changed guardrail files

* test(guardrails): cover function_call_output string form; drop em-dash in new docstring

* fix(guardrails): map function_call_output straight to user role

Avoids ever materialising a schema-invalid bare tool message. The
downstream role-safety coercion in build_inspection_messages still
guards genuinely caller-supplied non-standard roles (developer,
function, custom values); add a regression test covering that path
so the coercion has real coverage after this simplification.

* test(guardrails): pin chat-completions tool-role coercion in build_inspection_messages

* docs(test): soften AIM-specific claims in LIT-4294 test docstrings

Ryan's review flagged that several test docstrings assert AIM's
/fw/v1/analyze validates + rejects specific schema violations. That
behavior is customer-reported in the LIT-4294 writeup, not directly
verified by us. Rephrase to attribute the AIM 422 to the customer's
writeup and describe the underlying constraint as the OpenAI chat
schema; any downstream API that validates against that schema rejects
the same shape.

* refactor(guardrails): move unsupported-role coercion into AIM only

The generic coercion in build_inspection_messages collapsed any role
outside {system, user, assistant} to user for every caller of the
helper. Combined with the pre-existing apply_redacted_messages_back
write-back behavior in Lakera/AIM/Cato, that turned a loud OpenAI 400
on chat-completions tool-message masking into a silent semantic
corruption of the outbound request (role tool with tool_call_id got
rewritten to bare role user, dropping the assistant + tool_calls
sibling).

AIM specifically requires the coercion because its /fw/v1/analyze
validates the payload against the OpenAI chat schema; other guardrails
either do not validate roles or do their own reconstruction. Move the
coercion to AimGuardrail._build_aim_inspection_messages so the shared
helper keeps caller roles intact and no new cross-guardrail role
corruption is introduced. The pre-existing apply_redacted_messages_back
structural flatten remains as separate follow-up work.

function_call_output items still synthesise role user in the shared
helper because they have no natural role field, which is a different
concern from coercing a caller-supplied role.

* refactor(guardrails): preserve role fidelity in shared _content_utils

Shared inspection helpers should extract text and preserve semantic
role signals; role coercion for third-party schema safety stays inside
the guardrail that needs it (AIM).

Three shared-helper changes:
- Bare content-part dicts (input_text/output_text) with an explicit role
  keep it; only role-less parts default to user.
- Responses message items already had their role preserved; the
  behavior is now covered by an explicit test.
- function_call_output items default to role tool (semantic equivalent
  of the chat-completions tool message shape) instead of role user, so
  Responses and chat completions produce symmetric inspection payloads.
  A caller-supplied role on the item is still preserved.

AIM's schema-safe coercion in _build_aim_inspection_messages already
handles the resulting role tool: it collapses to user before the POST
to /fw/v1/analyze so AIM's OpenAI-schema validator does not reject the
bare tool message (no tool_call_id can survive the flatten). Added a
regression test in test_aim.py covering that path.

(cherry picked from commit e84a19a)

* feat: add Meta Model API provider and muse-spark-1.1 (day-0) (#32701)

(cherry picked from commit d82645d)

* fix(bedrock): keep mid-conversation system messages in place for Claude Invoke (#32578)

Hoisting every role system entry into the top-level system field mutates
the cache prefix whenever a client such as Claude Code appends a new
mid-conversation system message, invalidating the prompt cache for the
entire message history on Bedrock Invoke. Bedrock only rejects a system
entry at messages.0, so hoist just the leading run and forward the rest
in place

(cherry picked from commit cc36d54)

* feat(otel): emit the gen_ai.client.operation.exception event on failed LLM calls (#32655)

* feat(otel): emit the gen_ai.client.operation.exception event on failed LLM calls

The GenAI semantic conventions record failures of a GenAI client operation as
a log-based event named gen_ai.client.operation.exception, carrying the
exception.type / exception.message / exception.stacktrace trio at severity
WARN and correlated to the failed span. OTel v2 never emitted it: a failed LLM
call produced only the deprecated error.* span attributes, a generic exception
span event without a stacktrace, and the stacktrace under the vendor key
litellm.provider.error.stack_trace.

Build the logs pipeline (LoggerProvider + console/OTLP log exporters mirroring
the metrics plumbing) and record the event behind the enable_events flag, which
until now was defined but consumed nowhere. An operator-configured LoggerProvider
global is reused so the events ride their existing logs pipeline; an explicit
NoOpLoggerProvider global is honored as an opt-out and builds no recorder at all.

The existing span-side error surface (error.type, error.message, the exception
span event, and the litellm.provider.error.* detail keys) is untouched for
backwards compatibility.

* fix(otel): always ride the semconv-required exception pair on the GenAI event

Filtering the event attributes on truthiness conflated "absent" with "empty",
so an empty exception.type or exception.message would have been dropped, leaving
an event with neither semconv-required field. Build the attributes so the pair is
unconditional and only the recommended stacktrace is omitted when the payload
carries none.

* docs(otel): document the events plumbing module in the package README

* test(otel): cover the log exporter selection and logs endpoint normalization

The new logs plumbing had no coverage for exporter-kind selection, the
console fallback for an unrecognized kind, the /v1/logs signal-path rewriting
that lets one OTEL_ENDPOINT serve every signal, or the simple-vs-batch
processor split.

(cherry picked from commit 99b4c5e)

* fix(bedrock): gate in-place system role messages on model support for Claude Invoke (#32831)

* fix(bedrock): gate in-place system role messages on model support for Claude Invoke

* feat(bedrock): default unmapped Claude 4.8+ to in-place system role handling via fallback rule

(cherry picked from commit 5e23a5a)

* fix(anthropic): translate adaptive thinking/effort to pre-4.6 model support (#32867)

* fix(anthropic): translate adaptive thinking/effort to pre-4.6 model support

AnthropicMessagesConfig now reshapes the 4.6+ adaptive-thinking interface
(thinking:{type:adaptive} + output_config:{effort:...}) to whatever the routed
model supports. Thinking-capable non-adaptive models (e.g. Haiku 4.5, Sonnet 4.5)
get the effort translated to a legacy thinking budget_tokens. Models with no
reasoning support have thinking/effort dropped under drop_params. And because
adaptive thinking carries no budget while the legacy form must satisfy Anthropic's
max_tokens > budget_tokens rule, the translated budget is capped below max_tokens,
dropping thinking when max_tokens can't fit the minimum budget. 4.6+ models pass
through untouched.

This matters because clients like Claude Code speak native Anthropic /v1/messages
and send the adaptive interface unconditionally, regardless of the routed model.
The native passthrough previously only capability-gated the OpenAI-style
reasoning_effort alias and forwarded native output_config/adaptive thinking raw, so
a pre-4.6 model rejected it with "This model does not support the effort parameter"
and the request failed. Claude Code already gets drop_params auto-set, so its
requests now succeed.

* test(anthropic): gate undersized-max_tokens thinking drop on drop_params; add edge tests

Addresses review feedback on the max_tokens-too-small branch. Previously a
thinking-capable model whose max_tokens could not fit the minimum thinking budget
had thinking silently dropped regardless of drop_params, while a residual
output_config field in the same call still raised when drop_params was off. Gate
both consistently on drop_params: raise a clear error (naming max_tokens for the
undersized case) when drop_params is off, drop otherwise. Claude Code gets
drop_params auto-set, so it still succeeds.

Adds tests for the undersized-max_tokens raise, the residual output_config raise,
and the no-adaptive-interface passthrough on a non-adaptive model.

* fix(anthropic): make adaptive-effort translation silent to avoid breaking provider strip contracts

The previous raise-when-not-drop_params behavior broke existing bedrock and vertex
messages tests: those providers already silently strip unsupported output_config
for pre-4.6 models (issue #22797) with no drop_params required, and the shared
parent transform raising pre-empted that. It also conflicted with the goal of
keeping requests working rather than failing them.

Make the reshape silent: translate effort to legacy thinking for thinking-capable
models, drop thinking for non-reasoning models, and remove only the consumed effort
key from output_config, leaving any residual (e.g. format) for provider subclasses
(bedrock/vertex) to handle. No raise, no drop_params gating. This also resolves the
review note about inconsistent drop_params handling by making every path uniform.

Updates the tests to assert the silent behavior and residual output_config
preservation.

* fix(anthropic): handle output_config-capable but non-adaptive models (Opus 4.5)

Greptile caught a real bug: the early-return guard treated supports_output_config
as equivalent to supporting adaptive thinking. Claude Opus 4.5 advertises
supports_output_config (it accepts output_config.effort) but is not adaptive, so it
rejects thinking:{type:adaptive} with "adaptive thinking is not supported on this
model". The guard early-returned for Opus 4.5 and forwarded the adaptive thinking
block raw, reproducing the exact failure the fix is meant to prevent.

thinking:{type:adaptive} and output_config.effort are independent capabilities.
Only early-return for adaptive-thinking models. For a model that supports
output_config.effort but is not adaptive, keep the native effort and drop only the
unsupported adaptive thinking block. Verified live against Opus 4.5: the Claude Code
payload now returns 200 instead of 400.

Adds regression tests for Opus 4.5 with and without adaptive thinking.

* fix(anthropic): translate adaptive thinking for effort-capable pre-4.6 models

Claude Opus 4.5 advertises supports_output_config but not adaptive thinking,
so the early-return guard forwarded thinking.type=adaptive raw and Anthropic
rejected it. The guard now only skips true adaptive models; effort-only
requests on effort-capable models still pass through untouched. The
_map_reasoning_effort call is wrapped to surface unrecognized effort values
as a clean 400, matching _translate_reasoning_effort_to_anthropic

* fix(anthropic): fall back to legacy thinking when effort level unsupported

Opus 4.5 accepts output_config.effort but only low/medium/high; Claude Code
defaults to xhigh on newer models, so preserving that level raw gets rejected
by Anthropic. Gate the native-effort passthrough on _validate_effort_for_model
and fall through to the budget translation for unsupported levels

* fix(anthropic): keep effort-only requests untouched for provider normalization

The xhigh fall-through consumed effort-only requests on effort-capable
models, breaking bedrock invoke's own normalization which clamps xhigh to
the model's ceiling after the base transform runs
(test_bedrock_messages_normalizes_output_config_effort_for_opus). Restrict
the fall-through to requests that carry adaptive thinking; effort-only
requests pass through so provider subclasses keep owning level clamping

---------

Co-authored-by: Abhimanyu Kapur <38531241+akapur99@users.noreply.github.com>
(cherry picked from commit 3a62e54)

* fix(bedrock): flag mapped Claude 4.8+ entries with supports_mid_conversation_system (#32882)

Exact cost-map hits resolve before fallback-generalization rules, so the
mapped Sonnet 5, Fable 5 and jp Opus 4.8 Bedrock entries bypassed the
bedrock-anthropic-claude-mid-conversation-system rule and hoisted
mid-conversation system messages, invalidating the prompt cache.

(cherry picked from commit c15891f)

* Merge pull request #32873 from BerriAI/litellm_fallback_rules_routing_split

refactor(fallback-generalizations): split rules into routing and provider-neutral capability kinds

(cherry picked from commit 45d3644)

* Merge pull request #32874 from BerriAI/litellm_thread_provider_capability_probes

fix(anthropic): thread real provider through capability probes instead of pinning anthropic

(cherry picked from commit ead7ad3)

* test: add /v1/messages to supported_endpoints schema enum (#32739)

(cherry picked from commit bf02a4a)

---------

Co-authored-by: Mateo Wang <277851410+mateo-berri@users.noreply.github.com>
Co-authored-by: yucheng-berri <yucheng@berri.ai>
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: Yassin Kortam <yassin@berri.ai>
Co-authored-by: Abhimanyu Kapur <38531241+akapur99@users.noreply.github.com>
Co-authored-by: tin-berri <tin@berri.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant