Read a reference page
Authorization
ApiKeyAuth API key from API Keys in the dashboard menu.
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.
Who this key is GET
The team an API key belongs to, the organization above it, and the name the key's owner gave the key. It exists so that anything holding a key can say what it is connected to without first knowing an id. `label` is the ready-made answer for a connection list: the team name, with the key's own name when it has one, since a team can have several keys.