Salesforce, HubSpot meter agent API access: comp and pricing implications for sales teams
## The pricing shift Salesforce and HubSpot are both metering agent API access, but differently. HubSpot is charging mainly for its own agents: Breeze credits, per-resolution pricing, custom agent metering since July. The MCP server for customer-brought agents stays free. Salesforce is going the opposite direction: every successful call a third-party agent makes through MCP or the API becomes a Flex Credit charge. Agents must be registered, and existing customers migrate to the new billing at renewal. The pattern extends beyond those two. Multiple B2B vendors are adding agent API charges to existing seat pricing. One example: Salesforce already sells extra API capacity for integration traffic at about $83 per million calls. The proposed agent meter lands between $5,000 and $100,000 per million. Same endpoint, same record, 60x to 1,200x markup based on whether a human's integration or an agent made the call. ## What this means for sales stack budgets For sales teams running agents, the immediate question is: how do we work around this? Sync the CRM data to an internal database, read from there, write back only when something changes. Agents read far more than they write. Most of the calls a vendor would meter are lookups. That sync work used to be hard. Now it is a weekend project. When we evaluate new tools, "how does this price agent access" is now a real question, and a bad answer is disqualifying. The risk for vendors is a usage death spiral. They meter agent access. Usage drops because teams route around the meter. New agents get built against other systems or internal data copies. Less data flows through the platform. Less work happens there. The moat for a system of record was that everything touched it. Price the touching, and less of it touches. ## The ANZ context Salesforce reported FY2026 revenue of $41.5 billion globally and A$2.14 billion from Australia, with 2,182 local employees. It has 29,000+ Agentforce deals and recently acquired Intercom's Fin customer-agent product. HubSpot is much smaller: Q1 2026 revenue was $881 million, 306,446 customers by Q2, and 8,882 employees. That size difference matters. Salesforce's agent billing changes hit large enterprise buyers harder. HubSpot's pricing shifts land more with growth and mid-market teams adopting first-party AI features. ## What actually works The meter is not the problem. Agent traffic is real load. The problem is additive pricing: keep the seat, keep the storage premium, keep the API tiers, add a per-call meter on top. Three bills for one piece of work. Vendors who get this right will publish the rate and cap it, let a registered agent replace a seat instead of stacking on top, or price the outcome rather than the call. The ones who leave it vague and uncapped will get teams reading from a copy and writing back as little as possible. Atlassian is doing a version of this: Rovo credit usage includes calls through the Teamwork Graph CLI and the MCP server, overage billing starts December 3, 2026, at $0.01 per credit. A basic action is 10 credits, so $0.10. Every paid plan includes an allowance: 25 credits per user per month on Standard, 70 on Premium, 150 on Enterprise, pooled org-wide. The allowance is thin, and extra usage is on by default unless an admin caps it. But Atlassian published the rate, published the date, and gave admins a switch. For sales leaders planning 2024-2026 budgets, the takeaway is: account for agent API costs as a separate line item, and pressure vendors for published rates and caps before renewal.