Home / Signal / #001

Signal #001 · 21 August 2026

What we found when we checked all thirty-four

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. Seven items, no filler, and a link to the document behind every claim.

This first issue is not a week of news. It is the output of a full documentation audit of all 34 vendors on this site, completed 21 August 2026 and published as the Agent-Access Registry. From next week, Signal covers what moved.
01Layer 9 · Commercial Systems

CRM went from zero documented agent interfaces to two — and our own review was the thing that was wrong

HubSpot publishes a remote MCP server with scope-gated, admin-authorised read and write access to CRM objects and engagements, distinct from the in-product Breeze copilot. Pipedrive publishes a native MCP server with per-client setup guides, governed by the same authentication and permission settings that bound a human user.

Why it matters: Our August review described Pipedrive as a “bring your own agent” CRM with no native agent layer. That was wrong, and it was wrong because we assessed the marketing surface instead of the developer documentation. Both entries are now corrected and dated. The lesson is not about Pipedrive — it is that a claim in this market goes stale within a quarter, which is why the registry carries dates and why this letter exists.

Source: HubSpot MCP docs · Pipedrive MCP

02Layer 2 · Go-to-Market

Outreach shipped an MCP server this month — and deliberately left out the edit verb

Outreach now publishes a first-party MCP server at api.outreach.io/mcp over OAuth 2.1, released in August 2026 on the Amplify add-on. It exposes read, create and delete tools, governed by the user’s existing profile permissions. Update is not among them.

Why it matters: The omission is the signal. A vendor that lets an agent create and delete records but not quietly amend them has thought about blast radius: a wrong create is visible, a wrong edit is not. Expect the permission model, rather than the tool count, to become the thing worth comparing.

Source: Outreach MCP overview

03Layer 3 · Pricing and Packaging

Zilliant announced an “industry-first” MCP server. There is nothing in the docs.

Zilliant issued a press release announcing an MCP server slated for Q1 2026. No MCP page appears anywhere in its public developer documentation or Customer API reference — no authentication method, no scopes, no tool schema.

Why it matters: This is the pattern this site exists to catch, and it deserves naming plainly rather than burying in a rating. An agentic capability that lives in the newsroom and not the docs cannot be scoped, permissioned or budgeted for. When a vendor tells you they have an MCP server, the follow-up question is the URL of the page that documents it.

Source: Zilliant press release

04Layers 3 + 5 · Pricing and Compensation

The two layers that have to change first are the two nobody is building for

Across seven pricing-strategy and sales-compensation vendors, not one publishes an agent interface. Zero. Meanwhile QuotaPath, CaptivateIQ and Salesforce Spiff all document REST APIs with real write endpoints — commissions, worksheets, plan objects.

Why it matters: So an agent can recalculate a commission or restructure a plan. It simply cannot buy the interface to do it. Every other category on the registry has at least one vendor who has done that work for you; in pricing and compensation you build and maintain it yourself, or you keep a human in the loop indefinitely. If your operating model assumes agents take part of the commercial motion, that integration cost belongs in the business case, not in a footnote.

Source: Agent-Access Registry

05Layer 4 · Sales Enablement

“We have an MCP server” is becoming a marketing line. Ask which verbs.

Gong’s MCP server is real and first-party, but its documentation describes query and read access only — the scoped writes, such as call and CRM data upload, sit on the separate REST API. Highspot’s MCP server exists as a product page listing write-sounding capabilities with no published authentication method, scopes, permission model or tool schema. Clari’s MCP server, documented through the Salesloft help centre, comes with a newsroom claim of write-back that no published scope detail confirms; rollout is phased through late summer.

Why it matters: Three vendors, three different distances between the claim and the documentation. We downgraded our own Gong entry for overstating it — we had called it “genuine bidirectional agent connectivity” on the strength of a press release. Read access is not agency. If the docs describe only reads, plan for reads.

Source: Gong MCP · Highspot MCP · Clari developer docs

06Layers 6 + 8 · Metering and Revenue Architecture

In billing, the sandbox boundary is the entire story

Chargebee publishes three first-party MCP servers — Knowledge Base, Data Lookup and Onboarding — but the one that writes targets test and sandbox sites, not production billing. Metronome ships an MCP server inside its official Node SDK whose writes include contract creation and usage ingestion.

Why it matters: Same nominal capability, completely different risk surface. Agent-assisted configuration of a billing system is a productivity feature. An agent ingesting usage events into production is a revenue-integrity decision, and it needs an approval path and an audit trail before it needs a demo. Anyone evaluating this layer should ask which environment the write lands in before asking anything else.

Source: Chargebee MCP · Metronome SDK

07Layer 3 · Market structure

Consolidation is hitting the two weakest layers first

PROS has divested its B2B CPQ and pricing line to Conga and now positions itself around airline retailing. m3ter is under a definitive agreement to be acquired by Salesforce, with consumption billing for Agentforce given as the stated rationale.

Why it matters: Both moves sit in the layers with the thinnest agent story, and they point the same way: the independent pricing and metering vendors are being absorbed into platforms that need consumption billing for their own agent products. Good for the platforms. It narrows the field for anyone who wanted to buy this layer independently, and it is a reason to ask hard questions about roadmap continuity in any pricing-system evaluation this year.

Source: Agent-Access Registry

Registry moves

Thirty-four rows established, each with an evidence URL and a verification date. Eighteen vendors publish an official MCP server — more than double what our August review recorded. Eight category write-ups were corrected as a result: Pipedrive, ActiveCampaign, Chargebee, ClickFunnels, Outreach, Clari and Zilliant all claimed an absence that was not there, and Gong was overstated in the other direction.

Put bluntly, our own first pass had an error rate above fifty per cent on the vendors it had not properly checked. That is the honest reason the registry is dated and this letter is weekly. A one-off review of this market is out of date before it is published.

Signal lands weekly. The registry updates with it.

Seven items, layer-tagged, evidence-linked. If something here is wrong or out of date, tell us and we will re-check and re-date the row.

Open the registry →