Machine interfaces

Helm has a registered HTTP API and a generated machine-readable operation manifest. These support consistent descriptions of method, route and permission requirements.

Available today

Use the HTTP integration guide with an owned, scoped user credential. The manifest inventories operations; it does not execute them on its own.

A database function, source module or manifest row is not evidence of a supported client transport.

Planned transport

A separately runnable or hosted MCP server is planned. There is no supported launch command or deployed MCP connection URL documented for this version. Read MCP status before attempting a connection.

Keep descriptions aligned

When a registered operation changes, update and check the generated machine description along with the mounted route and scope. Never add a planned money command to a tool inventory as though it were available.

Any future transport must preserve admitted-user identity, ownership, scopes and the same financial retry rules as HTTP. It should not grant a language model a privileged database client to work around validation.

See generation drift for maintenance and financial safety for command behavior.