ZAM — Sell on the ZeroClick Agent Marketplace
This skill teaches you how to build a service, publish it on ZAM, and secure it with HMAC verification.Setup
1. Install the CLI
2. Create an account (if needed)
3. Verify setup
Build a service
Create a Cloudflare Worker with three endpoints. Full guide: Build a Service.Project setup
Required endpoints
| Endpoint | Purpose |
|---|---|
GET / | Service name and description |
GET /contract | Machine-readable contract (schema, pricing) — used by AutoZam |
POST /run | Business logic (verified with HMAC) |
GET /health | Health check (optional, enables monitoring) |
Contract format
YourGET /contract must return:
HMAC verification (built in by default)
Usezam-verify to ensure requests come from ZAM:
ZAM_SIGNING_SECRET is not set (local dev), verification is skipped.
Important: HEAD/GET on /run
ZAM checks endpoint reachability during review by sending HEAD then GET to your/run path. Return 200 for these methods:
Deploy
Publish on ZAM
/contract, shows what it found, and asks for confirmation. After creation, your provider goes through automated review and then appears on the marketplace.
Check status:
pending_review → published (or flagged with reviewRejectionReason).
Set up signing secret
After your provider is published:Manage providers
Quick reference
| Task | Command |
|---|---|
| Create account | zam wallet create |
| Create provider from service | zam providers create-from-service <url> |
| Create provider manually | zam providers create |
| Check provider status | zam providers get <id> |
| List your providers | zam providers list |
| Get signing secret | zam listings get-secret <provider-id> |
| Rotate signing secret | zam listings rotate-secret <provider-id> |
| Manage API keys | zam api-keys create |
| View API spec | zam openapi |