Explore Forge routes with real schemas and live requests.

This explorer is generated from the same OpenAPI 3.1 document that Forge serves from /api/v1/openapi.json. You can inspect every route, review request and response payloads, and point Try it out at your own live Forge runtime.

Open explorer Download OpenAPI JSON Inspect spec source

- Documented paths

- HTTP operations

- Tagged domains

- Selected live runtime

Try It Out

Choose the Forge runtime this public page should call.

GitHub Pages is static, so the explorer needs one live Forge API base URL for interactive requests. Set it once and the page keeps it in your browser.

Spec defaults active Open health route

Tip: use an HTTPS Forge runtime such as your Tailscale URL when calling from GitHub Pages, and share a preconfigured docs link with ?server=https://your-runtime.

See real payloads

Every route exposes the generated Forge schema for parameters, request bodies, examples, and typed responses.

Try routes live

Swagger UI is enabled directly inside the docs site, so the public page can execute calls against your configured Forge runtime.

Auto-published

GitHub Pages now rebuilds when server-side API source changes land, so the published docs stay aligned with the runtime contract.

Coverage

Forge API groups surfaced in the explorer.

The group cards below come from the generated OpenAPI document and give a fast view of the product domains exposed in the HTTP API.

Explorer

Interactive request and schema reference.

If Try it out fails, the docs page is usually pointing at the wrong runtime origin or the runtime is not allowing that browser origin through CORS yet.

This page is published from generated docs assets in openclaw-plugin/docs and rebuilt by GitHub Pages whenever the API documentation inputs change.