Beta
OpenAPI + webhooks + MCP

Connect everything.
Break nothing.

Connect external agents and applications through remote MCP, portal-scoped REST, and signed webhooks.

Service accountsSigned webhooksFiltered external OpenAPIOfficial target catalog

Official integration targets

Only supported targets and live channels are shown here.

Claude
ClaudeGA
Remote MCP over Streamable HTTP with OAuth DCR by default and service-account fallback for direct HTTP clients.
ChatGPT
ChatGPTGA
Remote MCP in ChatGPT developer mode with OAuth DCR and the same governed tool surface as Claude.
n8n
n8nGA
REST plus signed webhooks for orchestration and sync workflows.
Gmail
GmailGA
OAuth connector for email workflows and AI-assisted processing.
Google Drive
Google DriveGA
OAuth connector for file synchronization and governed document ingestion.
Google Calendar
Google CalendarGA
OAuth connector for scheduling signals and calendar-driven automations.
Custom ERP
Custom ERPGA
Portal-scoped REST endpoints documented in the filtered external OpenAPI spec.
WordPress / WooCommerce
WordPress / WooCommercePreview
Reference architecture only in v1; no first-party plugin promise.
Telegram
TelegramGA
Native messaging channel wired into the governed agent runtime.
WhatsApp
WhatsAppGA
Native messaging channel with linking flows and governed agent execution.
Need another system? Use the filtered external OpenAPI contract and signed webhooks.

Official paths by target

Claude/ChatGPT uses the public MCP surface. n8n and ERP integrations use the filtered OpenAPI contract plus signed webhooks. WordPress/WooCommerce stays preview as a reference architecture.

Claude / ChatGPT

Official OAuth/DCR remote MCP path for Claude, ChatGPT, and Cowork.

GA
Official path
Remote MCP over Streamable HTTP
Entry point
/mcp
Authentication
Company-scoped service account bearer key
ClaudeChatGPT

n8n

Automation path using REST plus signed webhooks.

GA
Official path
Portal-scoped REST plus signed webhooks
Entry point
/api/platform/openapi/external.json
Authentication
Service account for runtime calls, user session for admin setup
n8n

Custom ERP

ERP integration path via portal-scoped REST endpoints and webhook sync.

GA
Official path
Portal-scoped REST plus signed webhooks
Entry point
/api/platform/openapi/external.json
Authentication
Service account for runtime calls, user session for admin setup
Custom ERP

WordPress / WooCommerce

Reference architecture for CMS or commerce embedding, without first-party plugin support.

Preview
Official path
Reference architecture
Entry point
/platform/catalog/targets
Authentication
Preview architecture review before implementation
WordPress / WooCommerce

An API built for developers

Portal-scoped REST, signed webhooks, and remote MCP all point to the same governed platform surface.

platform
1# Service-account authenticated REST call
2# Host: your API deployment
3
4curl -X GET https://your-api-host.example.com/c/companies/<companyId>/sales/invoices \
5  -H "Authorization: Bearer <nzsa_live_service_account_key>" \
6  -H "X-Portal: company" \
7  -H "Accept: application/json"
8
9# Official external spec
10GET /api/platform/openapi/external.json

Real workflows, not demos

Inspect accounting, sales, and HR workflows through one governed MCP surface.

Claude

Banking & Reconciliation

ChatGPT

Accounting

Claude

Approvals

ChatGPT

Swiss Payroll

Cash Flow Forecast

Banking & Reconciliation

Accounting

Swiss VAT

Approvals

Comments & Tasks

How it works

Three official paths, one governed platform contract.

01

Create a service account

Provision a tenant- or company-scoped machine principal with explicit permissions and modules.

02

Integrate through the real contract

Use remote MCP for agents, or portal-scoped REST plus signed webhooks for application sync.

03

Operate with governed flows

Approvals, audit metadata, and catalog-driven surfaces stay aligned with the runtime.

●Bearer nzsa_live_••••••••

One governed platform contract.

Service accounts for machines, user sessions for admin setup, and signed webhooks for sync.