Use Novem from the interface that fits.
Work in the workspace, CLI, API or MCP where each resource is supported.
Different entry points. Shared resources.
Support varies by resource. The canonical documentation shows the available interfaces and exact routes.
Choose an interface
Use the web workspace, command line, HTTP API or MCP server according to the resource and task.
Address supported resources
Where an interface is available, it works with the platform resource rather than a separate copy.
Use the platform controls
Available programmatic interfaces remain subject to Novem authentication and access controls.
Use the interface that fits.
Supported interfaces work with the same platform resources.
Authentication · organisation context · permissions
Switch interfaces without rebuilding the work.
Why interface consistency matters.
A team should not have to reconcile a separate version of the work for every tool it uses.
Consistent resources
Supported interfaces address the same platform resource so automation and the workspace stay aligned.
Controlled access
Programmatic access uses Novem authentication and the permissions available to that caller.
Connected results
Keep outputs with the run and inputs that produced them so the team can follow the record.
Readable definitions
Use documented formats and repositories for definitions that need to be read, exported or versioned.