Published outcome data

Agentic Batch Changes outcome definition

Published definitions and source metadata for Agentic Batch Changes.

Source metadata

General availability 2026-09-14 (cloud). The vendor names per-resolution support pricing as its model.

You pay per changeset merged into your codebase, not per token, seat, or attempt.

Class: Code change
Unit: merged changeset
Price: Not published (The vendor states that final credit rates are published in its Enterprise Portal, which is open to customers. We found no rate on its public pages.)
Authority: Vendor rule
States: merged, not merged
Since: 2026-09

What triggers a charge

A changeset counts when it is merged into the buyer's codebase.

You pay per changeset merged into your codebase, not per token, seat, or attempt.

Who decides

The buyer's own team. A changeset merges only after the team approves it.

Approve every change set before it merges.

Does silence count

Inaction never counts. A pull request that the team does not merge costs nothing.

If it opens a pull request and your team decides not to merge it, you don't pay for it.

When the conversation ends

No waiting window. The merge is the event.

If the customer comes back

Not found in the sources we reviewed on 2026-09-19.

Can a counted unit be reversed

Not found in the sources we reviewed on 2026-09-19.

Allowance and expiry

Charged in credits. The public pricing page lists no monthly credit expiry, and purchased credit buckets roll over on renewal.

Purchased credit buckets rollover on renewal

How to dispute a count

Not found in the sources we reviewed on 2026-09-19.

Merge status in the product
changeset merge status
It tracks merge status throughout, so you can see your changes going live from one place.
Source