Why Future Trillion-User Products Won’t Need a UI
With machine traffic now surpassing human traffic, the author argues that traditional front‑end UI is becoming obsolete for the coming era of AI agents, urging developers to treat APIs as the true UI and focus on agent‑friendly infrastructure such as sandbox compute, micro‑payments, service discovery, and composable workflows.
2025 web‑traffic data shows machine‑generated traffic exceeding 50%, making human users a minority.
UI loses relevance for AI agents
Developers have optimized page dwell time, button colors, and animations to protect core functionality behind complex web interfaces. Agents, however, will issue direct commands such as “clean this database” via tools like Claude Code or OpenClaw, bypassing any UI.
Y Combinator partner Jared Friedman notes that many developer tools still require manual account registration and key retrieval, which agents cannot perform. If a system cannot be auto‑registered and invoked through a pure API, it is effectively dead for agents, and the traditional product‑led growth funnel collapses in favor of “API‑doc decides survival.”
Four emerging infrastructure tracks for the trillion‑agent era
Agent sandbox compute layer : Servers will host stateless sandbox environments for agents, e.g., the E2B platform ( https://github.com/e2b-dev/e2b).
Agent identity and wallet : Agents will need to scrape paid resources; micro‑transactions at Stripe‑level become essential for machine‑to‑machine commerce.
Machine‑to‑machine service discovery : Agents must negotiate handshake protocols to discover each other’s capabilities.
Trust and over‑privilege governance : Mechanisms are required to prevent agents from hallucinating or over‑reaching when operating core CRM systems.
Agent‑First era iron rules
Rule 1: API is the final UI. If core functionality is not exposed via API, CLI, or MCP (Model Context Protocol), it effectively does not exist.
Rule 2: Documentation is for machines. Provide a --help output and a highly structured API schema so large language models can read it instantly with zero trial‑and‑error.
Rule 3: Embrace extreme composability. Build clean, stateless, machine‑readable workflows that can be stitched together on demand.
Question for developers
Ask whether a pure AI agent could connect to a core pipeline within five seconds without a web page.
Reference material
https://x.com/levie/status/2030714592238956960
https://www.imperva.com/resources/resource-library/reports/2025-bad-bot-report
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
TonyBai
Tony Bai's tech world (tonybai.com). Not satisfied with just "knowing how", we strive for mastery. Focused on Go language internals, high-quality engineering practices, and cloud‑native architecture, exploring cutting‑edge intersections of Go and AI. Gophers who pursue technology are welcome—follow me and evolve with Go.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
