The full wings API reference is now on the site

The wings page no longer just links to the docs — the complete

API reference now lives right on it.

The whole API on one page

Seven reference tables cover every endpoint, grouped the way a panel

developer actually uses them:

• System & discovery — /v1/ping, /healthz, /v1/self, /v1/nodes,

/v1/system/info, /v1/events, /v1/metrics.

• Containers — the full surface: create/inspect/lifecycle, logs?follow=1

and stats?stream=1 as SSE, exec, the interactive terminal over

websocket (/terminal/ws) and SSE, and the container file browser

(fs/ls|cat|tree, cp).

• Images — list, inspect, Docker Hub search, async pull with progress,

tag, push, remove.

• Blueprints — catalog, detail, async install/uninstall.
• Tasks — poll background jobs, including persisted finished tasks.
• Services & functions — CRUD, scale, invoke.
• Cluster — fleet health, replicas, containers across nodes.

Each table lists method, path and a one-line description, and five curl

examples show the calls end-to-end — from auth and the first /v1/ping to

pulling an image and polling its task, opening a terminal session, and

hitting a specific node with ?node=.

Still experimental — on purpose

Wings is a young project, so the page now says so clearly: the API works and

everything on it is real, but endpoints and payloads can still change between

versions, and it is not recommended for production panels yet. The API

reference is still the best map of where wings is going — it will simply be

kept in sync as the API evolves.

Around the repository

The wings repository also picked up a MIT license, a **contributing

guide and a security policy**, alongside the existing OpenAPI schema,

cluster guide and the automated release pipeline (latest: v0.4.x).

Next up remains the panel itself — a UI that sits on this API.