Marketplace

The marketplace is the host's plugin registry. Since 4.0.0-rc.1 it serves the local .fyp lifecycle under /api/plugin-packages — install (upload), inspect, enable, disable, and uninstall for every plugin, official and third-party alike; POST /upload is the install path for a built .fyp (used by the marketplace UI's upload button). Catalog browsing and install/update by id moved to the unified plugin store under /api/plugin-store. A deprecated /api/plugin-market compat layer still forwards the lifecycle endpoints 1:1 (with Deprecation headers); its old catalog endpoints answer 410 Gone naming their /api/plugin-store replacements.

Unified plugin store (Claude / Codex / Grok / FengYu)

Since 4.0.0-alpha.7. Alongside the FengYu marketplace above, the Stores tab subscribes to third-party Claude Code, OpenAI Codex, and Grok Build marketplace catalogs and merges them into one browsable, source-badged grid.

• Sources. Add/remove/refresh marketplace sources under /api/plugin-store/sources. The FengYu source is seeded by default; Claude sources serve .claude-plugin/marketplace.json, Codex sources serve .agents/plugins/marketplace.json, and Grok sources serve .grok-plugin/marketplace.json (for example, the official xAI catalog).
• Install. Claude/Codex/Grok plugins are installed by cloning their git source (JGit). Claude and Grok url/subdirectory sources verify a pinned sha; Codex and Grok local sources record the resolved HEAD sha in the install record so every install carries an auditable fingerprint.
• Security. Catalog names are slugified to a single safe path segment before they reach the filesystem, clone URLs are restricted to https/http/file, skill extraction skips symlinks, and catalog responses are capped at 16 MiB. Third-party catalog content is treated as untrusted.
• Signed FengYu packages. A FengYu catalog may publish sha256, Ed25519 signature, and keyId. The host downloads once, verifies those exact bytes, checks publisher namespace and package/key revocation against bundled plus user trust roots, then installs the same file. Configure user roots in <runtime-root>/trusted-plugin-publishers.json (by default <working-directory>/.fengyu/...); create catalog signature metadata with fengyu sign.
• Windows unsandboxed toggle. On platforms without a native process sandbox, a Settings row (gated behind a confirmation dialog, defaulting off) lets you opt plugin workers into the unrestricted() channel. See the changelog for the alpha.7 security hardening.

Official plugins

Infinia ships with a set of official plugins — real capabilities the Agent can orchestrate out of the box. Each has its own page:

Plugin	What it does	Docs
Excel Splitter	Split workbooks by sheet, column value, or complex rules — with six AI tools.	Excel Splitter →
Email Center	Multi-account SMTP/IMAP, contact management, batch sending, archives — nine confirmation-first AI tools.	Email Center →
Offline Python Builder	Build offline Python install repositories (wheelhouses) with all dependencies — six AI tools and async builds.	Offline Python →
Markdown Editor	Split-pane editor with isolated server-side rendering.	Markdown Editor →

Browse the catalog

Since 4.0.0-rc.1, catalog browsing happens under /api/plugin-store — the unified, source-badged view rendered by the UI's Stores tab. The FengYu source lists each installable plugin with its manifest, source (OFFICIAL or THIRD_PARTY), enabled flag, and supportsAi badge, merged with the Claude/Codex/Grok sources described above. The deprecated GET /api/plugin-market alias answers 410 Gone, naming /api/plugin-store/catalog as its replacement.

Install a plugin

There are three install paths — two local ones under /api/plugin-packages, one from the store catalog under /api/plugin-store:

Method + path	Body	Use when
POST /api/plugin-packages/upload	multipart .fyp file	You have a built .fyp archive (the normal path; the CLI uses this).
POST /api/plugin-packages/upload-native	JSON {path}	Desktop only — install from a .fyp that already lives at a local filesystem path.
POST /api/plugin-store/{uid}/install	—	Install a plugin already listed in the store catalog by its uid.

• POST /api/plugin-packages/upload parses the uploaded .fyp, extracts its manifest.json, validates the structure, and registers the plugin. Its source becomes THIRD_PARTY. When the package's id matches an installed plugin the upload replaces it — the host stops the running worker (update gate) and atomically swaps the package directory; the enabled state carries over.
• POST /api/plugin-store/{uid}/install is the one-click install for a plugin already present in the store catalog but not yet installed locally. The deprecated POST /api/plugin-market/{id}/install answers 410 Gone naming this replacement.

In the marketplace UI, every local .fyp pick first goes through a confirmation dialog backed by the inspect endpoints below: it shows the incoming version against the installed one (1.0.0 → 1.1.0), warns on a downgrade or a same-version reinstall, and only then uploads. The catalog, inspect, and install responses all carry permissionsOsEnforced — when it is false (every platform except the Linux sandbox today), the confirmation states that the plugin's declared permissions are not enforced by the operating system on this platform. An installed plugin's detail drawer also offers Update from local package as the per-plugin entry point.

