One hub, every endpoint.
Live OpenAPI 3.1 explorers for the REST services, prebuilt JSON snapshots of the shared game databases, and machine-readable feeds — all generated from the open monorepo.
Everything, one place
API directory
Live OpenAPI specifications
3 endpointsInteractive OpenAPI 3.1 explorers rendered inside the dashboard.
The primary public REST API served by axum-kbve — auth, profiles, chat, and platform services.
Staff-only firecracker-ctl service for managing microVM build and runtime workloads.
Game-services API behind the ChuckRPG launcher — sessions, characters, and instance orchestration.
Static data endpoints
16 endpointsPrebuilt JSON generated from the MDX content collections at every deploy.
Every item in the shared ItemDB with stats, sprites, and cross-game references.
The application reference index — tools, services, and integrations.
The CI dispatch registry — every buildable target in the monorepo.
Curated resource index across the docs.
Structure definitions for the building and simulation systems.
Metadata for every docs page — titles, descriptions, and tags.
Feeds & machine-readable
3 endpointsSyndication and LLM-friendly exports of the site.
Condensed site index for language models.
Full-content export for language models.
Questions
Frequently asked
Where is the interactive API explorer?
The dashboard at /dashboard/api/ renders live OpenAPI 3.1 specs for the KBVE public API, the staff-only Firecracker control service, and the ROWS game-services API.
How fresh are the JSON data endpoints?
They are regenerated from the MDX content collections on every deploy, so they always match the published docs pages.
Do I need an API key?
The static JSON endpoints and feeds are fully public. The REST API uses Supabase JWT auth for authenticated routes — see the API project docs for details.
Can I use this data in my own project?
Yes — everything is generated from the public monorepo. Attribution is appreciated but the data endpoints are free to consume.