Rovo credit consumption and status for Forge rovo:agentConnector (remote agents in Jira)

Question

Hello,

We are planning to integrate an externally hosted AI agent into Jira Cloud using the Forge rovo:agentConnector module (A2A, as described in "Integrate remote agents with Jira"). Before we roll this out, we would like to confirm a few points that we could not find in the public documentation.

Questions:

* Rovo credits: Does invoking a remote agent registered through rovo:agentConnector consume Rovo credits from our organization's pool? Please clarify for each invocation type (work item assignment, @mention , workflow transition, manual trigger, automation rule, and chat via the Rovo Chat panel). If credits are consumed, what is the rate per invocation, and do Jira's GetTask polling requests or streaming reconnections count as separate billable events?
* Extra usage billing: The Rovo credits documentation states that extra usage billing takes effect on December 3, 2026. Will this apply to remote agent invocations in the same way as to native Rovo agents?

We would be grateful for pointers to official documentation if these points are already covered.

Thank you for your help.

Mihai_LeanZero · Answer

Not documented either way. The rovo:agentConnector page and the remote agents guide don't mention credits at all.

The credits page lists "Agents in Jira" under Premium, variable credits per event, but doesn't say if that includes remote agents. The Forge pricing page says "Each agent request consumes credits ... regardless of whether the agent was built by Atlassian, created by the customer in Atlassian Studio, or distributed through a Marketplace Forge app". Remote agents aren't named. Nothing on whether GetTask polls or stream reconnects are billed either.

Matthew's guess is probably where it lands. Still, I'd measure it before extra usage billing starts on Dec 3.

Easy test. Assign a single work item to the remote agent, then export the CSV from Insights > Platform usage > Rovo credits (it has agent, timestamp and credits per row). A row for that agent means it's metered, and the credits column shows what that run cost. Premium is variable per event, so run a few. If a task that ran for minutes leaves one row, polls probably aren't billed separately.

Haven't run it against a real remote agent.

Arkadiusz Wroblewski · Answer

Hello @Damian Bielawski

Many things before the December deadline are still not confirmed by Atlassian, so without speculating, I would recommend contacting Support.

https://support.atlassian.com/jira-software-cloud/docs/collaborate-on-work-items-with-ai-agents/

https://developer.atlassian.com/platform/forge/remote-agents-in-jira/

Best,

Arek🤠🧙‍♂️

Matthew Sinclair · Answer

1: As far as I understood it - if Rovo is doing the "thing" - Rovo Credits are burned - how much depends on whether its a "new thing" - but I do know if its just reading - its less costly than creating - especially if cached (in the teamwork graph).

2: I'm going to say "Yes" because if rovo is sending commands - that's credits.

Just a guess based on what I keep seeing/reading. Glad to be wrong.

Def. willing to leave this up to the other Rovo Nerds.😁