CLI Reference

The runvero CLI provides both interactive tool execution and server gateway modes.

runvero run

Execute a WASI 0.2 WebAssembly component tool:

runvero run <COMPONENT_PATH> [OPTIONS]

Options

Flag	Description	Default
--input <JSON>	JSON input payload passed to the guest tool	"{}"
--fuel-limit <N>	Maximum instruction units allocated for execution	10,000,000
--memory-limit-mb <MB>	Hard memory ceiling in megabytes	16
--timeout-ms <MS>	Isolated wall-clock epoch deadline in milliseconds	5,000
--raw	Output only the raw guest string without telemetry headers	false
--breakdown-json	Emit structured execution telemetry as JSON	false
--allow-host <HOST>	Whitelist scoped HTTP egress hostname (e.g. api.example.com)	None

Examples

# Set a custom 50M fuel limit and 32MB RAM cap
runvero run tools/calc.wasm --input '{"expr": "1 + 1"}' --fuel-limit 50000000 --memory-limit-mb 32

# Pipe clean output into jq
runvero run tools/analyzer.wasm --input '{"file": "logs.txt"}' --raw | jq .summary

---

runvero serve

Start the Axum HTTP REST and Model Context Protocol (MCP) gateway:

runvero serve [OPTIONS]

Options

Flag	Description	Default
--host <IP>	Network address to bind to	127.0.0.1
--port <PORT>	Network port to listen on	8080
--tools-dir <DIR>	Directory containing .wasm tools to discover	./tools
--max-concurrency <N>	Maximum concurrent execution workers	64

Endpoints

• GET /health — Health check and readiness probes.
• GET /v1/tools — List all registered WASI components and their input schemas.
• POST /v1/execute — Execute a tool with fuel and memory budgets.
• POST /mcp — JSON-RPC 2.0 endpoint implementing Anthropic Model Context Protocol (initialize, tools/list, tools/call).