TIP

Upload a built .fyp from the marketplace UI, or POST it directly: curl -F file=@./my-plugin-1.0.0.fyp -H "Authorization: Bearer $FENGYU_TOKEN" http://<host>/api/plugin-packages/upload.

Update

POST /api/plugin-store/{uid}/update

Pulls the latest version of a store-catalog plugin and replaces the installed copy. No body required — the host resolves "latest" from the source catalog. The deprecated POST /api/plugin-market/{id}/update answers 410 Gone naming this replacement.

Updates are transactional. The old package is retained as a rollback snapshot until the new Worker passes its reserved startup handshake; a failed spawn/handshake restores and preflights the old package. Interrupted transactions are recovered on host startup. When the new manifest adds permissions, pass ?confirmPermissions=true only after showing the added permissions to the user; otherwise the host rejects the escalation.

Update from a local package

For a plugin that is not in any catalog (e.g. installed from a locally built .fyp), the catalog update above cannot resolve a download URL. Upload the new package instead — same id, new version:

POST /api/plugin-packages/inspect       # multipart "file"; or /inspect-native {"path": "..."}
POST /api/plugin-packages/upload        # replaces the installed copy after confirmation

/inspect reads the incoming manifest without installing and returns a PackageInspection — {id, name, version, installed, installedVersion, comparison} where comparison is upgrade, downgrade, same, or null for a not-yet-installed id — so a client can confirm the version step (and warn on a rollback) before the upload stops the worker and swaps the package.

Enable / disable

PATCH /api/plugin-packages/{id}/enabled
{ "enabled": true }   // or false

Toggles the plugin's enabled flag. Disabling stops the worker process immediately — the host's PluginProcessManager tears the OS process down and any in-flight RPC rejects. Enabling does not eagerly spawn the worker; the process is started lazily on first invoke. See Plugin Overview for the full lifecycle.

Uninstall

DELETE /api/plugin-packages/{id}?deleteData=true|false

The data policy is required and explicit. The marketplace UI asks twice: first whether to uninstall, then whether to permanently delete runtime data. deleteData=false stops the worker and removes the unpacked package while retaining plugin-data/<id> and the provisioned DB namespace/credentials for a later reinstall. deleteData=true also removes those resources; if filesystem deletion cannot be completed, the endpoint returns an error instead of reporting a false success. Database cleanup that cannot complete is retained as DELETE_PENDING for retry.

Catalog URL override

The catalog the marketplace browses is fetched from a configurable URL. Point the host at a different catalog (e.g. a private registry) with a system property:

java -Dfengyu.marketplace.catalog-url=https://internal.example/fengyu-catalog.json -jar fengyu.jar

Endpoints summary

Endpoint	Action
GET /api/plugin-store/catalog	Browse the unified store catalog → source-badged plugin grid
POST /api/plugin-packages/upload	Install from uploaded .fyp (same id installed → update)
POST /api/plugin-packages/upload-native	Install from a local path (desktop)
POST /api/plugin-packages/inspect	Preview an uploaded .fyp → install-vs-update + version step
POST /api/plugin-packages/inspect-native	Preview from a local path (desktop)
POST /api/plugin-store/{uid}/install	Install a store-catalog plugin by uid
POST /api/plugin-store/{uid}/update?confirmPermissions=<boolean>	Health-gated update to latest; explicit permission escalation confirmation
PATCH /api/plugin-packages/{id}/enabled	Enable/disable (disabling stops the worker)
DELETE /api/plugin-packages/{id}?deleteData=<boolean>	Uninstall with explicit runtime-data retain/delete policy

The deprecated /api/plugin-market compat layer forwards the lifecycle rows above 1:1 (with Deprecation headers); its catalog rows — GET /api/plugin-market, POST /api/plugin-market/{id}/install, POST /api/plugin-market/{id}/update — answer 410 Gone naming their /api/plugin-store replacements.

Store download trust

The native Infinia Store client bundles the production platform-ed25519-2026 public key for https://store.summer.fan. Configure that HTTPS address as the store API base in Settings. Downloads still require both SHA-256 integrity and an Ed25519 signature over the downloaded bytes; an unknown or revoked key fails closed.

Operators can add public keys or revoke a bundled key in <runtime-root>/trusted-store-keys.json, then restart the backend. Obtain keys through an authenticated deployment channel, such as the Jenkins public trust artifact, and verify its fingerprint before installing it. Never copy the store's private .b64 key into a client. To revoke the bundled key:

{"keys": [], "revokedKeys": ["platform-ed25519-2026"]}

Store platform trust is separate from trusted-plugin-publishers.json, which governs third-party catalog publishers.

Next steps

• Plugin Overview — the install → enable → invoke → disable → uninstall lifecycle.
• Build & Deploy — produce a .fyp to upload.
• SDK & CLI — the create + build commands.