ESC
↑↓ navigate↵ open

Home / Signal / #005

Signal #005 · 5 October 2026

Rippling's 'unclear' write access resolves. DealHub's October deadline arrives empty.

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 28 September 2026 Agent Access Registry baseline: all 43 vendors' developer documentation, changelogs, GitHub repos and official press pages re-verified against that dated row.

In this issue

  1. Rippling's ‘unclear’ write access resolves. The docs finally spell out what it can do.
  2. DealHub's self-set October deadline arrives. The developer docs still don’t know about it.
  3. PROS had a public, write-capable API the whole time. We just hadn’t found the subdomain.
01Finance and Operations · HR and Payroll

Rippling's ‘unclear’ write access resolves. The docs finally spell out what it can do.

Rippling's own developer portal now fully documents the Rippling MCP we'd previously flagged as real but unverifiable: a first-party Model Context Protocol server, architected as AI client → Rippling MCP Gateway → MCP server → the Rippling platform, gated by a dual permission model (an admin-configured Gateway policy, plus the connecting user's own role-based access). Authentication is per-user sign-in, not a shared API key or service account; per Rippling's own setup guide, the AI client “never acts as an unrestricted service account, global admin, or static API key.” The Tools reference documents genuine write actions behind that gate: request_time_off, create_draft_hire, and a full custom-object CRUD set (create/update/delete_custom_record, _custom_field, _custom_object). High-impact actions like hiring create a draft for human review rather than executing immediately, and time-off requests route through the normal manager-approval queue; SSNs, home addresses, personal emails and tax IDs are explicitly excluded from what any tool can touch.

Why it matters: we had this one flagged with a confidence caveat in August because Rippling's JS-rendered docs site blocked a direct, automated fetch; the marketing claim was plausible but unverified. It's now fully documented, with named tools, a named auth model, and a named approval path — a “claimed, undocumented” grade resolving the way this registry wants it to: the vendor published the spec, rather than us taking a product page's word for it. If you're building or buying an HR agent workflow, this is a real, scoped interface to design against now, not a demo. Compare it to DealHub in the next item: same kind of ambition, opposite outcome so far.

Source: Rippling: MCP overview · Rippling: MCP tools · Rippling: MCP setup

02Layer 3 · CPQ

DealHub's self-set October deadline arrives. The developer docs still don’t know about it.

Back in September, DealHub's own press release promised “MCP for Admin” — agentic configuration of pricing rules, approval workflows and guided-selling flows — would be “available to all customers in October 2026.” October has arrived. developers.dealhub.io's own page index (an llms.txt file the site itself publishes for AI agents to crawl) still lists zero pages mentioning MCP or Model Context Protocol anywhere on the site; the only agent-facing addition we could find is a pointer to that same index and an OpenAPI export of the existing REST surface. The one MCP package carrying DealHub's name that we could locate, listed on a couple of community MCP directories, is a module published under an individual developer's personal GitHub account — not something DealHub itself built, owns, or documents.

Why it matters: we flagged this exact date back in Signal #003 because, unlike CaptivateIQ's open-ended “Coming Soon,” DealHub gave itself something checkable. The clock has now run out with nothing to show for it. If you're evaluating DealHub's CPQ for an agentic workflow, budget for the REST/OpenAPI surface that exists today, not the admin layer the press release described a month ahead of its own deadline. If the GA does land later this month, we now have an exact date already on record to hold it to.

Source: DealHub developer docs · DealHub press release (GlobeNewswire)

03Layer 3 · Pricing and Packaging Strategy

PROS had a public, write-capable API the whole time. We just hadn’t found the subdomain.

Our registry had PROS at zero on every column — MCP, external API and agent write access all “none found” — with only a login-gated connect.pros.com portal on file. That was incomplete. buildwith.pros.com and marketplace.pros.com publish, with no login wall, a real developer reference covering Quote, Price, Configurator, Catalog, eCommerce and Transportation & Logistics pricing APIs. The eCommerce Quote API's own Redoc-rendered reference documents token-based authentication (a token obtained through the QuoteX Public API, with a 30-day lifespan) and genuine write endpoints: setting a field or grid-cell value, deleting lines from a quote, changing quote status, and adding a row. There's still no MCP server anywhere on the site, and no vendor announcement framing any of this as agent-facing — it's a plain, documented REST API that happens to exist in public.

Why it matters: this is a correction, not a launch, and we're naming it as one: a vendor we'd written off as having nothing to evaluate turns out to have a real, write-capable API sitting one subdomain away from where we'd looked. PROS moves off the all-zero list, but its MCP column stays at “none found” — the gap between “has an API” and “has an agent interface” is exactly the distinction this registry exists to hold onto. It's also a reminder to re-check a vendor that looks entirely login-gated before writing it off: the public docs may just be living somewhere else.

Source: PROS developer portal overview · PROS eCommerce Quote API reference · PROS Marketplace: API documentation

Registry moves

Three rows change this week, all re-dated to 5 October 2026. Rippling moves from “Claimed, undocumented” to “Official” for its MCP server, and from “Unclear” to “Documented” for agent write access, now that its developer portal fully specifies auth, tools and approval flow. PROS moves from “None found” to “Documented” on both external API and agent write access (its MCP column stays “None found”), after we located its public buildwith.pros.com / marketplace.pros.com developer portal. DealHub's row is re-dated without a status change: its own October 2026 GA date for “MCP for Admin” has arrived with developers.dealhub.io still showing no corresponding documentation.

Two aggregate figures move: the registry now shows 27 of 43 vendors publishing an official MCP server, up from 26, and 33 of 43 documenting agent write access, up from 31. 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 →