About this reference #

View this page as Markdown

This reference is generated from the same contracts your AI coding tool reads through the MCP server.

  • Action catalog: every management action a customer can call, with its tier and registration status, each linked to its page of descriptions, arguments, results, and access metadata.
  • turnzero command reference: each subcommand of the turnzero command with its usage line, its options, and its statuses, generated from the command's own texts.
  • Refusals: every refusal the platform returns, by surface, with its status, its cause, and its remedy.
  • An OpenAPI 3.1 document for the management actions you can call with a bearer token, served at /cloud/openapi.json for client generators and API tools.
  • MCP resources and prompts: the resources the MCP server serves, the argument list its prompts share, and each skill a customer can use, with the actions it requires.
  • Contract sources: the indexed documents, schemas, and operating guides.

Registration describes the default dispatcher in this build. It does not guarantee that a caller has the required credential or grant, that a tool is listed for that connection, or that the required service is configured.

Field tables use JSON pointers to identify locations in the complete schema. A parent object's required list identifies mandatory child fields. The complete source includes constraints not expanded into separate rows, references, shared shapes, and alternatives; a summary table does not replace it.

Every page in this reference is generated automatically: the turnzero command reference from the command's own texts, and every other page from the published contract sources, which the Contract sources section below lists. Names and identifiers are copied exactly as the sources write them. A citation of a source that list does not include points to our internal records and has no page here.

Contract sources #

The published contract sources this reference is generated from, one page each. A source that names an action only platform staff can call leaves it out, and its page says so. Each JSON Schema source is also served as the file itself, at its source path under /cloud/reference/sources/.