DSL knowledge base · preview

Write NoETL playbooks against the grammar that will run them.

Everything here is generated from noetl-orchestrate-core, the types the server parses playbooks with. Nothing is hand-written, so an AI grounded on it cannot be taught a field or tool kind the server does not have.

Version

loading: …

Tool kinds

Accepted by the parser under default gates. Accepted is not the same as executable: which kinds a live worker can run is reported by workers (RFC Phase 3).

Describe it, get a validated playbook

Coming in RFC Phase 6. Every generated playbook will be checked by the server's own validator at the current schema digest before it is shown as valid, and re-checked on every edit. Until that validator exists this box stays off: an unvalidated answer is the thing this site exists to prevent.

For AIs and tools

GET /schema/v2/playbook.schema.json: release artifact (static)
GET /dsl/manifest.json, /dsl/source.json, /llms.txt: static
GET /api/dsl/{version,schema,tools}: live, from the deployed server
POST /mcp: MCP tools noetl.dsl.describe, noetl.dsl.schema