The list-currency-reports API is for Power Platform “currency” consumption reporting, so the AI category can include AI capacity usage, but I would not assume it is only Copilot Studio usage.
Based on Microsoft’s current licensing model, AI Builder credits and Copilot Credits can overlap during the transition period. AI Builder features in Power Apps/Power Automate can consume AI Builder credits first, then fall back to Copilot Credits when AI Builder credits are unavailable or exhausted. Microsoft is also moving toward Copilot Credits as the long-term currency for AI usage.
So in practice:
“AI” in the currency report is not necessarily equal to only Copilot Studio agent usage.
It may include AI Builder-related consumption, especially if AI Builder actions/prompts are being used in Power Apps, Power Automate, or Copilot Studio agent flows.
It may also reflect Copilot Credit consumption, depending on the environment and licensing setup.
The API response should be treated as a tenant/environment-level AI currency consumption report, not a clean “Copilot Studio only” report.
For Copilot Studio-specific usage, I would cross-check with:
1. Power Platform Admin Center → capacity / licensing / Copilot Credits usage.
2. Copilot Studio analytics for agent-level activity.
3. AI Builder activity / AI Event table in Dataverse for model-level AI Builder usage.
4. Environment-level filtering in the API response, if available.
My interpretation: the endpoint is useful for overall AI credit/currency reporting, but not enough by itself to separate Copilot Studio credits vs AI Builder credits unless the response includes a more detailed meter, product, or workload dimension.
