Reference

Purpose: authoritative HTTP, schema, and configuration lookups while building or operating Fleet.

Updated

Find quickly: HTTP API (routes + bearer matrix) · Schemas & OpenAPI (mirrored to Hosting /schemas/) · Configuration.

Audience Integrators, client authors, operators verifying payloads
Effort ~1–2 hours first read; then use as a catalog
Prerequisites Skim Learn 101 so vocabulary (docker_argv, meta, tokens) is familiar
Success You can point to the exact route + schema for each call you make
Page Covers
HTTP API (v1) Every /v1/*, /admin/* static asset, bearer matrix
Schemas & OpenAPI docs/schemas/openapi.json + sibling JSON schemas (mirrored to Hosting /schemas/)
Configuration Environment knobs + defaults
Forge LCDL relationship How Fleet compares to forge-lcdl governed LLM
Workspace localization scope SKU / locale stance for workspaces

Before: Operate 301 · Examples: Examples hub