--- title: "When one vendor prices the work, governs it, and grades it" description: "When one vendor prices, gates and grades your AI agents, you lose leverage. Six controls to set before production, and where the referee belongs." canonical: "https://www.kondevs.com/content-hub/vendor-controls-meter-gate-referee-ai-agents/" language: "en" type: "article" author: "https://www.kondevs.com/authors/stoyan-kondev/" published: "2026-11-05T16:37:50.737Z" modified: "2026-11-05T16:40:25.709Z" image: "https://www.kondevs.com/assets/images/content/vendor-controls-meter-gate-referee-ai-agents/og.jpeg" tags: ["AI Agent", "IBM webMethods", "Camunda", "Business Process Management (BPM)"] --- > For the complete index of this site, see [llms.txt](https://www.kondevs.com/llms.txt); the whole site in one file: [llms-full.txt](https://www.kondevs.com/llms-full.txt). # When one vendor prices the work, governs it, and grades it EAI & Integration 5 November 2026 3 min read By [Stoyan Kondev](https://www.kondevs.com/authors/stoyan-kondev/) ## Key takeaways - Application vendors increasingly control the meter (what is billable), the gate (what an agent may reach) and the referee (the tooling that judges value), as Forrester argued on 3 November 2026. - Credits consumed and agents activated are activity, not business value; measure work removed, cost avoided and quality improved yourself. - Consumption pricing is becoming the renewal baseline: in Growth Unhinged's 2025 survey of more than 240 software and AI companies, hybrid pricing rose from 27% to 41% in a year. - Set six controls before production: know who acted, keep the evidence, verify the value, know the real price, choose the route and keep the off switch. - In a mixed estate no vendor console sees an agent's whole job, so the referee belongs in your own integration layer: your gateway, your event records, your off switch. Salesforce lists some Agentforce actions at $0.10. SAP assigns 0.02 AI units to certain agent actions. Workday prices a completed task at five times the rate of an information retrieval. Three models, one direction: the vendor defines the billable unit. That would be a pricing question only, if the same vendor did not also decide which routes an agent may take and supply the dashboard that judges whether the spend was worth it. ## The meter, the gate and the referee Forrester's Faram Medhora put it in one line on 3 November 2026: [application vendors now control the meter, the gate and the referee](https://www.forrester.com/blogs/your-application-vendors-control-the-meter-the-gate-and-the-referee/). The meter is what counts as billable. The gate is what an agent may reach. The referee is the governance and monitoring tooling that tells you whether it worked. Integration architects feel the gate first. Forrester points to SAP's April 2026 API policy, which restricts third-party agents that plan or execute sequences of SAP API calls outside approved paths. An external finance agent that needs an SAP transaction may have to go through a Joule-mediated route. SAP has a legitimate interest in protecting its application. But when the approved route is also metered, an API policy becomes an architecture constraint and a commercial lever at once. ## Activity is not value Credits consumed and agents activated are activity. Work removed, cost avoided and quality improved are outcomes. Forrester made the same point in its [review of H1 2026 enterprise software earnings](https://www.forrester.com/blogs/2026-h1-enterprise-software-earnings-reveal-a-new-vendor-power-play/): adoption and activity metrics say little about effort removed or cost avoided. This matters because consumption pricing is becoming the renewal baseline. Growth Unhinged's 2025 State of B2B Monetization survey of more than 240 software and AI companies, [summarized by Orb](https://www.withorb.com/blog/consumption-based-pricing-statistics), found hybrid pricing up from 27% to 41% in a year and flat-fee subscriptions down from 29% to 22%. If you cannot rebuild the vendor's bill from your own event records, you negotiate the renewal on the vendor's numbers. Lock-in moves the same way. "We can export our data" is not an exit plan when the switching cost sits in orchestration logic, configurations, permissions and agent behavior. ## Six controls before production Forrester's six lenses translate directly into integration decisions: - **Know who acted:** every production agent has its own identity, an owner and bounded authority. - **Keep the evidence:** what the agent saw, which rules it applied, which tools it called and what it changed, stored outside the vendor's console. - **Verify the value:** set consumption against completed transactions, exceptions, human corrections and financial impact. - **Know the real price:** count retrievals, API calls, retries, approvals and reversals at production volume, not pilot volume. - **Choose the route:** write the supported routes, mandatory gateways, charges and telemetry rights into the contract. - **Keep the off switch:** test that you can revoke authority, stop execution, keep the evidence and find unfinished work. All six are easiest to set while the agent is still optional. ## Our view: the referee belongs in your integration layer A vendor's governance tooling sees the vendor's suite. In the mixed estates we work in, SAP next to webMethods or Camunda, an agent's work crosses several systems, and no single vendor console sees all of it. The one place that does is the integration layer every call already passes through. That is where we put the referee: - **Your own gateway:** route agent calls to core systems through it, so identity, policy and limits are yours, whichever vendor's agent is calling. - **Your own records:** log every call as an event with agent, owner, route and outcome, so you can rebuild the vendor's bill and check it. - **Your own off switch:** keep it at the gateway, where one decision stops agents from every vendor. It is the same discipline as [API governance with versioning, deprecation and policy as code](https://www.kondevs.com/content-hub/api-governance-versioning-deprecation-policy-as-code-enterprise/), applied to a new kind of caller. Adopt agents for the value they deliver, but make sure the terms, the telemetry and the off switch belong to you before the agents become load-bearing. Designing that layer is the core of our [Enterprise Integration & BPM](https://www.kondevs.com/services/eai-integration/) work. ## Frequently asked questions ### What do the meter, the gate and the referee mean? They are Forrester's terms for three things application vendors now control in AI agent deployments: the meter decides what is billable, the gate decides which systems and routes an agent may use, and the referee is the governance and monitoring tooling that judges whether the work was worth it. ### How do Salesforce, SAP and Workday price AI agent work? Differently, but always per activity. Salesforce lists some Agentforce actions at $0.10, SAP assigns 0.02 AI units to certain agent actions, and Workday prices a completed task at five times the rate of an information retrieval. Forrester cited these examples in November 2026. ### Why are activity metrics not enough? Credits consumed and agents activated show that something ran, not that it helped. Compare consumption with completed transactions, exceptions, human corrections and financial impact, and keep event-level records so you can rebuild the vendor's bill yourself. ### Does vendor governance tooling cover a mixed estate? Usually only the vendor's own suite. When an agent's work crosses SAP, webMethods, Camunda or other systems, the place that sees every call is the integration layer. That is where we put identity, policy, event records and the off switch. ### What should be in place before an AI agent goes into production? Six controls: know who acted, keep the evidence, verify the value, know the real price, choose the route in the contract, and keep an off switch you have tested. They are easiest to set while the agent is still optional. ## Sources 1. [Your Application Vendors Control The Meter, The Gate, And The Referee, Forrester](https://www.forrester.com/blogs/your-application-vendors-control-the-meter-the-gate-and-the-referee/) 2. [2026 H1 Enterprise Software Earnings Reveal A New Vendor Power Play, Forrester](https://www.forrester.com/blogs/2026-h1-enterprise-software-earnings-reveal-a-new-vendor-power-play/) 3. [Consumption-based pricing statistics, Orb](https://www.withorb.com/blog/consumption-based-pricing-statistics) ## Related concepts & services Key terms: [AI Agent](https://www.kondevs.com/glossary/#ai-agent), [IBM webMethods](https://www.kondevs.com/glossary/#webmethods), [Camunda](https://www.kondevs.com/glossary/#camunda-bpm), [Business Process Management (BPM)](https://www.kondevs.com/glossary/#business-process-management) Explore our service: [Enterprise Integration & BPM](https://www.kondevs.com/services/eai-integration/)