Skip to main content
All zend apps commands use the key saved by zend login. deploy can also use ZEND_APP_KEY from the environment.

​
create

Creates a private ZApp and prints its credentials once:
Slugs are 2–31 characters of a-z, 0-9 and -. You can have up to 10 apps.

​
list

​
check

Checks the manifest’s interaction rules locally, without uploading. Defaults to ./zapp.json. It stops on mistakes the server would also refuse:
  • Unknown states, and transitions from or to them.
  • An initial state that isn’t in states.
  • Transitions out of a terminal state.
  • A move listed twice.
  • Unknown keys in a transition, with a “did you mean” hint for a misspelt serverOnly.
It also lists the moves only your server can make:

​
deploy

Runs check, then uploads the manifest as a new version. Defaults to ./zapp.json. The app is found by the manifest’s app field.
With visibility: "public", the status becomes in_review. Track it with zend apps review. If ZEND_APP_KEY is set, deploy uses it instead of your login. Use this in CI.

​
info

Shows the app’s id, status, visibility, tier, manifest version, this month’s network budget, and the latest review.

​
review

Shows the listing status and every review with its findings.

​
testers add

Lets someone open your private app while you build it. You’re always a tester of your own apps.

​
payout

Sets the Zend account that receives your app’s share of split payments.

​
rotate-key

The old value stops working immediately. Update your server and CI secrets right away.

​
resolver-key

Generates an Ed25519 key for signing prize results, locally: