ESC
↑↓ navigate↵ open

Home / Signal / #007

Signal #007 · 29 October 2026

Sierra and Meta's protocol spec was due this month. It still isn't one. DealHub's October deadline missed it too.

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 four items, because four is what the documentation actually supports.

Checked against the 5 October 2026 Agent Access Registry baseline: all 43 vendors' developer documentation, changelogs, GitHub repos and official press pages re-verified against that dated row. Four rows re-date below, to 29 October 2026; none change grade.

In this issue

  1. Sierra and Meta's Personal Agent Protocol promised a spec ‘later this month.’ It’s still a draft with an unimplemented reference repo.
  2. DealHub’s self-set October GA for ‘MCP for Admin’ arrives with zero mentions in its own developer docs.
  3. Customer.io splits its MCP write and delete scopes apart, a day before we checked.
  4. Clari’s customer community folds into Salesloft’s. The MCP documentation gap it’s merging into stays open.
01Layer 6 + 8 · Billing and Usage Metering

Sierra and Meta's Personal Agent Protocol promised a spec ‘later this month.’ It’s still a draft with an unimplemented reference repo.

On Oct 6, 2026, Sierra and Meta's “Personal Agent Protocol” (PAP) announcement promised a formal v0.1 spec and a reference implementation “later this month.” Neither has arrived. personalagentprotocol.org, live as of this issue, still frames the spec as a working draft built “with design partners,” and the sample manifest in its own published documentation declares "protocol_version": "0.3", not 1.0. The protocol's own GitHub repository holds exactly one commit, and its README states plainly that it “documents the protocol but does not implement the APIs the specification describes” — the reference implementation Sierra promised doesn't exist either. A follow-up post on Oct 9 (“Poppy”) added 35 more design partners but reset the framing back to “a draft,” with an implementation now promised only “over the next month,” no firm date given.

Why it matters: we flagged PAP in #006 as “a blog post and a promised date,” and compared it directly to DealHub's own missed October deadline two issues back. One month later, that comparison holds in both directions — see the next item. For the five billing and usage-metering vendors we track, PAP's pitch is a shared protocol for how an external consumer's own agent authenticates and transacts with any business, rather than each vendor building its own; that pitch can't be evaluated against a 0.3 draft with no working code behind it. Worth re-checking once Poppy's “over the next month” window actually ends, with the same skepticism we're applying here.

Source: Sierra: Introducing the Personal Agent Protocol · Sierra: Poppy · personalagentprotocol.org · GitHub: personal-agent-protocol

02Layer 3 · CPQ

DealHub's self-set October GA for ‘MCP for Admin’ arrives with zero mentions in its own developer docs.

DealHub's own Sep 9, 2026 press release promised “MCP for Admin” — agentic configuration of pricing rules, approval workflows and guided selling — would be “available to all customers in October 2026.” That month is now over. developers.dealhub.io's own llms.txt page index, which the site publishes specifically for AI agents to crawl its roughly 350 documented endpoints (Quote, Subscription, Revenue Recognition, CRM, Partner, User, Jobs and more), contains zero mentions of MCP or Model Context Protocol anywhere. DealHub's own newsroom shows nothing published in October 2026 corroborating the claim either; the most recent dated item there is a November 2025 acquisition announcement. The only MCP package carrying DealHub's name turned up in community MCP directories is a module published under an individual developer's personal GitHub account — not something DealHub built, owns, or documents, and a risk worth naming on its own: a buyer searching “DealHub MCP” could mistake it for the real thing.

Why it matters: this is DealHub's second missed self-set deadline across the three issues we've covered it in. Unlike CaptivateIQ's open-ended “Coming Soon” (see the registry note below), DealHub gave itself an exact month and missed it the same way it missed its first one. If you're evaluating DealHub's CPQ for an agentic workflow, the documented REST/OpenAPI surface remains what you'd build against today, not the admin layer the press release described two months ahead of its own deadline. We're re-dating the row rather than changing its grade: “claimed, undocumented” remains the right read, now with an explicit date past the vendor's own promise and an impostor-package warning attached.

