User Problem

CSV access to usage-based consumption doesn't scale. Customers want to automate the monitoring and control of usage-based pricing.

Today, customer usage of Rovo (and soon Automation) is available through Platform Usage and manual CSV export, while controls such as *Allow extra usage* and spending limits are available only in Atlassian Administration. Administrative tools (eg Forge Apps) cannot read an organization’s current Rovo-credit consumption, allowance, or limit settings; determine the actual Rovo consumption caused by app-initiated activity; or react when the organization’s Rovo meter is paused.

This is especially an operational gap when multiple UBP capabilities are used together. Rovo used in Automation or Forge amplifies the magnitude and velocity of consumption. Administrators must leave the app and manually check Platform Usage to understand Rovo consumption or change controls, while the app itself can only infer a potential usage problem after calls begin to fail.

Suggested Solutions

Atlassian should provide secure, documented, permission-aware access to platform consumption information (UBP) and applicable controls via APIs.

The ideal solution would allow these APIs to be used in Forge Apps so that Solution Partners, Marketplace Partners, and customers themselves can build governance. The follow further describe the desirable characteristics of API access to UBP.

• An API exposing Rovo-credit consumption attributable to the calling Forge app, including Rovo agent and Teamwork Graph activity initiated by that app.
• A read-only Forge permission scoped to the organization’s Rovo Platform Usage meter, including current consumption, allowance, limit, extra-usage setting, and paused-meter status. Access should be granted through Forge installation and administrator consent rather than require an organization-wide admin API key. Many enterprise customers will not provide an organization-wide administrative credential to a Marketplace app.
• Rovo-meter metadata that identifies the usage unit, consumption to date, measurement period, allowance or limit, applicable product or workspace, and refresh behavior.
• Events or webhooks when an organization reaches standard or configurable Rovo-consumption thresholds—such as 80% and 100%—or when the Rovo meter is paused because additional usage is disabled.
• A published RFC, roadmap signal, or supported implementation pattern that Marketplace developers can follow before usage-based pricing begins.

Current Workarounds

Today, customer usage of Rovo is available through Platform Usage and manual CSV export and controls such as *Allow extra usage* and spending limits are available only in Atlassian Administration. Manual process does not keep pace with swings in usage created by apps.