---
title: "Data Cloud, agents, Flex Credits — Kiweely"
description: "Flex Credits are fungible across agents and Data Cloud, but Data Cloud is a separate public-cloud SKU with its own zero-copy paths."
url: https://kiweely.com/blog/workday-data-cloud-agents-flex-credits
---

# Data Cloud, agents, and Flex Credits

Platform Consumption Console meters agent skills and Data Cloud on one Flex Credit balance for UMSA customers. Data Cloud itself is a separate license, public-cloud only, and it does not turn Live Data Query or the Iceberg data lake into a Workday-built agent.

-   By Kiweely
-   November 16
-   5 min read

Flex Credits are Workday’s usage credits for AI and platform innovations. Data Cloud is one of the things those credits can pay for. Agents are another. They share a balance. They are not the same feature, and turning on an agent does not enable Data Cloud.

Workday’s Flex Credits marketing page says you pay for work completed rather than tokens, that complimentary credits let you explore agents in Production, and that most agents can be tested in non-Production without that charge. The only worked rates on that page are examples: Self-Service Agent instant information retrieval at 1 credit per action, and autonomous task completion at 5 credits per action. Every other skill’s rate is on your Rate Card, not in this article.

## What Data Cloud is

Data Cloud is its own SKU. The tenant must be public-cloud hosted. You need a contract with a supported partner platform. Workday’s examples are Salesforce, Snowflake, Databricks, and Google Cloud. You must subscribe to Flex Credits to access Data Cloud products. Zero-copy connectivity is limited to specific partners. It is not a general JDBC connection to any tool you have.

The suite is bidirectional and zero-copy: external systems read Workday objects without an ETL copy, and Workday can see external data.

| Direction | Piece | When Workday says to use it | Access |
| --- | --- | --- | --- |
| Out | Live Data Query | Real-time SQL over JDBC or Python | ISU for table and column security, or user-as-self for Workday’s full security model including rows and cells |
| Out | Data Lake | Large analytics where a daily Iceberg refresh is enough | Table-level access. Data stays in Workday until read. |
| In | Zero-Copy Data In | Live virtual access from Prism Data Catalog | Prism domains |

Live Data Query’s own page suggests ISU authentication for data platforms such as Snowflake, and user-as-self for analytics tools and for AI, LLMs, and agents. The example agent client is Gemini. That is an external client querying Workday through Data Cloud. It is not Agent Management Hub registering a Workday-built agent.

User-as-self uses a browser login plus an API client. ISU uses a key pair and domain permissions on an unconstrained security group. Pick that before an agent platform gets a service account that can see every worker.

Workday also says Live Data Query can replace some custom RaaS extracts, and that Prism can blend external and Workday data. Accounting Center can ingest through Prism or reference external data for journals. Data Cloud is described as a data foundation for Workday Build. None of those sentences say a reporting agent or a planning agent runs inside the lake.

## How the same credits get spent

Platform Consumption Console is on for MSA and UMSA customers. Everyone can see API requests and document storage. Only UMSA customers track agent usage and the Flex Credit balance. Flex Credits exist only for UMSA customers, either under the Complimentary Flex Credits Policy in the UMSA product terms or under the Flex Credits and Platform Entitlement Policy on an order form. When complimentary credits run out, you sign the entitlement policy to keep using Workday AI agents.

Credits are fungible across Rate Card offers you are entitled to. The console’s total consumption breakdown includes agents and Workday Data Cloud as separate sources. API request counts are informational until you sign the entitlement policy; Workday says Flex Credits are not charged for them until then. Document storage does not consume Flex Credits. It has its own service limits.

Metering is in blocks, not one credit per click. Workday’s example: a skill blocked at 10 units for 5 credits. The first execution buys the block. The next nine executions in that block cost nothing more. The 11th buys another block. Your Rate Card columns are applicable environment, consumption meter, definition, units per block, and credit rate per block.

