On October 6, the World Bank. On October 20, ECLAC and Chile’s National Center for AI. Two distinct assessments reached the exact same conclusion: the bottleneck lies not in the tool itself, but in the organizational capacity to absorb it. An academic concept originating in 1990 brings order to what today’s numbers describe.
The challenge is not merely implementing AI agents. It is knowing precisely which ones are running, who bears accountability for them, how their outputs are validated, and how swiftly they can be shut down when something fails.
Applying agentic AI to payments requires the exact same level of rigor as any system handling third-party funds—extended to a type of actor that did not exist two years ago: one that decides and executes, rather than merely recommends.

An agentic task is not a single model call. It is an end-to-end sequence that can encompass retries, inter-agent orchestration, database queries, and human-in-the-loop review. The guidelines established by the FinOps Foundation help break down these distinct operational layers:
The guide published on October 6 by Tammy Burnitt of the FinOps Foundation adds a nuance that any chief financial officer will immediately recognize: supporting tooling is purchased in silos across different teams, and observability is a frequent source of budget overruns because generative AI applications produce massive volumes of telemetry data. Compounding this challenge, some cloud vendors have begun billing separately for components such as persistent memory, agent sessions, and skill registry management—as reported by Revista Cloud Computing in September regarding Google Cloud infrastructure updates.
The State of FinOps 2026 report—surveying 1,192 practitioners managing over $83 billion in annual cloud spend—reveals that 98% now track AI expenditure, up from just 31% two years ago. Tracking has arrived. Control, however, has not.
Splunk's State of Observability 2026, which surveyed 2,050 IT operations and engineering leaders across ten countries, found that 55% lack effective control over AI costs, 56% struggle to accurately evaluate the quality of their AI workloads, and 54% have yet to align system monitoring with concrete business outcomes. While conducted by an observability vendor, these findings mirror regional operational realities. A joint study by Sensedia, Squadra, and MIT Sloan Review Brazil—presented at APIX 2026 on August 4—indicates that 74% of Latin American enterprises incur unexpected cost overruns driven by fragmented, uncoordinated AI implementations.
The formula is simple. The difficulty lies in having the underlying data to apply it:
Define what constitutes a completed task before measuring its cost: An output only counts if it is accepted by the business process, the end customer, or the responsible manager. Without this explicit validation threshold, the denominator remains a subjective opinion.
Account for the harness, not just the model: The FinOps Foundation warns that in production agentic architectures, the supporting infrastructure surrounding the model can account for 40% to 60% of total operational expenditure—none of which appears on the primary vendor's API invoice.
Route by task complexity: Reserve high-reasoning models exclusively for tasks whose delivered value justifies the elevated cost, resolving simpler routines through lower-cost alternatives. This represents Gartner's primary architectural recommendation.
Embed economic guardrails directly into the software architecture: Enforce maximum execution steps, token limits, and time caps per run, alongside session-level budgets and deterministic escalation triggers to human operators. The FinOps Foundation recommends monitoring each application's performance baseline for 30 to 60 days, establishing operating budgets at 110% to 120% of that baseline, and configuring real-time telemetry alerts at 80% and 100% thresholds.
Attribute and govern AI procurement centrally: Tag every API request by team, business function, and task type at the point of origin—as proposed by Donald Farmer—and channel all experimental AI spending through a centralized review board to eliminate redundant software subscriptions, as advised by the FinOps Foundation.
There is a crucial sixth implication that executive committees often uncover too late: when costs are evaluated on a per-accepted-task basis, the decision ceases to be a technical debate and becomes an operational work design question: For any given workload, is the task best executed by an autonomous agent, a human professional, or a hybrid team? The answer shifts task by task, and can only be determined through hard data.
Puedes configurar tu navegador para aceptar o rechazar cookies en cualquier momento. Si decides bloquear las cookies de Google Analytics, la recopilación de datos de navegación se verá limitada. Más información.