LXLEONARDX
Start building

LEONARDX / WORKSPACE

Plugin registry

Review trusted plugin metadata and its current boundaries.

Back to developer platform
Trusted registry · metadata only

Review trusted plugin contracts and runtime access.

Approved manifests are persisted by plugin ID and version. Registration validates permissions and compatibility; enabled plugins can be invoked through the protected runtime gateway.

Manifest reference Registry API
Enabled manifests
Only enabled metadata is public; runtime calls require an authenticated gateway request.
1 entry
  • LEO Project Reader

    leo-project-reader · v1.0.0 · API 1

    Reads supported project information for LeonardX.

    Enabled · metadata only
Manifest contract
Validated before metadata is stored.
id · lowercase letters, digits, hyphens
version · semantic version (major.minor.patch)
apiVersion · 1
permissions · projects:read, projects:write, webhooks:read
entrypoint · public HTTPS URL
Security and lifecycle
  • Registration and lifecycle changes require platform-owner 2FA.
  • Register an updated manifest as a new version; an existing version cannot be overwritten.
  • Lifecycle states are registered, enabled, disabled, and deprecated.
  • Runtime actions require a matching manifest permission and server-only gateway token.
  • The gateway calls the plugin's trusted HTTPS entrypoint; it does not execute arbitrary uploaded code inside Next.js.

Registry controls

These controls manage the platform-wide trusted plugin registry. Only the platform owner can approve or change trusted integrations; manifests do not install or execute uploaded code.

Registered versions

No manifest versions registered.

Integration StudioSimulation · no request sent

Follow the integration, one step at a time.

Explore real LeonardX contracts with sample code and a simulated terminal. This walkthrough never uses credentials, contacts endpoints, or changes account data.

Source-backed examples

Walkthrough scenario

The current registry validates metadata and a small permission vocabulary.

Review a manifest

A valid manifest has a semantic version, API version 1, HTTPS entrypoint, and only declared permissions.

leo-plugin.json1 / 2
{  "id": "sample-inspector",  "name": "Sample Inspector",  "version": "1.0.0",  "apiVersion": "1",  "description": "Manifest example only",  "permissions": ["projects:read"],  "entrypoint": "https://example.invalid/plugin.js"}

Execution preview

Synchronized to the highlighted code

Example manifest · not registered
leo · pluginssimulated

[SIMULATION] Manifest not submitted

Schema: Zod-validated metadata

Entrypoint: HTTPS required

No extension code is loaded or executed

What is live? The examples describe existing API, SDK, CLI, and webhook behavior. This preview itself is local UI only and does not report a real execution.
Read plugin guideView registry endpoint

Manifest validation: step 1 of 2. Review a manifest