SOIT Docs
API Reference

Plugins API

API surface for SOIT plugin package installation, lifecycle, artifacts, capabilities, and runtime registry tools.

The plugins API manages plugin packages and the capability artifacts they export. It is also the query surface for plugin-owned skills and MCP servers — they have no separate APIs.

Prefix

/api/v1/plugins

Endpoint families

MethodPathPurpose
POST / GET/Register plugins; list with plugin_type filter
POST/package?mode=auto|reinstallOne-click zip upload: install, upgrade, or (confirmed) reinstall
GET / PUT / DELETE/{plugin_id}Inspect, update, or delete a plugin
POST / GET/{plugin_id}/versionsCreate and list immutable versions
GET/{plugin_id}/releasesRelease ledger (publish/rollback history)
POST/{plugin_id}/publish, /{plugin_id}/rollbackMove the live release pointer
POST / DELETE/{plugin_id}/installInstall into or uninstall from a workspace
POST/{plugin_id}/install-package, /{plugin_id}/upgrade-packagePackage-based install and upgrade
POST/{plugin_id}/enabledEnable or disable an installation (DB + filesystem manifest)
GET/{plugin_id}/installationsInstallation state per workspace
GET/{plugin_id}/artifacts, /artifactsProjected artifacts, filter artifact_kind=skill|mcp_server|tool|workflow_node
GET/capabilitiesCapability query, filter kind=skill|tool|mcp_tool|mcp_resource|workflow_node
POST/runtime/reloadRe-sync the in-process runtime registry
GET/runtime/toolsInspect tools the runtime router can dispatch

Notes

  • mode=auto package upload creates new plugins, upgrades on version change, and returns 409 CONFLICT (details.reason="same_version_exists") for same-version re-uploads.
  • Lifecycle operations run projectors that create or archive plugin-owned artifacts — see Plugins.

On this page