What changed
Atlassian announced on September 1 that expanded usage-based billing for Rovo credits, automation steps and AI agent resolutions begins December 3, 2026. Its current Rovo documentation explicitly includes enriched Teamwork Graph context accessed through the Rovo MCP server and Teamwork Graph CLI, including unified search and cross-product queries. Most enriched context tool calls consume 1–10 Rovo credits, while basic Rovo interactions consume 10 and premium AI features vary. Included monthly credits are pooled across an organisation; extra usage currently lists at $0.01 per credit. Installing MCP, simple single-product lookups and write operations remain free.
Why it matters
Builders using Claude, ChatGPT or custom agents to interrogate Jira and Confluence can no longer treat every enriched context retrieval as an unmetered integration call. Query design, cache policy, agent loop frequency and spending caps become part of operating cost. A simple work-item lookup is not the same billable event as a Teamwork Graph traversal. This creates an actionable distinction for small teams before December 3, without implying that every Jira API call or MCP tool invocation will be charged.
The boundary is enriched context, not every API request
Atlassian documents free single-product lookups and writes, including looking up a Jira issue or updating it. Enriched Teamwork Graph searches and cross-product relationship queries are metered, including searchAtlassian and context tools invoked through Rovo MCP or TWG CLI. The vast majority of these enriched calls consume 1–10 credits, depending on the operation.
The cost model sits above existing subscriptions
Standalone Jira and Confluence plans include 25 Rovo credits per user per month on Standard, 70 on Premium and 150 on Enterprise. Teamwork and Service Collections include higher per-user allowances. Credits pool across the organisation and reset monthly. Beyond the included pool, the published list price is $0.01 per credit, with prepaid options and discounts.
Controls matter for agent loops
Atlassian says extra usage is enabled by default on its general Rovo billing documentation, with alerts at 80% and 100% of allowance and optional spending ceilings or disabling overage. When metered capacity is exhausted with extra usage off, affected enriched calls pause. Its Teamwork Graph CLI FAQ separately describes an explicit opt-in, so admins should confirm the setting on their own organisation rather than rely on an assumption.
Founder evidence illustrates the risk but not a universal price
SaaStr founder Jason Lemkin says its 21-plus agents make 35,000–40,000 vendor API calls per day and describes an unverified estimate of up to $240,000 annually for future agent access across multiple vendors. That is an operator's scenario, not an Atlassian rate card or proof that all those calls are billable. The relevant lesson is to meter real workflows before a usage policy goes live.