---
id: "action-build-programmatic-interfaces"
type: "action-item"
source_timestamps: ["§ Information Systems", "§ Tools: Build agent tools."]
tags: ["procurement", "system-architecture"]
related: ["concept-programmatic-agent-interfaces"]
action: "Mandate API-first architecture for new tools and wrap legacy systems with programmatic interfaces."
outcome: "Agents can execute tasks directly and reliably without fragile screen-scraping or UI-clicking workarounds."
speakers: ["Harang Ju"]
sources: ["agentic"]
sourceVaultSlug: "hbr-seg-agentic"
originDay: 6
articleStem: "hbr-ext-17-workplace-set-up-for-agents"
sourceUrl: "https://hbr.org/2026/01/is-your-workplace-set-up-for-ai-agents"
sourceTitle: "Is Your Workplace Set Up for AI Agents?"
---
# Require API-First Architecture

When evaluating new vendor tools, make API-first architecture a strict requirement. For legacy systems, build or implement wrappers (using protocols like [[entity-mcp|MCP]]) that expose capabilities through direct programmatic channels, letting agents authenticate and act without clicking through a UI. Start read-only, then add write capability behind approval gates.

**Action:** Mandate API-first architecture for new tools and wrap legacy systems with programmatic interfaces.
**Outcome:** Agents can execute tasks directly and reliably without fragile screen-scraping or UI-clicking workarounds.

This is the tools pillar of [[framework-agent-first-transition]]; it realizes [[concept-programmatic-agent-interfaces]] and answers [[claim-screen-clicking-is-flawed]]. Requires [[prereq-api-vs-gui|understanding APIs vs. GUIs]]; see the [[question-legacy-vendor-adaptation|open question on legacy-vendor adaptation]].