Home / Signal / #002
Signal #002 · 14 September 2026
One of the two zero layers isn’t zero anymore
Signal is a weekly note on what actually changed in the commercial software stack (pricing models, agent interfaces, ownership) tagged to the layer of the Agentic Commercial Model it belongs to. A link to the document behind every claim, and no filler to hit a quota: this issue is three items, because three is what the documentation actually supports.
Checked against the 21 August 2026
Agent Access Registry baseline: all 34 vendors' developer documentation, changelogs, GitHub repos and official press pages re-verified against that dated row.
01Layers 3 + 5 · Pricing and Sales Compensation
One zero layer shipped a real MCP server. The other answered with a marketing page.
Zilliant now publishes a live MCP developer docs page: OAuth authentication with Salesforce as the identity provider, tenant isolated access, and logged, auditable interactions, delivering roughly seven months late on the Q1 2026 promise its press release made (and that we flagged as undocumented in issue #001). The access is explicitly read only: querying pricing data, not writing to it. Across the aisle in Sales Compensation, CaptivateIQ added an “AI Agents” page advertising a CaptivateIQ MCP Server for “secure, governed access to your live compensation and planning data,” labelled “Coming Soon” with no authentication method, scopes or tool schema published anywhere, including its existing developer docs.
Why it matters: Pricing & Packaging Strategy is no longer the category where literally no vendor has shipped an interface: that distinction now belongs to Sales Compensation alone. But don’t overread what Zilliant shipped. Read only means an agent can query a price, not change one, so if your operating model assumes an agent will actually adjust pricing or approve an exception, that build is still entirely on you. Watch whether CaptivateIQ follows Zilliant’s exact script (announce, go quiet, ship read only docs months later) or moves faster now that the playbook is public.
Source: Zilliant MCP docs · CaptivateIQ AI Agents page
02Layers 6 + 8 · Billing and Usage Metering
Salesforce closes on m3ter. Chargebee’s docs haven’t caught up to its own marketing page.
The Salesforce acquisition of m3ter we flagged as pending in issue #001 has closed: Salesforce’s own announcement page now carries an editor’s note stating the deal completed 1 July 2026. m3ter’s developer docs show no trace of it yet, still the same plain OAuth client credentials REST API, no Salesforce branding, no MCP server added. Separately, Chargebee’s own MCP marketing page now states write actions are “launching shortly, so agents will move from answering to doing: issuing credits, triggering dunning, and adjusting subscriptions,” a claim that exists nowhere in Chargebee’s actual technical documentation, where the one MCP server that writes still targets test and sandbox sites only.
Why it matters: Two shapes of the same story. The m3ter deal is the second acquisition to hit this layer in a matter of weeks (after PROS/Conga in issue #001), and it keeps building the case that standalone consumption billing infrastructure is being absorbed into platforms that need it for their own agent products. Chargebee’s teaser is the smaller, more familiar pattern this site exists to catch: marketing copy running ahead of documentation. “Launching shortly” is not a date, a scope, or an audit trail, and until it’s in the docs it doesn’t change how you should plan around this vendor.
Source: Salesforce (m3ter acquisition) · Chargebee MCP page
03Layer 2 · GTM and Sales Engagement
Correction: Clay’s MCP server isn’t “remote.” It’s a CLI you run locally, plus an OAuth bridge.
Our August entry for Clay carried a confidence flag: the finding rested on pages found via search after a direct fetch failed, and we described it as a “remote MCP server.” A direct fetch this week resolves the flag and corrects the description. Clay’s own docs describe a CLI launched local server: an MCP host spawns clay mcp, which runs over stdio and authenticates with the same session as the rest of the CLI (clay login, or a CLAY_API_KEY), not a hosted endpoint you put in a host config. A separate first party integration, documented on Clay University, is an OAuth gated workspace bridge connecting Clay to named platforms (Claude, ChatGPT, Copilot, Glean) rather than an open remote server.
Why it matters: Same correction instinct as issue #001’s Pipedrive entry, run in the other direction: not “Clay does more than we said,” but “Clay’s interface is a different shape than we said.” The registry’s “Official” status still holds, this is a genuine, documented, first party interface, but it changes what you’d design against. A plan that assumes you can point an arbitrary hosted agent at a Clay endpoint over HTTP needs a different design: a local CLI process, or a workspace level connection to a named platform, not a server URL callable from anywhere.
Source: Clay MCP docs · Clay University: MCP settings