Salesforce, HubSpot meter agent API calls at 60x to 1,200x human integration rates
Salesforce and HubSpot are charging separately for AI agent access to their platforms. Both companies announced new metering models in recent months that price agent API calls well above their existing integration rates.
Salesforce is metering third-party agent usage through Flex Credits. Every successful call an agent makes through MCP or the API becomes a Flex Credit charge. Existing customers migrate to the new billing at renewal. Salesforce already sells extra API capacity for integration traffic at around $83 per million calls. The proposed agent meter lands between $5,000 and $100,000 per million, a 60x to 1,200x markup on the same endpoint.
HubSpot is pricing its own Breeze agents separately: per-resolution pricing, custom agent metering since July, and Breeze credit usage. The MCP server remains free for agents customers bring themselves.
For context: Salesforce reported FY2026 revenue of $41.5 billion globally, with $2.14 billion from ANZ in 2026. HubSpot posted $911.7 million in Q2 2026 revenue and is tracking toward roughly $3.7 billion for the full year. Both sit in the core sales tech stack, so agent pricing flows directly into CAC, renewal negotiations, and platform stickiness for sales and RevOps teams.
What sales teams are doing
When vendors charge for agent API access, the immediate response is routing around the meter. Sync records to your own database, read from there, write back to the vendor only when something changes. Agents read far more than they write, so most of the calls a vendor would meter are lookups against data you already have a copy of.
That used to be hard. Now it is a weekend project.
New agents get built against other systems from day one, or against your own copy of the data. Less data flows through the platform. Less of your work happens there. The moat for a system of record was that everything lived there and everything touched it. Price the touching, and less of it touches.
What would work
The meter is not the problem. Agent traffic is real load. The problem is the additive version: keep the seat, keep the storage premium, keep the API tiers, and add a per-call meter on top.
Vendors who get this right will publish the rate and cap it, let a registered agent replace a seat instead of stacking on top of one, or price the outcome rather than the call. Firebase has charged $0.06 per 100,000 document reads for years and nobody calls it a tax. The question is the multiple.
Atlassian is doing a version of this with Rovo: $0.10 per basic action, same rate as an Agentforce action, but every paid plan includes an allowance (25 credits per user per month on Standard, 70 on Premium, 150 on Enterprise, pooled org-wide). Atlassian published the rate, published the date (overage billing starts December 3, 2026), and gave admins a switch to cap usage.
The vendors who leave it vague and uncapped will get agents reading from a copy and writing back as little as possible. Less usage, less stickiness, smaller footprint at renewal.