feat(runtime): source model metadata from models.dev #691

Area

Runtime catalog / model metadata / cost pricing

Problem

Mosoo maintains model presets in pkgs/runtime-catalog/src/catalog.ts and provider/model pricing schedules in apps/api/src/modules/cost/domain/cost-pricing.ts. Adding models and keeping their capabilities, limits, and prices current requires repeated manual edits. The model-support request in #593 illustrates this maintenance gap.

Models.dev provides provider-specific model data and provider-independent model metadata through public JSON endpoints. Its current provider catalog includes separate OpenCode Zen and OpenCode Go identities and model-level SDK overrides, which matter when a provider serves models through different protocols.

Proposal

Use models.dev as an upstream model metadata source, with a validated, versioned snapshot and Mosoo-owned compatibility rules.

• Import provider/model identities, display names, capabilities, modalities, context/output limits, lifecycle status, and provider-specific prices where supported by Mosoo's contracts.
• Preserve provider-specific model IDs and model-level serving overrides. Canonical model IDs may link metadata, but must not collapse distinct providers, endpoints, credentials, or pricing.
• Define an explicit adapter from upstream serving metadata to Mosoo's model protocols. Missing or ambiguous protocol information requires a reviewed override; importing a model does not establish runtime compatibility or authorize its execution.
• Keep a validated last-known-good snapshot available offline. Refreshes must be bounded, schema-checked, and atomic; upstream failure or invalid data must retain the previous snapshot. Do not put a remote metadata request on each model-call path.
• Retain documented Mosoo overrides for verified compatibility, defaults, and upstream omissions. Define refresh cadence, provenance, precedence, and review/rollback behavior.
• Version imported pricing by provider/model and applicable time. Refreshing prices must not silently reprice historical usage. Preserve unknown pricing explicitly; distinguish missing data from a validated zero rate. Handle cache/token/context tiers only where Mosoo can represent their semantics.
• Keep existing Session model identity, protocol, and configuration stable across refreshes; do not silently substitute another model or change a default for existing Sessions.

Acceptance criteria

• The upstream schema, selected fields, provider/model mapping, and override precedence are documented and fixture-tested.
• A valid snapshot supplies model-selection metadata without requiring manual duplication of imported fields in the current catalog.
• OpenCode Go and Zen remain separate, including model-level SDK/protocol differences and credential isolation.
• Tests cover malformed/partial data, timeout/unavailability, an interrupted refresh, upstream model removal/deprecation, and recovery using the last-known-good snapshot.
• Existing configured Sessions remain usable with their original identities and protocol after a metadata refresh or model removal.
• Pricing tests cover provider-specific identity, unknown versus zero prices, supported cache/context tiers, and unchanged historical cost calculations after a refresh.
• Runtime admission remains explicit and verified; catalog presence alone cannot enable an unsupported runtime/model/protocol combination.
• Relevant repository checks pass. Hosted refresh/fallback behavior is verified separately before claiming deployed support; real inference compatibility requires separate runtime/model acceptance.

Boundaries and related work

This issue concerns metadata ingestion and maintenance. Model inference, subscription management, quota accounting, and managed model supply remain separate work.

• feat(runtime): support Claude Fable 5.1 #593: specific model support and pricing; metadata availability does not close its inference acceptance requirements.
• fix(cost): correct model usage accounting across runtimes #331: usage normalization and persistence; a new price source does not repair incorrect usage accounting.
• feat(subscription): needs support opencode Go #531 and feat(providers): support opencode go subscriptions #684: OpenCode Go integration. Keep this metadata integration separately scoped; it does not block publishing or reviewing that draft PR.
• feat(platform): plan managed model supply and usage billing #636: managed model supply and billing.

No production deployment, historical data rewrite, or model/provider expansion is implied by opening this issue.

References

• Models.dev API and data semantics
• Provider/model API
• Provider-independent models
• Combined catalog

Contribution

I can help implement and validate this integration.

Checklist

• Searched existing open and closed issues for models.dev and related catalog/model/pricing requests.
• Kept this request focused on one improvement.
• Distinguished model metadata from runtime compatibility and deployed acceptance.