Fusion Claw and AI Units: A New Rate Card, and Your Agents Still Bill Separately

Fusion Claw and AI Units: A New Rate Card, and Your Agents Still Bill Separately

What changes in the cost model when a Claw runs, what does not, and the budget controls you can use today.

In August I wrote about making sense of Oracle AI units. The insight that cleared things up for me then was simple: models Oracle hosts carry a zero multiplier, and models Oracle has to call out to are where charging happens.

Fusion Claw adds a new wrinkle to that picture, and one of our team members asked about it during our session with Oracle's Fusion AI product management team. Here is what we learned.

Same meter, new rate

The meter does not change. An AI unit still represents the tokens processed combined with the complexity of the type of action. Today, nearly everything is a general action, which is the cheapest category.

What is changing is the set of rates. Oracle is publishing new rates for new capabilities: one for document generation, one for audio and video generation, and a new rate card it calls Frontier for Claw work.

The Frontier multiplier was not confirmed in our session, so I am not going to guess at one here. Watch for it on the rate card.

What the Frontier rate covers

For a Claw, consumption is mostly the orchestration work: the frontier model doing the planning and reasoning. It is based on the tokens processed, and it is independent of the agents.

Your agents still bill

This is the part worth getting right in a forecast.

When a Claw asks an agent to execute something, that agent is still doing its own work, using its own model, under the rate for the type of action it performs. The Claw does not absorb or replace that consumption.

So the cost of a Claw run is two things added together: the Claw's own orchestration at the Frontier rate, plus whatever each underlying agent consumes along the way.

That is consistent with what Oracle told us in August about agentic apps: same meter, more moving parts. A Claw is one more moving part, on a different rate.

Why the hosted model escape hatch does not apply

In my earlier post I suggested starting any Fusion AI cost model by working out which use cases genuinely need a premium model, and assuming the rest can run on Oracle-hosted inference at no incremental cost.

That framing still works for agents. It does not work for the Claw itself. Oracle told us that GPT-OSS, the hosted model with the zero multiplier, is not capable enough for Fusion Claw, and that frontier models are required.

Fusion Claw is inherently premium. The question shifts from which model a Claw should use to whether a given outcome justifies a Claw at all, or whether a standard agentic app interaction will do.

What you need to have

Fusion Claw is accessed through agentic apps, so you need the agentic app SKU. That SKU includes an allotment of AI unit credits, and if your usage grows beyond it, you buy additional AI units for that consumption.

As before, I am deliberately not quoting figures. Have that conversation with your account team early.

Budget controls you can use in 26D

One of our architects asked the question every platform owner is thinking: what happens when someone kicks off something ambitious and it runs for nine hours straight?

The answer was partial but useful. In Agent Studio in 26D you can set AI unit budgets at three levels:

·        An entire environment

·        An individual agentic app, which includes its Claw usage

·        An individual agent

You can also tell it what to do when a budget is reached: stop execution, or let the current work finish. And there is a kill-all button. As it was put to us, kill -9 for the Unix users.

What is not there yet:

·        User-level budgets. You can see what individual users are consuming, but you cannot set a budget per user.

·        Events or APIs for budgets. These controls live in Agent Studio today.

Oracle described work in progress on both fronts: exposing operational observability data through something like an OpenTelemetry stream so you can monitor it in your own systems, and APIs to set budgets, stop agents, and manage user access from the outside. Until those land, budget management happens in Agent Studio.

What I would do

Set budgets before the first Claw run, not after the first surprise. At minimum, put an app-level budget on every Claw-powered agentic app you enable, and an environment-level budget on anything that is not production.

And apply the same discipline I argued for in August, one level up. Before reaching for a Claw, be clear on why the outcome needs long-running, frontier-model reasoning rather than a point-in-time agentic app interaction.

What I am still watching

·        The published Frontier multiplier.

·        Whether a single Claw run can be broken down into its Frontier consumption and its underlying agent consumption, which is what a finance conversation will ask for.

·        Whether the ROI dashboard in Agent Studio reports on Claw outcomes the way it does for agents.

Based on a working session between our team and Oracle's Fusion AI product management group in October 2026, combined with Oracle's public announcement of Fusion Claw on September 29, 2026 and Oracle's public documentation. I am reporting a conversation, not a contract. Product details and pricing mechanics change between releases. Confirm specifics against your own environment, rate card, and Oracle account team. Views are my own.