The Problem Workday Is Solving
General-purpose coding agents have made individual developers significantly faster. What they have not solved is context — specifically, the business rules, delegation hierarchies, and audit requirements that govern every action inside an enterprise system of record.
A developer can prompt an LLM to write a Workday integration in minutes. Whether that integration respects role-based access controls, triggers the correct approval workflow, or leaves a compliant audit trail is an entirely different question. Workday Build’s new capabilities are designed to answer that question before anything reaches production.
Developer Agent: Prompt-to-Production Without Leaving Your Toolchain
The most immediately practical of the three announcements is Developer Agent. Rather than requiring teams to adopt yet another proprietary IDE or low-code canvas, it integrates directly into the agentic development environments developers already use — Claude Code, Cline, Codex, Cursor, and Google Antigravity among them.
The workflow is straightforward. A developer types a plain-language request — for example, “Build an agent that alerts finance when a department is trending to go over budget this quarter” — and Developer Agent selects the appropriate Agent-Ready Tools, wires in the relevant data and services, and surfaces the documentation needed to complete the build. Work that previously required days of setup and API archaeology is compressed into minutes.
The AgentSkills Standard
Underlying this is an open standard called AgentSkills (Skills.md), which defines how custom agents are described and deployed on the Workday platform. The use of an open standard here is a deliberate architectural choice — it signals that Workday is building for interoperability rather than lock-in, and it gives the developer ecosystem a common language for packaging and sharing reusable agent capabilities.
The feedback from early adopters is telling. Jules Mayberry, the sole developer at Waste Connections, described Developer Agent as giving her
“a real starting point”
that handles technical scaffolding so she can focus on understanding what the business actually needs. That is precisely the value proposition: reduce the distance between a developer’s intent and a working, compliant agent.
Agent-Ready Tools: Controlled Access to HR and Finance Data
Once an agent is built, it needs a structured, safe path to act on Workday data. This is where Agent-Ready Tools enter the picture.
Traditional APIs were designed for system-to-system data integrations — predictable, synchronous, and operated by humans who understand the context. Autonomous agents are none of those things. They make decisions dynamically, can chain multiple actions in sequence, and have no inherent understanding of why a particular business rule exists.
Purpose-Built for Autonomous Agents
Agent-Ready Tools are a new class of enterprise connectors built specifically to address this mismatch. They expose precise business logic and context to agents in a form that reduces both hallucination and latency — two failure modes that are particularly costly when the subject matter is an employee’s benefits record or a department’s budget line.
Hundreds of these tools span the full breadth of Workday’s platform and connect through the Model Context Protocol (MCP), an open standard that is gaining traction as the lingua franca for agent-to-system communication. Critically, agents that use Agent-Ready Tools automatically inherit Workday’s existing security model, business process controls, and audit trail. There is no separate security layer to configure — compliance is structural, not optional.
For actions that extend beyond Workday’s native surface, developers can build custom agent actions from a library of thousands of pre-built Pipedream connectors and expose them through the same Agent-Ready Tools interface. The architecture is consistent regardless of where the action ultimately lands.
Agent Passport: Independent Verification Before Deployment
The third component addresses a question that every enterprise security team will ask before approving an autonomous agent for production: how do we know this thing is actually safe?
Agent Passport answers that question with standards-based attestation stamps. Each stamp records which security and compliance tests the agent has passed, who performed the verification, and which frameworks were applied. The standards referenced are not proprietary — they include OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS, the same frameworks that enterprise security teams already use to evaluate risk.
Cisco as the First Attestation Partner
Cisco is the launch partner for Agent Passport attestation, providing independent third-party verification rather than self-certification. This distinction matters considerably. An agent that carries a Cisco-verified stamp has been evaluated by an external party against recognized standards — a meaningful signal in procurement and compliance conversations.
Agent Passport also operates continuously, not just at the point of initial deployment. Every internal and third-party agent running in Workday can be monitored against these standards on an ongoing basis, which addresses the reality that agent behavior can drift as underlying models are updated or as the data environment changes.
Availability and Access
Developer Agent and Agent-Ready Tools are currently available to early access customers through Workday Extend Professional, with general availability projected for the second half of 2026. Agent Passport enters early access in the second half of 2026, with general availability expected before the end of the year.
The phased rollout is consistent with Workday’s historically cautious approach to releasing capabilities that touch regulated data. Early access programs allow enterprise customers to validate behavior in controlled environments before broad deployment.
Who This Is Actually For
The primary audience is enterprise development teams — internal developers, system integrators, and ISV partners — who are building automation on top of Workday’s HR and finance platform. The secondary audience is the security and compliance functions within those enterprises, who now have a structured framework for evaluating and governing agent deployments.
For organizations already invested in the Workday ecosystem, this stack removes the most significant friction points in agentic AI adoption: the gap between development speed and enterprise-grade safety. For organizations evaluating enterprise AI platforms more broadly, it sets a concrete benchmark for what responsible agentic architecture looks like in practice.
The Broader Signal
What Workday has announced is not simply a set of developer tools. It is a position on what enterprise-grade agentic AI requires: open standards for interoperability, structural security rather than bolt-on compliance, and independent third-party verification as a prerequisite for deployment.
The hard part of enterprise AI has never been making agents fast. It has been making them trustworthy enough to act on the systems that run a company. Workday’s agentic stack is a serious attempt to solve that problem — and in a domain where the margin for error is effectively zero, seriousness of purpose is the differentiator that matters most.
Comments (0) No comments yet
Want to join this discussion? Login or Register.
No comments yet. Be the first to share your thoughts!