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).

Generate a playbook

Prompt or spec to a validated playbook happens in the NoETL console, which calls this knowledge base and its validator, so the console and every AI share one source of truth. The console generation workspace is on the roadmap.

Open the console · Join the waitlist

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 /api/dsl/validate: live dry-run validation, rule-tagged findings
POST /mcp: MCP tools noetl.dsl.describe, noetl.dsl.schema, noetl.dsl.validate