Developer Agent is metered by invocation. An invocation is a query or command you submit while developing in Workday Build. The chat box on the Developer Site and a plugin or connector in a desktop IDE are the same meter. A follow-up that says “now add a column” is another invocation. So is “Reject this and try again.”
The rate card, last updated November 5, 2026, prices a Developer Agent invocation at 2 Flex Credits. Footnote 5 says credits are consumed only after the customer passes an annual entitlement of 50,000 invocations. That entitlement resets on each anniversary of the subscription start date, is prorated for a partial period, and expires without rollover. The card says the rates are informational as of that date and are not a formal offer. The entitlements page tells enterprise customers to read the rate card for the initial entitlement and for the credits each invocation type uses.
Personal accounts and partner accounts are not on that Flex Credits path. The mistakes below all come from treating every account as if it were an enterprise customer with a soft overage.
The seven mistakes
1. Treating the conversation as one charge
Developer Agent keeps multi-turn context. That is a documented feature: it refactors earlier code, reviews it, and explains it. The meter does not care that the context is the same thread. Each query or command counts. A home page, a create page, and a manage page, plus two corrections, is five invocations, not one “build the app” session.
Ask for a summary of a concept, or “what’s the deployment status of myApp,” only when you need the answer. Those are invocations too. The prompt guide lists them as normal uses. They are not free lookups.
2. Assuming the IDE is outside the meter
Workday meters Developer Site chat and a supported third-party coding tool at the same rate. Installing the Developer Agent extension in Claude Code, Cursor, VS Code, or Google Antigravity does not open a second, unmetered bucket. A team that “just tries it in the IDE” while another person uses App Builder is sharing one entitlement, not splitting a free sandbox from a paid one.
Developer Copilot for Orchestrate is the exception Workday bothers to print: that usage does not count toward the Developer Agent invocation entitlement. Do not use that sentence to argue that Orchestration Builder work in general is free. The exclusion names Developer Copilot for Orchestrate.
3. Assuming a personal Build account can buy Flex Credits
The tutorials tell you the Workday Build account and development tenant are free to create. The entitlements page then says a personal account has a lifetime invocation entitlement. When usage passes it, Developer Agent stops responding to new requests. The page does not say the personal account then draws Flex Credits, and it does not publish the lifetime number. “The tenant was free” is not “the agent is unlimited.”
Watch the three-bar icon in the Developer Agent header. That view is available on personal accounts. There is no Entitlements Dashboard for a personal account. That dashboard is for enterprise customers and for partners and producers. The Platform Consumption Console under Agentic Platform is enterprise-only, and it lives in the production tenant.
4. Assuming a partner or producer account overages onto the rate card
Partners and producers get an entitlement that resets at the start of each calendar year, not on a subscription anniversary. When they pass it, Developer Agent stops until the next calendar year. Enterprise customers are the group Workday describes as extending with Flex Credits after the contract-year entitlement. If a partner demo environment suddenly goes quiet in November, the calendar-year cap is the published explanation to check before you file a defect.
5. Mixing Developer Agent credits with custom-agent and tool-call credits
The same rate card prices other meters that look similar and are not:
| Offer | Meter | Credits |
|---|---|---|
| OfferDeveloper Agent invocation | MeterPer invocation, after the annual entitlement | Credits2 |
| OfferCustom agent invocation | MeterPer invocation, by model tier | Credits1 base, 2 standard, 3 premium |
| OfferAgent-ready tool call, base | MeterPer 100 calls | Credits5 for custom agents, 10 otherwise |
| OfferAgent-ready tool call, advanced | MeterPer 100 calls | Credits25 for custom agents, 50 otherwise |
| OfferPipedream tool call | MeterPer 100 calls | Credits5 for custom agents, 10 otherwise |
| OfferCore platform API requests | MeterPer 10,000 calls, ingress and egress | Credits60 |
Footnote 6 says model tiers, tool catalogs, and invocation types are described further on the Developer Site. A custom agent your app registers is not a Developer Agent invocation. A tool call the running agent makes is not one either. Budget them separately. An app that “only used Developer Agent a little” can still spend tool-call credits in production once people chat with the agent you deployed.
6. Letting the unused half expire, then bursting in the next month
Unused Developer Agent entitlement expires at the reset. It does not roll. A team that avoids the agent all year and then generates an entire catalog of apps in the last month does not get the quiet months back. The opposite mistake is also real: a generate-and-reject loop in week one, because the agent can iterate on its own errors, burns the entitlement before anyone has a deployed app. The overview lists “validate its own work in real time” and “iterate and fix its own errors” as features. Each of those turns is still a submission.
7. Reading “2 credits” as the price of the first prompt
Footnote 5 is the whole price. The 2 credits apply after the annual entitlement. Quoting “2 Flex Credits a prompt” to a finance partner, without the 50,000, overstates the bill for a customer inside the entitlement and understates the cliff for a personal account that cannot buy credits at all. The marketing page says Developer Agent is generally available starting 2026R2+, through Workday Extend Professional, and will include Flex Credits-based pricing. That sentence points you to the rate card. It does not replace footnote 5.
The card also says rates for generally available skills are locked for the customer’s order term, and that new offers show up in the Platform Consumption Console at release. If a number on a slide disagrees with the console, the card tells you the console is where a newly released offer is priced for the rest of the term. It also says Workday can end an offer.
What to do before a long session
- Open the three-bar icon and read the remaining entitlement. On an enterprise account, an admin can also open Account, then Entitlements Dashboard.
- Write the prompt so the first response is reviewable. Name the business object, the fields, and the route. A vague prompt plus three corrections costs four invocations and often a worse diff.
- Reject a bad diff once, with a tighter prompt, instead of nudging one widget at a time.
- Keep Developer Copilot for Orchestrate, custom-agent runtime, and tool calls in a different column of the spreadsheet. They are different rows on the card.
- If the account is personal or a partner, plan to stop when the entitlement ends. There is no published “top up” for those accounts.
Frequently asked questions
Does a question about my app count the same as “build a page”?
Yes. The entitlements page defines an invocation as a query or command you submit. “What’s the deployment status of myApp” and “create a PMD” are both submissions. Workday has not published a cheaper rate for questions.
If I never hit 50,000, is Developer Agent free for an enterprise customer?
Inside the annual entitlement, the rate card says Flex Credits are not consumed. You still need the Extend Professional access the marketing page describes. The entitlement is prorated and it expires. It is not a perpetual free tier.
Will a personal tutorial tenant start charging 2 credits when the lifetime cap is gone?
The entitlements page says Developer Agent stops responding. It does not say a personal account begins consuming Flex Credits. Do not plan a class or a hackathon on the assumption that you can buy overage.
Where is the number I should quote in a budget?
The rate card dated November 5, 2026, and the entitlements page. Quote footnote 5 with the 2-credit row, and say the card is informational. Then check the Platform Consumption Console for the account you are actually buying for.