Skip to content

Agent guide ​

Use this page when operating from a terminal, code-generation tool, or agent without the interactive docs UI. These docs follow the current source tree and intentionally include the newest available capabilities.

Choose the route for the task ​

TaskStart here
Run a local evaluationTesting locally
Generate configuration without the wizardGetting started → Non-interactive configuration scaffold
Select storage, compute, or authStorage, Compute, Auth
Deploy the serverDeployment options, then Deploying
Build or call an API clientAPI & client and /openapi.yaml
Authenticate automationAPI tokens
Diagnose a deploymentTroubleshooting and Operations

Source-of-truth order ​

When two summaries appear to disagree, use these sources in order:

  1. CONFIG_SPEC for backend selectors and MARIMOHUB_* variables. It generates the Configuration reference.
  2. /openapi.yaml for HTTP paths, schemas, authentication schemes, and response envelopes.
  3. The backend pages for provisioning steps and operational constraints.
  4. The platform deployment guide for topology-specific wiring.

At runtime, GET /api/v1/version reports the deployment version. GET /api/v1/capabilities reports available features and server limits. Super admins can inspect backends through GET /api/v1/admin/config. Use these responses to determine what a deployment supports.

Non-interactive workflow ​

  1. Select one storage, compute, and auth backend from their complete tables.
  2. Copy the configuration scaffold and replace every _replace_me_ value, using the adjacent # e.g. comment when present.
  3. Add backend-specific variables from the generated Configuration reference.
  4. For Helm, replace <VERSION> with an existing GitHub release tag without its leading v.
  5. Validate /api/health, sign in or use a PAT, create a project, start a kernel, and verify a saved notebook survives a restart.

Interactive components are conveniences only. Every required provisioning and validation step has a Markdown equivalent linked above, so raw page Markdown and llms-full.txt remain sufficient.

Provider-agnostic. Deploy anywhere.