Changelog

Discovery

• Models are ordered by release date, with the newest versions first.
• Providers use a combined ranking based on provider type and supported model count.
• Organizations use a combined ranking across models, providers, and latest release date.
• Search filters use consistent component-based selects, with input and output modality and capability tags.

Comparison

• Model comparison is now a dedicated page instead of a modal.
• The comparison page can add models through a searchable selection dialog.
• The model Active label was removed: a model is available when at least one provider supports it.

Administration and product quality

• The admin model editor now covers the complete model parameter set.
• The admin dashboard uses real catalog data.
• Empty detail sections, Deployment, and the unused data-source panel were removed.
• Table columns and localized labels were adjusted so important values remain readable in every supported language.

Open the comparison workspace to inspect the current catalog.

What shipped

• A canonical identity hierarchy: Organization -> Model Family -> Model Version.
• Stable model IDs, slugs, aliases, release dates, input and output modalities, capability tags, relations, and resources.
• A separate delivery layer: Provider -> Provider Offering -> Pricing.
• Static catalog publishing backed by D1, with public pages for models, providers, and organizations.

Product boundary

ModelRegistry owns the canonical model identity and public URLs. A provider's model ID is stored as offering data and is not used as the platform's primary identity. Deployment and source-observation records are outside the product model.

Browse the model catalog or start with the organization directory.