Read a reference page
Authorization
ApiKeyAuth API key from Settings → API Keys.
In: header
Path Parameters
typst, canvas, or a reference page id from the listing.
Response Body
application/json
application/json
curl -X GET "https://example.com/api/v1/skills/string"{ "id": "typst", "title": "Typst skill", "kind": "skill", "engine": "typst", "summary": "The complete Typst reference.", "content": "# Typst Skill\n\n## What is Typst?\n…"}List engine reference pages GET
What you need to know to author a template, addressable by id. The write API lets you POST a Typst source or a canvas document, but knowing the format is the hard part. These pages are the same engine reference our own editor assistant runs on — the canvas component tables are generated from the engine itself, so they cannot drift from what the renderer will accept. Start with `typst` or `canvas` (`kind: skill`). Each cites the reference pages (`kind: reference`) by id for depth on one topic. The content is rendered for this surface: it names the endpoints you can actually call rather than the internal tool names our editor assistant uses, and it omits capabilities the API does not have.
Where to start GET
The entry point. One call that says what this API is for and where to read the rest. `start_here` points at the **recipes** skill — what you can do and the route to each thing, including what is deliberately not possible. Read it before authoring anything: it is the difference between a template that renders and one that looks plausible and fails. `skills` is the full catalogue, each fetchable in full at its `self`.