List engine reference pages
Authorization
ApiKeyAuth API key from Settings → API Keys.
In: header
Query Parameters
Return only pages that apply to this engine, plus cross-engine ones.
Value in
- "typst"
- "canvas"
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/skills"{ "skills": [ { "id": "typst", "title": "Typst skill", "kind": "skill", "engine": "typst", "summary": "The complete Typst reference: syntax, field annotations, images, the compatibility rules, and the catalogue of errors that actually happen.", "self": "https://automette.com/api/v1/skills/typst" }, { "id": "fonts", "title": "Font catalogue", "kind": "reference", "engine": "both", "summary": "Every available font family with its weights, italic weights, and which families are missing the ★ ✓ ₹ → symbols.", "self": "https://automette.com/api/v1/skills/fonts" } ]}Delete a template asset DELETE
Removes the asset and its stored file. Nothing checks whether the document still references it. Deleting an image a template uses is how you get a `missing_asset` error out of `validate`, which is the right way to find out.
Read a reference page GET
One page in full, as Markdown in the `content` field. Send `Accept: text/markdown` to get the body on its own with no JSON envelope, which is usually what you want to drop into a model's context. Only fonts we ship can be used, and only assets uploaded to the template resolve — both are covered here, and both are the most common way a first render fails.