Developer platform
The same authority model, through every surface
API, CLI, and MCP are documented around the same permission, policy, and idempotency model as the workspace. There is no privileged automation path.
curl https://app.example/readyz // 503 Service Unavailable · example { "status": "not_ready", "request_id": "req_demo_01" }
REST
API reference
The allowlisted health operations and complete public response shapes generated from the canonical contract.
Browse endpoints →TERMINAL
zcs CLI
Review the proposed operator command model without mistaking the CLI for a released distribution.
Review the CLI →AGENTS
MCP server
Read-first tool design where every proposed change stays a preview until a named person approves it.
Review MCP →Four rules that shape every integration
Scope is server-side
Identity comes from a verified Access assertion; scope from a server-generated session. Request data never grants authority.
Every write is keyed
Idempotency-Key is required on order creation and release. Same key and input replays the original result; same key and different input is a 409.
Validation gates every step
Ready and release refuse while validation.stale is true or the latest attempt failed — a 422 with the reason.
Errors name the next step
Every failure is a Problem: upper-case code, short message, and a request id to quote to support.
Start with the published boundary
Private workflow access requires explicit provisioning, a data-handling agreement, and separate acceptance evidence.
ZeroClickShip
Evidence-first shipping operations for UK ecommerce teams and fulfilment operators.
ZeroClickShip is a shipping operations platform. Carrier services are contracted directly between the merchant and the carrier under the merchant's own accounts. Capability status shown on this site reflects demonstrated, in-source, and roadmap work; provider activation is subject to integration and acceptance testing. © 2026 ZeroClickShip Ltd.