model-registry-maintainer

To update the model registry, you synchronize both capabilities.py and token_manager.py with the latest provider documentation to adjust context window limits and pricing. This ensures the registry stays aligned with provider releases during rollouts or audits.

You need to add a new model entry to capabilities.py during new model launches or provider updates. This involves consulting provider documentation to populate exact model names, capabilities, and release dates accurately.

The best way to keep registry capabilities and pricing aligned is applying registry maintenance during model rollouts. This requires consulting provider documentation to populate exact pricing and context window data across core files.

Yes, you must consult provider documentation to update token_manager.py. Populating exact model names, release dates, capabilities, and pricing requires referencing official provider data to keep the registry accurate.

A registry audit shows incorrect release dates or context window limits when capabilities.py and token_manager.py fall out of sync with provider updates. Running validation steps and updating both files resolves the mismatch.