>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3604256. --> Reported by: [codeitwisely](https://www.drupal.org/user/1210320) >>> <h3>Problem/Motivation</h3> <p> ai_metering syncs model pricing from LiteLLM<br> (<code>model_prices_and_context_window.json</code>). The source URL is hardcoded<br> in the sync service and <code>SyncPricingCommand</code>. There is no way to use<br> an alternative source without patching the module. </p> <p> In the AI Initiative issue #3586519, Marcus Johansson mentioned<br> <code>models.dev/api.json</code> as the preferred pricing source for the Initiative.<br> Albert Albala suggested independently that the pricing source should be a Drupal<br> Plugin so the community can add sources without forking. Sites with air-gapped or<br> on-prem deployments may also need a local static file. LiteLLM remains the best<br> default, but the architecture should not prevent alternatives. </p> <h3>Steps to reproduce</h3> <ol> <li>Open the AI Metering Settings page.</li> <li>There is no option to select a pricing source &mdash; LiteLLM is the only source and it is hardcoded.</li> <li>Pricing from <code>models.dev/api.json</code> cannot be used without a code change.</li> </ol> <h3>Environment</h3> <ul> <li>Drupal version: 11.3.11</li> <li>ai_metering version: 1.0.0-alpha1</li> <li>AI provider module + version: any (e.g. ai_provider_anthropic 1.2.2)</li> <li>AI feature module tested: N/A</li> </ul> <h3>Proposed resolution</h3> <p> Introduce a <code>PricingSourceInterface</code> as a Drupal annotated Plugin type<br> with a <code>PricingSourcePluginManager</code>. Each implementation returns a<br> list of <code>ModelPrice</code> value objects<br> (<code>provider</code>, <code>model</code>, <code>input_per_million</code>,<br> <code>output_per_million</code>, <code>cache_read_per_million</code>,<br> <code>cache_write_per_million</code>, <code>currency</code>). </p> <p> Ship two implementations: <strong>LiteLLMPricingSource</strong> (current behaviour,<br> becomes the default) and <strong>ModelsDotDevPricingSource</strong> (fetches and<br> normalises <code>models.dev/api.json</code>). The active source is selected on the<br> Settings page. Third-party modules can provide additional sources by declaring a<br> plugin in their namespace. </p> <h3>Remaining tasks</h3> <ul> <li>Define <code>PricingSourceInterface</code> and <code>PricingSourcePluginManager</code>.</li> <li>Define <code>ModelPrice</code> value object.</li> <li>Refactor existing LiteLLM sync into <code>LiteLLMPricingSource</code> plugin (default).</li> <li>Implement <code>ModelsDotDevPricingSource</code> plugin with schema normalisation.</li> <li>Add pricing source selector to the admin Settings form.</li> <li>Update <code>SyncPricingCommand</code> and the cron sync service to use the plugin manager.</li> <li>Add unit tests for both implementations against fixture responses.</li> <li>Review.</li> </ul> <h3>User interface changes</h3> <p>Yes, the Settings page gains a "Pricing source" selector (LiteLLM or models.dev, with the option for contributed sources).</p> <h3>API changes</h3> <p>Yes, introduces a new <code>PricingSourceInterface</code> Plugin type and <code>PricingSourcePluginManager</code>. Third-party modules can implement the interface to provide custom pricing sources.</p> <h3>Data model changes</h3> <p>N/A, pricing data is stored in Drupal State; the structure is unchanged.</p> <h3>AI assistance</h3> <p>N/A</p>