Usage for the previous day starts updating at 2:00 PM UTC and can take up to 3 hours. Embedded entitlement is used before purchased credits, and credits that expire sooner are used first. Workday does not turn the agent off from this dashboard when you pass the entitlement. You deactivate the agent yourself. Default alerts fire at 80, 90, and 100 percent. Custom alerts can be weekly, monthly, or annual per agent.

For most offers, non-Production usage does not reduce the organization’s Flex Credit balance. Non-Production dashboards still show an informational balance, and a Sandbox dashboard rolls up all non-Production tenants. Refreshes do not clear that dashboard. The Production dashboard does show non-Production consumption for specific agents: Adoption in Preview, and Deployment in Implementation, Preview, and Sandbox. Planning Agent’s own page adds that agent use in a sandbox Adaptive Planning instance does not consume Flex Credits.

The Flex Credit Estimator forecasts from generally available agents and capabilities, subtracts platform entitlement, and can export to Excel or PDF. Estimates are informational. Inputs are not customer content. If your signed policy has no platform components, those lines do not appear on the console.

## What not to assume

-   Buying credits does not license Data Cloud. The SKU, the public-cloud tenant, and a partner contract are separate requirements on the Data Cloud setup page.
-   Pointing Decision Intelligence at Snowflake is a DI connection, documented on the Decision Intelligence page. It is not the Data Cloud Live Data Query setup, unless you also complete that setup.
-   An external model reading Live Data Query as an ISU sees whatever that ISU’s domains allow, not “the same as the employee who asked.” Use user-as-self when the agent must match a person’s Workday security.
-   Marketing access to “the latest AI innovations without a new procurement cycle” still stops at offers on your Rate Card and at agents your products include. Registration pages still say you can register only agents in products you have.
-   Complimentary credits are sized by company size on the marketing page. Workday does not publish the table of sizes there. Read your agreement.

## Frequently asked questions

### Do agent chats query Data Cloud automatically?

Nothing on the agent reference or the Data Cloud setup page says that. Agents use their skills and tools. Data Cloud is a separate connection for external platforms and Prism.

### Will a Sandbox pilot of every agent drain Production credits?

For most offers, no. Confirm the agent is not in the exception list Workday prints: Adoption in Preview and Deployment in those non-Production tenants, which the Production dashboard does display. Still watch the informational non-Production balance so a test is not mistaken for a Production burn.

### Where do we see Data Cloud versus agent spend?

Platform Consumption Console, total credit consumption, then the agents grid and the Data Cloud source. Detailed agent activity is in Agent System of Record. The console updates daily, not per click.

## Sources checked

Data Cloud setup and overview, Live Data Query, Platform Consumption Console, and the Flex Credits marketing page, fetched 2026-11-16.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### From Workday Illuminate to AI agents](https://kiweely.com/blog/workday-illuminate-to-ai-agents-naming)
-   [November 16 ### When not to build a Workday custom agent](https://kiweely.com/blog/when-not-to-build-workday-custom-agent)
-   [November 16 ### Sana custom agents vs the desktop Workday chat](https://kiweely.com/blog/sana-custom-agent-vs-desktop-workday-copilot)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [CRAFT prompts for the Workday Deployment Agent](https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns)
-   [How to use Deployment Agent through an implementation](https://kiweely.com/guides/workday-deployment-agent-implementation-phases)
-   [A Workday admin’s first week with Deployment Agent](https://kiweely.com/guides/workday-admin-first-week-deployment-agent)
-   [Workday Core Reporting Agent: when conversational reporting is enough](https://kiweely.com/guides/workday-core-reporting-agent)
-   [Workday Adoption Agent: Release Impact Analysis for Preview admins](https://kiweely.com/guides/workday-adoption-agent-release-impact)
-   [Workday-built AI agents catalog: what each agent is for](https://kiweely.com/guides/workday-built-ai-agents-catalog)
-   [The 2026 Workday AI map: Sana, ASOR, Workday-built, custom, partner, and external agents](https://kiweely.com/guides/workday-ai-ecosystem-map-2026)
-   [Why Generic IDE Agents Still Need Workday Developer Agent for Extend](https://kiweely.com/guides/why-generic-ide-agents-need-workday-developer-agent)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
