TL;DR: TrueFoundry argues that agent-economy theory only becomes operational when institutions like identity, discovery, accounting, and stability are mapped to real enterprise controls, and that governed gateways can instrument some of them while leaving major gaps, according to TruFoundry. The hard boundary is that firm-scale observability is not economy-scale governance, especially where reputation, settlement, and cross-domain identity do not exist.
NHIMG editorial — based on content published by TruFoundry: Agent Economics, No. 2: Mapping Firm-Scale AI Controls to Agent-Economy Institutions
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should security teams govern AI gateways in production environments?
A: Security teams should govern AI gateways like shared control planes, not convenience proxies.
Q: Why do API gateways fall short for autonomous agent governance?
A: API gateways fall short because they treat each request as independent and do not model conversation flow, delegation, or the business meaning of a tool call.
Q: What is the difference between gateway accounting and real agent identity governance?
A: Gateway accounting records what happened, while identity governance decides who or what should have been able to do it in the first place.
Practitioner guidance
- Define the mediated boundary first Document which agent, LLM, and MCP flows are actually governed by the gateway and which flows bypass it through direct web access, queues, in-process calls, or non-MCP APIs.
- Separate identity from telemetry Use gateway attribution for model cost, token use, and tool calls, but do not treat that data as a substitute for lifecycle governance, trust decisions, or access certification.
- Map the trust gaps explicitly List where discovery, reputation, settlement, insurance, and mission design have no enterprise analogue today, then record those gaps as architectural dependencies rather than future assumptions.
What's in the full article
TruFoundry's full article covers the operational detail this post intentionally leaves for the source:
- The institution-by-institution mapping table that compares each agent-economy concept with a firm-scale control analogue.
- The gateway documentation references behind identity resolution, usage accounting, budgets, rate limits, and virtual-model fallback behaviour.
- The boundary analysis for traffic that bypasses the gateway, including direct web, queue, in-process, and agent-to-agent paths.
- The explicit gaps in reputation, settlement, insurance, and mission design that this post summarises rather than fully expands.
👉 Read TruFoundry's analysis of agent-economy controls and gateway governance →
Agent economics and gateway governance: what controls actually scale?
Explore further
Gateway governance is not the same as agent governance. The article is right to separate mediated traffic from the wider agent ecosystem, because a gateway only controls the paths it can see. That means identity, accounting, and policy enforcement are real only inside the mediated boundary, while other channels can remain invisible. The practitioner conclusion is simple: do not treat gateway observability as full agent governance.
A few things that frame the scale:
- 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to the AI Agents: The New Attack Surface report.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation.
A question worth separating out:
Q: What should teams do when agent traffic bypasses the AI gateway?
A: Treat bypass paths as separate control planes, not exceptions to ignore. Apply identity, policy, logging, and review controls to direct web access, non-MCP APIs, and in-process calls so that important activity does not disappear outside the governed boundary.
👉 Read our full editorial: Agent economics needs gateway controls, not just model access