Classic Workday AMS statements of work buy people-hours: tickets, releases, and monthly admin. Flex Credits buy metered Workday AI. When Illuminate agents, custom agents, or Developer Agent enter the estate, an AMS contract that never names credits leaves a hole between “we support the tenant” and “who pays when the agent loops.”
What Workday made measurable
Workday’s Platform Consumption Console gives UMSA customers a balance, entitlements, consumption by environment, and alerts at 80% / 90% / 100%. Usage updates daily from 2:00 PM UTC. Workday does not deactivate offers when entitlement is exceeded—someone must stop the agent.
The public Flex Credits Rate Card (November 5, 2026) prices skills from 1 credit conversational reads up through multi-hundred-credit recruiting and contracting skills, plus custom-agent invocations and tool-call blocks.
Those facts belong in the AMS commercial schedule, not only in a Workday admin guide bookmark.
Clauses AMS contracts usually lack
- Who owns the Flex Credit pool — customer Finance, the AMS provider, or a shared top-up process.
- Who receives console alerts — must include people who can deactivate agents, not only report viewers.
- What happens at 100% — Workday keeps offers running; the contract must say who decides to deactivate, throttle, or buy more credits, and within how many business hours.
- Non-Production exceptions — Deployment and Adoption agents can consume credits outside Production per Workday’s console docs; “Sandbox is free” is not a blanket warranty.
- Custom agent change control — who may raise model tier (1 / 2 / 3 credits per invocation) or add Advanced tool calls.
What not to promise in AMS language
- Do not promise real-time spend cutoffs; the console is day-lagged.
- Do not promise that crossing 100% auto-stops AI; Workday documents the opposite.
- Do not treat Flex Credits as payment for a partner’s desktop AI tools; those are separate (see Flex Credits vs Kiweely Credits).
A minimal AMS addendum outline
- Customer remains counterparty to Workday for Flex Credits purchases and UMSA policy signatures.
- Provider monitors the Platform Consumption Console for named agents and escalates at 80%.
- Provider may deactivate or restrict a listed agent only under a written customer runbook.
- Monthly report includes credits consumed by agent, not only ticket counts.
- Any new custom agent requires an estimate using Workday’s Flex Credit Estimator or Rate Card math before Production enablement.
This is commercial practice guidance grounded in Workday’s public console and Rate Card pages—not a template for counsel to paste without review.