Skip to content

chore: sync model developers data#1754

Merged
looplj merged 1 commit into
unstablefrom
sync-model-developers
Jun 1, 2026
Merged

chore: sync model developers data#1754
looplj merged 1 commit into
unstablefrom
sync-model-developers

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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.

@github-actions github-actions Bot added automated dependencies Pull requests that update a dependency file labels May 31, 2026
@greptile-apps

greptile-apps Bot commented May 31, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This automated PR syncs model provider data from the upstream PublicProviderConf source, updating providers.json with new models and revised metadata for existing ones.

  • New models added: claude-opus-4-8 (Anthropic), kat-dev-72b-exp (Kwaipilot), and three Xiaomi MiMo-V2.5-TTS variants; the Anthropic addition introduces a new experimental.modes.fast cost tier pattern.
  • Metadata updates: 36 existing models received field corrections including context-window expansions for DeepSeek models, minor price adjustments for several OpenAI models (e.g., gpt-4o-mini, o4-mini), and gpt-3.5-turbo's cache_read cost changed from 1.25 to 0.
  • No providers removed or added: the same 16 providers are present; the apparent churn in the diff is due to provider ordering changing (deepseek moved to first position).

Confidence Score: 4/5

Safe 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 kat-dev-72b-exp model is missing standard fields like cost and modalities (though the frontend handles this gracefully), and gpt-3.5-turbo's cache_read cost jumped to zero — an unusual change that could reflect an upstream data error rather than a real pricing update.

frontend/src/features/models/data/providers.json — the kwaipilot/kat-dev-72b-exp entry and the gpt-3.5-turbo cache_read value are worth a quick manual check.

Important Files Changed

Filename Overview
frontend/src/features/models/data/providers.json Automated data sync: 4 new models added, 36 existing models updated with metadata/cost corrections, and provider ordering changed. New kat-dev-72b-exp entry is missing several standard fields (cost, modalities, open_weights, release_date). JSON is structurally valid.

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]
Loading

Comments Outside Diff (2)

  1. frontend/src/features/models/data/providers.json, line 1 (link)

    P2 Incomplete kat-dev-72b-exp model entry

    The new kwaipilot/kat-dev-72b-exp model is missing several fields that are present on virtually every other model in the file: cost, modalities, open_weights, release_date, last_updated, and attachment. While the frontend accesses most of these with optional chaining (?.) and won't crash, the model will appear with $0 cost and no modality information in the UI, which could mislead users configuring it. Compare to the sibling kat-dev entry which has all of these fields populated.

    Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

  2. frontend/src/features/models/data/providers.json, line 1 (link)

    P2 gpt-3.5-turbo cache_read cost changed to 0

    The cache_read cost for openai/gpt-3.5-turbo changed from 1.25 ($/M tokens) to 0. This is the only model where a previously non-zero cache cost was zeroed out rather than reduced — all other cost corrections in this sync are small precision adjustments. If this reflects an actual pricing change from OpenAI, it's fine; otherwise it may be an upstream data error worth verifying before merging.

Reviews (1): Last reviewed commit: "chore: sync model developers data" | Re-trigger Greptile

@looplj looplj merged commit 70417cc into unstable Jun 1, 2026
junjiangao pushed a commit to junjiangao/axonhub that referenced this pull request Jun 2, 2026
Co-authored-by: looplj <231043908+looplj@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant