Validate a team manifest
Validates a team manifest without installing it. Returns structured errors, warnings and a summary of the manifest content (name, version, phase count, agents referenced).
Checks performed:
- YAML syntax and schema validation (phase graph, inputs, agents).
- Unused inputs — inputs declared at the top level but not consumed by any phase.
- Dependencies file (if supplied) — must be a valid YAML array.
- Orphan phases — phases not reachable from the graph root.
The response always has valid: true/false, an errors array, a warnings
array and a summary object. When valid is false, the manifest would be
rejected by teams/install.
From the CLI: cliq team validate ./path/to/team.
No credential is needed from this machine. From another host, send Authorization: Bearer with a dispatch token CliqHub signed for this daemon or a cliq_tok_… personal token of a user in the daemon’s realm; this only works once the daemon is connected to CliqHub. See Authentication.
Authorizations
Not needed from the same machine. From another host: a dispatch JWT CliqHub signed for this daemon, or a cliq_tok_… personal token whose user is in the daemon's realm.
Body
Response
Validation result (always returned — even when invalid)
true when the manifest passes all checks
Issues that would prevent install (empty when valid: true)
Non-fatal observations (orphan phases, etc.)
Parsed manifest metadata (null fields when parsing failed)