ROCKETRIDE_COMPONENT_REFERENCE

RocketRide Component Reference

Last Updated: June 2026

---

How Component Information Is Organized

When the RocketRide VS Code extension is installed, it populates a .rocketride/ directory in your workspace:

.rocketride/
├── services-catalog.json    # Summary of ALL components (name, class, lanes, descriptions)
├── schema/                  # Detailed config schema for each component
│   ├── webhook.json
│   ├── llm_openai.json
│   ├── qdrant.json
│   └── ...                  # One file per component
└── docs/                    # Documentation files (these files)

IMPORTANT: Always read .rocketride/services-catalog.json for the current list of available components. The catalog is the single source of truth: it is generated from the connected server and may contain components not listed in this document.

See also: docs/README-nodes.md is the node catalog grouped by category, with each node's lanes and the wire-vs-bind rule. docs/README-node-schema.md explains the services.json model (lanes, preconfig/profiles, fields, shape) behind this reference and the canvas UI.

Reading the Catalog

Each entry in services-catalog.json has this structure:

{
	"name": "component_provider_name",
	"classType": ["category"],
	"description": "What the component does",
	"lanes": {
		"input_lane": ["output_lane_1", "output_lane_2"]
	},
	"invoke": {
		"llm": { "description": "LLM used by the component", "min": 1 },
		"tool": { "description": "Tools available to the component", "min": 0 },
		"memory": { "description": "Memory store", "min": 0, "max": 1 }
	}
}

Key fields:

• name: the provider value you use in pipeline files
• classType: component category: source, data, text, image, audio, video, embedding, llm, store, database, tool, agent, memory, infrastructure, target, preprocessor
• lanes: the definitive reference for data flow. Each key is an input lane; its value array lists the output lanes produced. An empty array [] means the component consumes data with no lane output (e.g., storage, response). Source components use _source as the input lane key
• invoke: (optional) defines what control-plane connections the component requires or accepts. Each key is a classType (e.g., llm, tool, memory) with min/max constraints and a description. Components with invoke need corresponding entries in the control array of the pipeline definition