Skip to content

feat: add scalattice openai-compatible provider - #35221

Open
romulushill wants to merge 4 commits into
BerriAI:litellm_internal_stagingfrom
scalattice:feat/scalattice-openai-compatible-provider
Open

feat: add scalattice openai-compatible provider#35221
romulushill wants to merge 4 commits into
BerriAI:litellm_internal_stagingfrom
scalattice:feat/scalattice-openai-compatible-provider

Conversation

@romulushill

@romulushill romulushill commented Jul 30, 2026

Copy link
Copy Markdown

Summary

  • Register Scalattice in litellm/llms/openai_like/providers.json
  • Document endpoint coverage in provider_endpoints_support.json (chat completions)
  • Add Scalattice to the dashboard Providers enum + logo (scalattice.svg)
  • Publish catalog model pricing in model_prices_and_context_window.json (backup synced)
  • Base URL: https://api.scalattice.cloud/v1
  • API key env: SCALATTICE_API_KEY (optional override via SCALATTICE_API_BASE)

Docs page (separate repo): BerriAI/litellm-docs#719

Usage

import litellm
import os

os.environ["SCALATTICE_API_KEY"] = "slt_..."
resp = litellm.completion(
    model="scalattice/qwen-3-8b",
    messages=[{"role": "user", "content": "Hello"}],
)

Docs: https://scalattice.cloud/docs/developers#litellm
Product: https://scalattice.com/

Test plan

  • Local check_provider_folders_documented.py passes
  • CI against litellm_internal_staging
  • Dashboard shows Scalattice logo for scalattice provider
  • Live litellm.completion(model="scalattice/<model>", ...) with SCALATTICE_API_KEY

@CLAassistant

CLAassistant commented Jul 30, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Comment on lines +33 to +38
"scalattice": {
"base_url": "https://api.scalattice.cloud/v1",
"api_key_env": "SCALATTICE_API_KEY",
"api_base_env": "SCALATTICE_API_BASE",
"supported_endpoints": ["/v1/chat/completions"]
},

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.

P1 Provider coverage metadata is missing

When the provider documentation coverage check loads this new registry key, scalattice has no matching entry in provider_endpoints_support.json, causing the check to raise UndocumentedProviderError.

Rule Used: Block new LLM Provider integrations if they're ope... (source)

Knowledge Base Used: LLM Provider Adapters

@greptile-apps

greptile-apps Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds Scalattice as a JSON-configured OpenAI-compatible provider.

  • Registers the Scalattice API base URL and API-key environment variable.
  • Supports an API-base override through SCALATTICE_API_BASE.
  • Declares chat completions as the supported endpoint.

Confidence Score: 4/5

The provider coverage failure must be fixed before merging by adding Scalattice to provider_endpoints_support.json.

The runtime JSON-provider resolution path handles Scalattice, but the new registry key deterministically violates the repository's provider documentation coverage check and raises UndocumentedProviderError.

Files Needing Attention: litellm/llms/openai_like/providers.json and provider_endpoints_support.json

Important Files Changed

Filename Overview
litellm/llms/openai_like/providers.json Adds the Scalattice registry entry, but omits the coordinated endpoint-support metadata required by the provider coverage check.

Reviews (1): Last reviewed commit: "Add Scalattice as an OpenAI-compatible p..." | Re-trigger Greptile

@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codspeed-hq

codspeed-hq Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 31 untouched benchmarks


Comparing scalattice:feat/scalattice-openai-compatible-provider (bc2ff0d) with litellm_internal_staging (71b825a)

Open in CodSpeed

Register Scalattice in the openai_like providers registry and document
endpoint coverage for chat completions.
@romulushill
romulushill force-pushed the feat/scalattice-openai-compatible-provider branch from 144698c to 34c492e Compare July 30, 2026 09:23
@romulushill romulushill changed the title Add Scalattice OpenAI-compatible provider feat: add scalattice openai-compatible provider Jul 30, 2026
@romulushill
romulushill changed the base branch from main to litellm_internal_staging July 30, 2026 09:24
Register Scalattice in the dashboard provider map with the brand mark, and publish catalog model costs so spend tracking and docs pricing stay aligned.
@romulushill

Copy link
Copy Markdown
Author

Follow-up pushed on this branch:

  • Dashboard provider entry + Scalattice logo (scalattice.svg)
  • Catalog model pricing in model_prices_and_context_window.json (backup synced)

Docs page PR (separate repo): BerriAI/litellm-docs#719

Rebuild pricing files from upstream staging and re-add only Scalattice catalog entries so backup matches main after merge.
@romulushill

Copy link
Copy Markdown
Author

Fixed pricing backup pollution: rebuilt model prices from upstream staging and re-added only Scalattice catalog entries so gpt-5.4-mini/nano max_input_tokens stay at 272000 in both files.

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.

2 participants