
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Bartenders engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Bartenders involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Bartenders performs 20 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+8 more via performs
Bartenders is typically employed by 126 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+114 more via typicallyEmploys
Bartenders is employed across 79 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+67 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Bartenders uses 49 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
+37 more via usesTool
Bartenders relies on 19 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+7 more via uses
The software Bartenders reaches for already exposes 8 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
+64 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.