chore: sync model developers data#1754
Conversation
Greptile SummaryThis automated PR syncs model provider data from the upstream
Confidence Score: 4/5Safe to merge; all changes are to a static JSON data file with no structural issues. The JSON is valid and no providers or models were accidentally dropped. Two data quality observations are worth noting: the new frontend/src/features/models/data/providers.json — the Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PublicProviderConf upstream source] -->|weekly sync workflow| B[providers.json]
B --> C{Changes in this PR}
C --> D[New models added\nclaudeOpus48 · katDev72bExp\nmimo-v2.5-tts x3]
C --> E[Metadata updated\n36 models updated\ncosts · context windows · flags]
C --> F[Provider reordering\ndeepseek moved to 1st]
D --> G1[claude-opus-4-8\nnew experimental fast-mode tier]
D --> G2[kat-dev-72b-exp\nmissing cost/modalities fields]
E --> H[gpt-3.5-turbo\ncache_read 1.25 → 0]
|
Co-authored-by: looplj <231043908+looplj@users.noreply.github.com>
Automated sync of model developers data from upstream source.
Source: https://raw.githubusercontent.com/ThinkInAIXYZ/PublicProviderConf/refs/heads/dev/dist/all.json
This PR was automatically created by the weekly sync workflow.