Abstract token usage

I'm investigating this at this moment.
Did you start coding?

Here is a starting point, allows us to discuss if this is the direction you want.

Added as a fgork to allow tests to run, and you have some test fails so this will need further work.

I learned a lot about contributing 2.0.

The token functions are only available on chat level at this moment.
If it's needed on other output classes we probably should move these to a trait.

Just to add to the above , can we also think of a helper method to Add tracking for retry token usage and retry reasons in AI responses.

My thought is :
we are tracking the mentioned properties but it does not explicitly track retries — which can silently increase token usage and costs when outputs are malformed or invalid (e.g., bad JSON, failed function/tool calls, hallucinated responses, timeouts, etc.).

These retries consume additional tokens and can skew both performance and cost reporting if left untracked.

While total input and output tokens might include retries, but they dont tell:

• How many times a retry occurred
• Why each retry happened
• Which prompt caused it

Can we do it as a feature in AI and tke it ofrard in a seperate ticket if this really can be a good add on.
Open for suggestions

Thanks !

This merge request, together with https://www.drupal.org/project/ai_provider_openai/issues/3519302 ✨ Abstract token usage support Active
Allowed me to create this module: https://www.drupal.org/project/ai_usage_limits →

@vakulrai - we have this already in review that keeps track of parent and child unique id, maybe we should create a retry id or something similar as well, so you can track when multiple request are re-done because of validation errors. This means truly errors that fails writing the response as you like, not that its in an agent loop where the output quality is bad and a validation agent asks it to retry (this fails under normal parent/child hierarchy).

Edit: I should link also :) https://www.drupal.org/project/ai/issues/3515879 📌 Add thread id and parent id to AI calls. Active

Thanks @aspilicious - added one small comment, could you have a look and fix and then we will merge it.

Set the tag to ddd2025, so we can track user contributations that happened during Leuven :)

Hi @aspilicious, based on your comment I added some comments - its probably good if we allow null to be returned to be able to check for the difference between 0 being an actual value and it not being set at all by the provider.

Tests are failing but I don't think this patch is causing it.