Full narration of the briefing. Click a section heading to jump the player to that moment.
For fifteen years the Workday commercial model was one number: a subscription per employee per year, per module, with unlimited use inside it. Agents broke that model. Workday has moved its AI agents onto Flex Credits, a pre purchased pool metered per action, and introduced Platform Entitlements, an annual allowance of production API calls above which your integrations draw credits too. I am Tom, Claire is with me, and this briefing is how the two meters work, what counts, why the free credits are a lever rather than a gift, and what to negotiate before the API grace period ends on February first, 2027.
Every agent skill carries a fixed credit cost per unit of work. A Sana platform or self service action is one credit. A payroll missing data check, five per ten worker records per run. A resume screened and matched, six.
Standard API calls above your entitlement, sixty per ten thousand. A full contract negotiation review and redline, five hundred per document. And talent rediscovery or internal mobility retrieval, seven hundred fifty per requisition. Workday has published all of this in credits and none of it in dollars, and independent estimates run from under one cent to ten cents a credit.
That range is the whole negotiation.
The second meter is the API allowance. Every customer gets an annual entitlement of production API requests sized by employee count, two and a half to six and a half million by segment, lifted by the SKUs you hold: Extend adds fifty percent, Procurement and Accounting Center one hundred each. Above the allowance every call converts to Flex Credits at sixty per ten thousand. What does not count: Workday built agents, unmodified delivered integrations, Built on Workday apps.
What counts: Studio integrations, modified delivered integrations, partner integrations, and any external AI agent calling the tenant. For a large estate that is most of the integration layer.
Year one looks free, and that is by design. Workday grants complimentary credits by company size: fifteen thousand a year under thirty five hundred employees, up to two hundred thousand above one hundred thousand. Its stated purpose is usage data to size a paid subscription. It is the vendor's discovery phase, run on your tenant.
The credits do not roll over, do not stack across order forms, reset on January first, and Workday may reduce or withdraw them at the renewal of the underlying order form. So the number that makes year one comfortable is a lever, not an entitlement, and it will be traded.
Here is the illustration: a forty five thousand employee HCM and Financials customer, first year. Self service actions, twenty five per employee, one point one million credits. Talent rediscovery on twelve hundred requisitions, nine hundred thousand. Payroll missing data checks, five hundred eighty five thousand.
Resume screening on sixty thousand resumes, three hundred sixty thousand. And twenty million API calls against a six million baseline, another eighty four thousand. About three point two five million credits against one hundred twenty thousand complimentary. At one cent to ten cents a credit, the overage is thirty one thousand to three hundred thirteen thousand dollars a year.
Scoped and negotiated, the same estate runs forty to sixty percent lower.
Watch three dates. September first: the promotional period ended and the Self Service Agent started consuming credits, so this month is the first time the complimentary pool is drawn down by the agent every employee uses. January first, 2027: complimentary credits reset. January thirty first, 2027: the API overage grace period ends, and from February first production calls above the entitlement draw credits, and an empty pool triggers a purchase.
Workday is not charging for API overage today, but the meter is running and the Console is recording it. The grace period is a free audit of your API estate and a free pilot of every agent, if someone reads it before Workday's account team does.
The move from this briefing. Read what you signed: the UMSA addendum and the policy are contract changes, not enablement paperwork. Own the Console: name an owner and export consumption by agent and component every month. Classify every integration as counted or excluded, replace counted ones with delivered connectors, and stack every baseline uplift you are entitled to.
Put the seven hundred fifty credit skills behind an approval step. Then negotiate the four numbers into the order form: the per credit price with tiers, a committed pool with rollover, the API baseline as a contractual figure, and the complimentary allotment protected through the term. The full research note is free to download under this video, at redresscompliance dot com slash newsletter slash september.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Workday negotiator