The Fusion Agentic Applications fee, decoded.

The Fusion Agentic Applications subscription is a separate platform fee that unlocks production publishing and the Agentic Applications Builder. Publishing an application to production triggers it, and upgrading to 26C does not. This guide covers what the fee buys, what Oracle has published about the price, and how to hold the line inside your Fusion renewal.

What is the Fusion Agentic Applications subscription?

It is a separate platform fee granting two things: the right to publish agentic applications into a production environment, and access to the Agentic Applications Builder. Oracle introduced it alongside 26C, in the Fusion Agentic Applications announcement of 24 March 2026.

It does not replace the AI Unit meter and it does not license the agents themselves. It sits above both. The meter prices the work an agent performs; the platform fee prices the right to run a composed, multi step application in production.

What does the platform fee include?

• The production publishing right. The entitlement to move an agentic application from a test pod into a live one.
• The Agentic Applications Builder. The composition tooling for chaining agents, tools and human approval steps into one application, described in Oracle's Agentic Applications Builder announcement.
• A bundled annual unit allowance. In the ordering documents we have read, a yearly block of AI Units sits inside the fee, on top of whatever monthly grant your base subscription carries.

What actually triggers the fee?

Publishing an agentic application into a production environment triggers it. Not the 26C upgrade, not enabling a feature flag, and not building the thing. Oracle's guidance on when a Custom AI Agent subscription applies is the closest published statement of where the entitlement boundary sits.

The practical consequence is a window. Everything up to the production publish is planning time you already own, and the platform fee falls due on a date you can put in a project plan rather than a date Oracle picks.

What has Oracle actually published about the price?

Almost nothing, and any honest guide has to say so. Oracle's public product page for AI Agents for Fusion Applications carries capability detail and no commercial terms. Neither March 2026 announcement states a rate, an allowance or a pack price.

Everything circulating as the commercial model comes from price list extracts, ordering documents and third party write ups. That does not make it wrong. It makes it undated, unguaranteed and unusable as a negotiating anchor unless you get it restated in your own paperwork.

Why a reported rate is not a list price

A list price is a published number the vendor stands behind until it republishes. A reported rate is a snapshot somebody took of a document that is revised without notice. Only one of those survives contact with a procurement challenge.

The failure mode is specific and we have watched it happen. A buyer anchors a business case on a figure from an article, Oracle quotes a different number, and the buyer has nothing to point at because the source was never Oracle's own public material.

What to get in writing before you sign

1. The trigger, stated as an event. Ask for a sentence naming production publishing as the act that starts the fee, so the upgrade cannot be read as the trigger later.
2. The unit rate, held for the term. Without a price hold, a list revision reprices your whole meter in the middle of your subscription.
3. The status of the monthly allowance. Contractual or promotional is a one word answer that changes every forecast you will build.
4. The size and expiry of the bundled block. Establish whether unused bundled units roll forward, expire, or offset the next term.
5. A spend cap with an alert. A ceiling on monthly unit spend, with notification before it is reached, converts an open meter into a budget line.

How is the platform fee different from AI Unit consumption?

The platform fee is a fixed entitlement and AI Units are variable consumption, so they behave differently, budget differently and are negotiated differently. One is a right to publish, the other is a meter on work performed. Treating them as a single bundle is the most common costing error we see on 26C proposals.

Why budget them as two lines?

Because they move in opposite directions and at different times. Unit burn climbs with adoption from the first agent onward, while the platform fee is a step that lands once and then stays flat.

Merging them into a single AI budget hands the vendor a packaging advantage. Every conversation then becomes a discussion about a blended number, and blended numbers are where fixed fees hide inside variable ones.

How do you size the bundled allowance honestly?

Size it from measured burn in a non production environment, extrapolated to your real user population, and nothing else. A forecast built from an Oracle sizing worksheet is a forecast built from Oracle's assumptions about your adoption curve.

