ChurnZero's REST API already writes to Accounts and Contacts. Our own note called it read only.
ChurnZero's HTTP API, documented at support.churnzero.com and authenticated with an account level appKey, exposes setAttribute, incrementAttribute and trackEvent endpoints that create and update Account and Contact records. ChurnZero's own integration guide states plainly: “we only allow updates to Accounts and Contacts using our API and Javascript.” Our Aug 21, 2026 registry note described this same API as read only, with writes handled by a separate ingestion API whose agent-scoped use was undocumented. That was a misread: the write capability it was describing is this API, not a separate one, and it has been documented the whole time. No roles, scopes, or permission tiers are documented beyond the appKey itself, and the API's response format (every call returns HTTP 200 with a 1x1 tracking pixel) gives no indication of whether a write actually succeeded.
Why it matters: this is a correction to our own research rather than a vendor announcement, and it moves ChurnZero's Agent write access grade from Unclear to Documented — the registry's aggregate write-access count rises to 34 of 43. It does not touch ChurnZero's MCP status: Agentic Essentials and ChurnZero Connect (MCP) remain verifiable only through an Aug 2026 press release, with zero technical documentation behind the AI-specific interface. The broader lesson travels past ChurnZero: a vendor's plain old REST API, built with no AI framing at all, often already clears the “documented write access” bar this registry checks for, while the newer, flashier MCP server sitting next to it gets none of its own documentation. Grading the boring API honestly matters as much as catching the undocumented new one.
Source: ChurnZero: Integrate ChurnZero using HTTP API · ChurnZero: Agentic Essentials press release