AsyncAPI channel · wasmCloud · wasmCloud Control Interface API

wasmbus.ctl.v1.{lattice}.provider.start.{hostId}

Command channel for starting a capability provider on a specific wasmCloud host. Providers are identified by their OCI image reference and a link name that scopes their configuration.

Open source AsyncAPI → All wasmCloud channels wasmCloud provider profile
Provider: wasmCloud AsyncAPI: v2.6.0 Spec: wasmCloud Control Interface API Operations: 2 Messages: 2

Channel address

wasmbus.ctl.v1.{lattice}.provider.start.{hostId}

Parameters

Operations

publish
startProvider
Start a capability provider on a host
receiveStartProviderAck
Receive start provider acknowledgment

Messages

StartProviderCommand
Command to start a capability provider on a wasmCloud host
Content-Type: application/json
CtlOperationAck
Acknowledgment response for control interface commands
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.