• Run the pilot for a full month. Weekly extrapolations miss period end spikes, which are where agent traffic concentrates in finance and supply chain.
• Separate human triggered from scheduled runs. Scheduled agents produce a floor you cannot manage down without changing the design.
• Record the model tier per agent. Tier choice moves unit draw more than agent count does, so a burn figure without a tier breakdown is not reusable.
• Add a variance band, not a buffer. Present the range to whoever signs, so the commitment decision is made with the uncertainty visible.

What does the subscription commit you to?

An annual platform fee for the term of the order, plus whatever bundled units the sizing carries. Its value depends entirely on whether production publishing is real inside that term. For a buyer with live agentic applications it can be efficient, and for a buyer still running design workshops it is a prepayment.

The term, the renewal and the quiet growth clause

Read the term dates against your Fusion subscription end date before anything else. A platform fee that runs on its own calendar creates a second renewal event, and a second renewal event is a second opportunity for an uplift you did not plan.

Check also how the fee behaves if your Fusion user counts grow. Where the platform fee is expressed against a band rather than a flat figure, ordinary headcount growth can move you into a higher band without any new decision being taken.

A worked example: three publishing paths, same estate

Take one Fusion estate and three plausible plans for the next twelve months. The platform fee is identical in all three. What changes is how much production work it supports, and therefore what it is worth.

The middle row is where most buyers actually sit and where most of the money is lost. Signing a full year fee for seven months of shelf time is a discount problem you created yourself, and it is easier to fix with a start date than with a percentage.

Separate

Fee from AI Unit consumption

Publish

The internal act that starts the clock

Renewal

The only sensible moment to price it

Source: Redress Compliance advisory engagement file, 2024 to 2026, read against Oracle ordering documents.

Where the common advice on the Agentic Applications subscription is wrong

The standard account team position is that the platform fee is a necessary part of moving to 26C, and the standard buyer response is to argue about the percentage. We disagree with both. In the Fusion deals we have advised, the fee is triggered by publishing an application to production, and the value of the delivered agents plus the monthly grant carries most customers well past the upgrade without any publishing at all. The argument worth having is not about rate. It is about the start date, the length of the first term, and whether the bundled block is sized to a burn figure anyone has actually measured. Buyers who win this line win it on timing, not on discount.

What to check before you sign

• The publishing plan, in dates. Name the applications, the pillars and the release windows. If nobody can, the fee is premature.
• The bundled block against measured burn. An allowance you will not consume is a discount that never lands.
• The entitlement boundary. Read Oracle's Custom AI Agent subscription guidance and mark which of your planned agents sit on each side of it.
• The co termination. Align the platform fee end date with the Fusion subscription end date so you keep one negotiation, not two.

How do you negotiate the platform fee?

Fold it into the Fusion renewal and price it against a dated production plan. Pulled out as a standalone purchase, it is a small deal Oracle can price in isolation. Folded in, it is one line inside a relationship where you still hold something Oracle wants.

The platform fee is not the price of 26C. It is the price of publishing to production, and that is a date you write.

How does timing change the deal?

It changes it more than any other variable, because the trigger is an event you schedule. If the first production application lands in month nine, a fee starting in month one is eight months of shelf time you paid full price for.

The three timing moves that work are a deferred start date, a short first term that snaps back to the Fusion anniversary, and a ramp where the bundled block grows across the term rather than arriving in full on day one.

Five clauses worth more than the discount

What to say when the fee first appears in the quote

Say less than you think, and ask three questions in a fixed order. The order matters because each answer narrows the next.

1. Ask what act triggers the fee, and ask for it in writing. You are establishing whether the seller will commit to the reading their own documentation supports.
2. Ask what happens if we do not publish this term. A seller who says the fee is due anyway has just told you the fee is being sold as an upgrade tax.
3. Ask how the bundled block was sized. If the answer references a standard model rather than your pilot data, the block is a list construct and the size is negotiable.

Then stop. The most common buyer error at this point is to volunteer a production date that has not been agreed internally, which converts a planning assumption into a commercial commitment.

Who inside your organization can trigger this fee?

Whoever holds the privilege to publish an agentic application into a production pod. That is an operational permission, usually held by a small group of configurators or a delivery partner, and in most estates nobody has ever mapped it against a commercial consequence.

