The kit's authored content, a JSON format for a circuit, and a simulator that runs it on the same solver the player's bench uses. Everything here is keyless except POST /api/ask, which needs an X-Api-Key from POST /api/keys. A circuit document is described by /api/schema/circuit.json; read /llms.txt first if you are a model.
GET /api/experiments — The manual's 25 experimentsGET /api/experiments/{id} — One experiment, with its circuit, hash and schematicGET /api/recipes — Short circuits that show what one part doesGET /api/recipes/{id} — One recipe, with its circuit, hash and schematicGET /api/lessons — The classroom's courseGET /api/lessons/{id} — One lesson, with its full bodyGET /api/parts — The standard board, the drawer, and the pin names of every kindGET /api/schema/circuit.json — JSON Schema for a circuit documentGET /api/openapi.json — This documentGET /api/docs — This document, renderedPOST /api/links — A bench link for a circuit document, plus the canonical document the link carriesGET /api/circuit — The circuit a bench link describesPOST /api/simulate — Run a circuit on the same solver the bench uses and read itPOST /api/keys — Mail an API key for POST /api/askPOST /api/ask — Ask the shop teacher about a circuitMachine-readable: /api/openapi.json · /api/schema/circuit.json · /llms.txt
Prefer MCP? The same thing as a connector: POST /mcp (Streamable HTTP).