How pest control workers are reshaped as AGI capability advances.

Only about 15% of Pest Control Workers is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: The role is fundamentally physical, driven by core Work Activities like 'Operating Vehicles, Mechanized Devices, or Equipment' (4.20) and 'Performing General Physical Activities' (3.75), alongside environments like 'Outdoors, Exposed to All Weather Conditions' (4.67) and 'Exposed to Contaminants' (4.54). While 14 of the 30 listed tools are software (UNSPSC segment 43) used for reporting and scheduling, these function as administrative wrappers around hands-on extermination work that cannot be digitized.
grounded in the economy graph · digital scalar 0.15 · physical
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Pest Control Workers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Pest Control Workers 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.
Pest Control Workers performs 13 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+1 more via performs
Pest Control Workers is typically employed by 51 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+39 more via typicallyEmploys
Pest Control Workers is employed across 30 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+18 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Pest Control Workers uses 38 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.
+26 more via usesTool
Pest Control Workers relies on 16 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.
+4 more via uses
The software Pest Control Workers reaches for already exposes 12 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.
+5 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.