This is the single cheapest control on the page. A vendor cannot trigger the fee. Only your own release process can, so the release process is where the spend control belongs.

• Name the privilege holders. List every account with publishing rights in every Fusion environment, including partner and contractor accounts.
• Put publishing behind a gate. Require a named approver, the same way you would for a chart of accounts change.
• Separate the environments in policy, not just in practice. Write down which pods are production for this purpose, so a test pod promoted quietly does not become an argument later.
• Tell the delivery partner. Implementation teams publish to prove progress. They are not measured on your subscription line.

The agent register that makes this manageable

Keep one sheet with six columns: agent name, business owner, template or custom, model tier, environment, and expected monthly runs. Update it at every release. It takes an hour a month and it answers every question Oracle will ask you.

The register also does the work at renewal. When Oracle proposes a bundled block, you can hold up measured burn by agent and by tier instead of accepting a sizing worksheet built on generic assumptions. The full model sits in the Fusion AI Agents pillar, and the build layer is covered in what AI Agent Studio includes.

What should a buyer do next?

Work this sequence before you accept any platform fee proposal. It is ordered so that each step gives you the evidence the next one needs.

1. Confirm in writing that production publishing, and not the 26C upgrade, is the trigger.
2. List every planned agentic application with its pillar, its owner and its intended release window.
3. Run a full month of pilot burn in a test environment and record units by agent and by model tier.
4. Value the bundled block against that measured burn, and present the range rather than a point estimate.
5. Inventory who holds publish privileges and put a named approval gate in front of them.
6. Negotiate the start date, the first term length and the renewal cap inside the Fusion renewal, not as a separate purchase.
7. Ask the Oracle practice team to read the ordering document before signature, covered on the Oracle practice page.

Frequently asked questions

What is the Fusion Agentic Applications subscription?

It is a separate platform fee granting the right to publish agentic applications to production and access to the Agentic Applications Builder. Oracle introduced it alongside 26C on 24 March 2026. It is distinct from the AI Unit meter, and in the ordering documents we have read it also carries a bundled annual block of units.

What triggers the Agentic Applications platform fee?

Publishing an agentic application into a production environment triggers it, not the 26C upgrade and not a feature flag. Testing in a non production pod does not commit you. Because the trigger is an internal release action, the practical control is your own change management gate rather than anything in the contract.

Has Oracle published the price of Fusion AI Agents?

No, Oracle's public product and announcement pages carry capability detail and no commercial terms. The figures in circulation, including a unit rate near one cent and a monthly grant of 20,000 units, are reported and corroborated by third parties rather than published by Oracle. Treat them as a dated snapshot and get your own numbers restated in the ordering document.

Is the platform fee the same thing as AI Units?

No, the platform fee is a fixed annual entitlement to publish, while AI Units are variable consumption metered on agent actions. You can burn units against delivered agents without ever paying the platform fee, and you can hold the platform fee while burn stays inside the monthly grant. Budget them as two lines that move independently.

Do you need the subscription to upgrade to 26C?

No, the upgrade does not require the Agentic Applications subscription. Most customers get real value from the agents delivered inside applications they already own, plus the monthly unit grant, long before anything is published to production. The subscription becomes relevant at the publishing moment, which is an event you schedule.

How should the bundled unit allowance be sized?

Size it from a full month of measured pilot burn, broken down by agent and by model tier, extrapolated to your real user population. Present a range rather than a single number so the person signing sees the uncertainty. A block sized from a vendor worksheet reflects vendor assumptions about your adoption curve, not your data.

When is the right moment to negotiate the platform fee?

Inside your Fusion renewal, timed to the first real production application. Folding it into the wider agreement keeps the whole relationship in play as leverage, and lets you trade the start date and first term length rather than argue about a percentage. Bought separately and late, it is a small deal Oracle can price on its own terms.

What happens if a test agent is accidentally published to production?

Assume the entitlement question follows, because the act that matters has occurred regardless of intent. Log the publish, roll it back, and record the sequence with timestamps before raising it. Buyers who can show a controlled release process and a prompt reversal are in a materially stronger position than buyers who discover it during a review.