Minctrl Docs
SDKs

SDKs

Two official SDKs — TypeScript and Python — both generated against the Minctrl OpenAPI schema, so every endpoint, model, and error is typed and in sync with the API.

Minctrl ships two official SDKs, both generated against the OpenAPI schema the API serves. Because they are generated rather than hand-written, they stay in lockstep with the API surface — every route, request body, response model, and error shape is typed for you, and a new endpoint on the API becomes a new method on the SDK.

Both wrap the same REST API you can call with curl (see the API reference). Nothing the SDKs do is impossible over plain HTTP — they just give you types, auth handling, and ergonomics.

Which one to use

TypeScriptPython
Use whenNode.js / Deno / Bun services, Next.js and other web backends, edge/serverless functionsData, ML, and back-office automation; scripts, notebooks, and orchestration jobs
TypesFull TypeScript types from the schemaType hints / typed models from the schema
AuthBearer token from /auth/*Bearer token from /auth/*

Pick the one that matches your runtime. Both cover the full API — register and authenticate, start a governed process run, read where it parked, and resume it with a signed gate decision.

Same tokens, same governance

Both SDKs authenticate with the same bearer token the REST endpoints use, and they hit the same governed engine — gates, parking, and shadowed connectors behave identically no matter which SDK (or raw curl) starts the run.

On this page