A partner-built agent is an agent a certified Workday partner builds. Workday’s admin guide lists it beside four other types: Workday-built, custom agents you build in Workday Extend, external agents you build outside Workday, and Sana user agents you build in Sana. You manage partner-built agents in Agent Management Hub through the same phases as the others: register, configure skills and who can access them, activate, deactivate, and archive.
The public Workday AI Agents page, fetched 2026-11-16, describes three commercial buckets. Workday-built agents are developed and maintained by Workday and orchestrated by Sana. Partner-built agents are built by partners outside Workday, brought in over open standards, and orchestrated by Sana. Customer-built agents are built by your teams and orchestrated by Sana. That page points partner-built discovery at Marketplace.
Workday has not published a current Concept: Agent Marketplace topic on doc.workday.com. The path .../agents/agent-marketplace/agent-marketplace.html returned 404 on 2026-11-16. This guide does not invent catalog buttons, partner program tiers, or a purchase flow from a page that is not on the public admin guide. Buy, try, and contact steps belong to Marketplace itself and to your Workday account team.
What you can govern after a partner agent exists
ASOR is included in the core subscription. Production registration requires opt-in to the Universal Main Service Agreement (UMSA). Configuring an agent sets which skills are on and which security groups may use each delegate skill. Activating it makes it available to those people. Deactivating hides it from users and leaves it in the hub. Archiving removes it from Agent Registry and keeps history.
Delegate skills need an interaction security group. Example from Workday: Employee as Self for a skill an employee runs. Ambient skills do not, because they act without a person, on a schedule or another initiation. Being allowed to talk to the agent is not the same as being allowed to call the tool. The person must sit in a group on the skill and in a group on the API policy. View Security for Agent Skill is the report that shows those policies.
Hub analytics are uneven. Active Agents is for all agents. Total Agent Sessions, Total Agent Sessions Over Time, and Total Unique Users are documented only for Workday-built agents. Do not promise a partner-agent session dashboard from those reports.
Workday creates and stores the private key for client credentials. Your environment still has to support OAuth 2.0. After Configure Agent, Workday generates an Agent System User. Developers use that account when the agent calls Workday through Agent Gateway.
Agent Gateway, which is documented
Agent Gateway is the regional front door for third-party agents, including partner agents, into Workday. The concept page says it includes:
- All public REST operations
- Workday Graph API
- Workday Query Language (WQL)
- Workday RaaS
- Access to the Agent Definition Registry API
Every third-party agent that calls Workday APIs must send that traffic through Agent Gateway using Agent System User security. The agent must already be registered in ASOR, with authentication configured. Turning an agent on or off in Workday can take up to a minute to show up on gateway requests.
Calls must include:
- The regional host. Workday’s table is US
https://us.agent.workday.com, EUhttps://eu.agent.workday.com, UKhttps://uk.agent.workday.com, Canadahttps://ca.agent.workday.com, Australiahttps://au.agent.workday.com, Singaporehttps://sg.agent.workday.com, Indiahttps://in.agent.workday.com, and Japanhttps://jp.agent.workday.com. - HTTP header
wd-agent-tenant-aliasset to your tenant alias. Workday says the value must be unique. - For SOAP,
https://us.agent.workday.com/soap/{version}/{serviceName}with the host swapped for your region.
A sample Workday gives is GET https://us.agent.workday.com/api/common/v1/workers with that tenant-alias header. If the agent platform supports OAuth 2.0, Workday expects the authorization-code grant. The authenticate-to-gateway topic says you register and activate with the agent registration API, keep the client id, client secret, redirect URI for delegate agents, and x509 public key for ambient agents, then post to https://us.agent.workday.com/auth/oauth2/<tenant alias>/token using the authorization code. Substitute the regional host.
Changing Agent Gateway region resets agent analytics in Agent Management Hub. Workday recommends you do not change regions if you need that history.
Gateway also states that it rate-limits, authenticates every call through Workday security, and gives you one place to track API consumption for billing. It does not publish numeric rate limits on the concept page. Do not invent a calls-per-minute figure.
How to evaluate a partner agent without a public admin catalog
- Read the partner’s description on Marketplace, then write down the skills you expect to see in Agent Management Hub. If Marketplace and the hub disagree, the hub is what the tenant will run.
- Confirm the agent type is partner, not a Workday-built row you already own. The Workday-built reference table is a different list.
- Confirm UMSA before anyone promises a Production registration.
- Map Available To groups to the same populations who can call the underlying APIs.
- Point the agent at the regional gateway host that matches the data center, and put the tenant alias on every call.
- Ask the partner which execution mode they use. Delegate follows the human’s security. Ambient uses the agent account and does not need an interaction group.
- Check whether you need Workday-built usage reports. Those session reports will not describe the partner agent.
Sana is the experience layer on the marketing page: it interprets intent and routes work through ASOR. That does not mean every partner agent appears inside Sana on day one. Activation and security groups still decide who can run it.
Frequently asked questions
Can we install a partner agent the way we register Case Agent?
Case Agent is selected from Unregistered Workday Agent because Workday ships it. Partner agents are registered as partner agents, and external agents are defined through an API. Use the path your partner’s onboarding topic specifies, then confirm the row in Agent Registry. Do not look for the partner’s name on the Workday-built reference table.
Is Marketplace the system of record?
No. ASOR is the system of record for agents in the tenant. Marketplace, on Workday’s marketing page, is where customers discover partner-built agents. Discovery is not activation.
What if legal asks for an admin procedure for the storefront?
Say the public admin guide did not serve an Agent Marketplace concept page on 2026-11-16. Govern the agent with About Workday Agents and Agent Gateway. Treat storefront steps as unpublished until Workday puts them on doc.workday.com or your tenant’s own task guide.
Sources checked
About Workday Agents, Concept: Workday Agent Gateway, Authenticate Agents to Agent Gateway, and Workday AI Agents on workday.com, fetched 2026-11-16. The admin-guide Agent Marketplace URL returned 404 the same day.