Synet CLI uses a plugin architecture to extend its functionality without bloating the core.
Plugins are optional and modular — handling payments, storage, advanced networking, and more.
This design follows the Unix philosophy: Do one thing well, and compose functionality as needed.
payment-sei
, payment-iota
.storage-zerog
.Plugins are installed via:
synet plugin install <plugin-name>
Example:
synet plugin install payment-sei synet plugin install storage-ipfs
Plugins integrate into CLI namespaces dynamically.
Example — Payment Plugins:
synet payment sei create-invoice 10 --memo "AI Service" synet payment sei pay --to sei1xyz... --amount 10 synet payment sei balance
Example — Storage Plugins:
synet storage ipfs upload myfile.zip synet storage zerog push dataset.parquet
Discover available plugins:
synet --discover
Output:
Available plugins: [email protected], [email protected] Use `synet plugin install <name>` to install.
Each plugin typically includes:
plugin-name/
├── plugin.js # Main CLI extension logic
├── manifest.json # Metadata (name, version, commands exposed)
├── SHA256SUMS.sig # Cryptographic signature
synet plugin install payment-sei payment-iota
synet payment sei create-invoice 5 --memo "Data Service" synet payment sei track --invoice sei1xyz...
synet payment iota pay --to iota1xyz... --amount 50
The Synet Plugin System is structured so it can later evolve into a full Synet Plugin Manager (SPM), supporting:
This ensures today's architecture remains compatible with tomorrow's upgrade paths.
Plugins are the future of Synet's flexibility.
Starting with payment and storage modules, Synet's agent economy can evolve into a fully autonomous service marketplace.