Canonical representations
- Human index
- /nodes/
- JSON index
- /registry.json
- Markdown index
- /registry.md
- Node HTML
- /nodes/{slug}/
- Node JSON
- /nodes/{slug}.json
- Node Markdown
- /nodes/{slug}.md
- Node schema
- /schemas/node-record-v1.json
- Template JSON index
- /templates.json
- Template Markdown index
- /templates.md
- Template HTML
- /templates/{slug}/
- Template JSON
- /templates/{slug}.json
- Template Markdown
- /templates/{slug}.md
- Template schema
- /schemas/template-record-v1.json
Agent selection contract
- Fetch the node registry and search capabilities and providers.
- Check readiness and installation availability before selecting a record.
- Fetch the canonical node or template JSON record.
- Install only nodes whose readiness is installable, validated, or stable.
- Connect to the user's n8n MCP and build or import the workflow there.
- Validate credentials, node versions, and workflow structure before execution.
- Return source URLs and unresolved requirements to the user.
Readiness is explicit
Appearing in the registry means a node is documented, not necessarily ready to install. The readiness field is separate from lifecycle status, so an alpha record can be public without being mistaken for a usable package.
- Documented
- The node appears publicly in the registry with its current facts and limitations.
- Installable
- A working GitHub repository and exact installation command are available.
- Validated
- The package and a representative example workflow have passed Tarvos tests.
- Stable
- The node is production-ready and carries a stable lifecycle release.
Required record fields
Every record provides a stable slug, name, summary, description, release readiness, lifecycle status, integration kind, node types, providers, credential definitions, capabilities, installation status, version, license, and update date. Repository and command fields become required when installation is available.