Source: DealHub developer docs (llms.txt index) · DealHub press release (GlobeNewswire) · DealHub newsroom

03Layer 2 · Marketing Automation

Customer.io splits its MCP write and delete scopes apart, a day before we checked.

Customer.io's MCP documentation, updated Oct 28, 2026 — one day before this check — splits what had been a single write surface into two explicitly separate tool categories: cio_write_api (POST/PUT/PATCH) and cio_delete_api (DELETE), each gated by its own scope (write, write:live, configure) so a client can approve creating or updating data without separately approving deletion. The same update adds strict request-body validation that now rejects any unrecognized field with a 422 error instead of silently dropping it, and switches error responses from plain text to structured JSON — a breaking change for any integration built against the old format.

Why it matters: nothing here moves Customer.io's registry grade — it was already “Documented” on write access and stays there — but the change is exactly the kind of granularity this registry cares about. Write access that lets an agent delete data under the same approval as creating it is a materially different risk than write access that makes you approve those separately, and Customer.io just drew that line explicitly, in its own docs, a day before we looked. It's also a reminder that “documented” isn't a one-time grade: a vendor can keep tightening or loosening the same interface indefinitely, and the registry's job is to keep checking rather than file this one away as settled in August.

Source: Customer.io: MCP get started docs

04Layer 4 · Sales Enablement and Revenue Intelligence

Clari's customer community folds into Salesloft's. The MCP documentation gap it's merging into stays open.

Clari's customer community has been folded into Salesloft's: the community.clari.com thread we cited in #006 for the paused “Copilot MCP Server” now 302-redirects to a dedicated Clari section inside community.salesloft.com. Salesloft's own newsroom, published Sep 2, 2026, confirms the brand consolidation directly — “Clari Forecast retains the Clari name,” it states, while everything else becomes Salesloft-branded — and a merger FAQ on the same community site says integrations and APIs are “unaffected for now,” with changes to be “communicated well in advance,” but says nothing about developer.clari.com's own fate. That page remains blocked by its own robots.txt, unchanged from our last two checks.

Why it matters: the technical story here hasn't moved — the paused Copilot MCP Server still has no release date, and the separate Salesloft-branded MCP server distributed through Claude's connector directory still has no page developer.clari.com will show you — but the organizational story has. When a customer-facing community gets absorbed before the developer docs do, that's usually the order these things happen in: brand first, documentation, if it ever arrives, later. Anyone holding off on a Clari write-access integration because the registry still reads “Unclear” has one more data point that the ambiguity is institutional, not accidental.

Source: Salesloft community: Copilot MCP Server removed · Salesloft newsroom: unified brand identity · Salesloft community: Salesloft–Clari merger customer FAQ

Registry moves

Four rows re-date this week, to 29 October 2026, with no pill-grade changes. DealHub's row is re-dated without a status change: its own October 2026 GA date for “MCP for Admin” has now fully passed with developers.dealhub.io still showing no corresponding documentation, and we've added a note flagging an unaffiliated third-party npm package using DealHub's name. Customer.io's row is re-dated to reflect materially more granular write-access documentation (separate write and delete scopes, stricter validation) published Oct 28, 2026, a day before this check. Clari's row is re-dated to note that its customer community has been folded into Salesloft's; the documentation gap itself — a paused Copilot MCP Server and an undocumented Salesloft-branded MCP server — is unchanged. CaptivateIQ's row is re-dated after its own “AI Agents” FAQ page quietly moved its MCP Server's expected general availability to 2027, still with no auth method, scopes or tool schema published.

No aggregate figures move: the registry still shows 27 of 43 vendors publishing an official MCP server and 33 of 43 documenting agent write access. The single zero-interface category (Sales Compensation & Incentive Management) is unchanged.

Signal lands weekly. The registry updates with it.

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 →